An update. This doesn't work on the up32 branch code (when logged in as admin), I was looking at an out of date db.
So the problem is that the fragment-admin channel is not added to the layout. Would adding it to the defaultTempalteUser.layout fix this for all users? Is that the goal of the allowExpandedContent parameter in DLM? Or should this channel (and any others) be added to the template owners layouts (ie student-lo etc) regards, Steve On 11/10/2011, at 1:08 PM, Steve Swinsburg wrote: > Hi all, > > We are having an issue where the fragment-admin link on the right hand nav > won't show up. > > We've patched uPortal 3.2.4 up to the latest 3.2.5 branch and along with it > came the mod from this issue: https://issues.jasig.org/browse/UP-2895 > > ...which essentially removes the cruft from the header and footer folder of > the layout templates, but specifically removing fragment-admin channel from > the defaultTemplateUser.layout > > I presume that removing this from defaultTemplateUser means it won't be added > in the header of a user's layout? How then does it ever get added? I think > this is to do with a modification we've made somewhere since it works fine on > the pristine 3.2.5 branch code, but I'm at a loss as to where I should look > as all of the layout code we have is identical to the branch. And the > statement in universality.xsl that is meant to add it to the page is still > the same as: > > <!-- Fragment Administration --> > <xsl:copy-of select="//channel[@fname = 'fragment-admin']"/> > > If a user navigates directly to the portlet then it works: > /uPortal/render.userLayoutRootNode.uP?uP_fname=fragment-admin > > Any tips? > > regards, > Steve > > -- 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
