Ah,So that is fixed in the import scripts in trunk, I forgot to mention that part of the commit. The .channel and .layout import scripts replace any character in an fname that doesn't match [\w-] with an _
-Eric Cris J Holdorph wrote:
I think you misunderstand what I'm getting at.If you have an existing portal you want to upgrade to uPortal 3.2 when it comes out. And if you have existing channels that *you* added that did not conform to the new naming conventions, then they would not import properly.I guess we can simply tell people they'll have to hand edit their channel files, before they reimport, but that seems kind of like a poor workaround.---- Cris J H Eric Dalquist wrote:I believe the export scripts are unaffected by these changes. Are they failing for you?Cris J Holdorph wrote:you might want to do some work on the export scripts, so people can't export something they can't then turn around and import.---- Cris J H Eric Dalquist wrote:In continuation of this great work I'm working on doing additional cleanup of the channel definition object model. One of these changes is enforcing further restrictions on FNames. I'm committing some changes that now enforce that all channel fnames can only contain characters [a-zA-Z0-9_-]. We had a bunch of channels that had . and / in the fnames which I've replaced with _ in the entity files and in the code where they are referenced.You will need do to do an initdb if you update from trunk after this email.-Eric Jen Bourey wrote:The new Portlet Administration Portlet is now the default channel managing utility in uPortal. If you notice any bugs, please let me know! The parameter-setting screen in particular still has a few rough edges, but you should be able to use the portlet to successfully modify, delete, and create channel definitions.- JenOn Wed, May 20, 2009 at 4:11 PM, Jen Bourey <[email protected] <mailto:[email protected]>> wrote:Hi all, The new Portlet Administration Portlet described by JIRA entry UP-2047 is now in the trunk, and I believe we've updated it to include all features currently available in CChannelManager. I would like to be able to switch the admin link in the layout over to use this new portlet. Does anyone have an objection to making this new portlet the default portlet administration tool sometime in the near future? Are there features you rely on inCChannelManager that don't appear to be included in the new portlet?We've also had discussions in the uPortal IRC channel about potentially removing CChannelManager altogether for the 3.2 release. Doing this would allow us to move forward with the proposed portlet workflow lifecycle work without having to worry about its affects on the legacy channel implementation. - Jen -- Jen Bourey -- Jen Bourey --You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
smime.p7s
Description: S/MIME Cryptographic Signature
