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
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
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
+1 for removing the old CChannelManager and switching over to the new
one in trunk.
I don't say this lightly either. I know there is some risk here, but I
think this is a HUGE improvement and is worth the risk.
Cris J H
Jen Bourey wrote:
Hi all,
The new Portlet Administration
+1 as well.
If we can perhaps get this switch done by the end of next week I could
get a 3.2.0-M1 release and quickstart (before I disappear into a 3 week
vacation in June) to give people a chance to play with the new portlet
manager and provide feedback.
-Eric
Cris J Holdorph wrote:
+1
. Mountain Time
(Arizona)
Subject: Re: [uportal-dev] Portlet Administration Portlet Update (UP-2047)
+1 as well.
If we can perhaps get this switch done by the end of next week I could
get a 3.2.0-M1 release and quickstart (before I disappear into a 3 week
vacation in June) to give people a chance
