Hi Drew, Thanks for replying, but I was obviously not going to do as suggested (too much hassle..)
I have decomposed the ID of the faulty transient node (u1976l1d11) as follows: u1976 l1 d11 I have then supposed that "u" must be the user and indeed, I did have the user 1976, which was, (surprise!), a layout owner. I have reinitialized it's layout, re-added tabs and portlets, and voilà, the error is gone. Thanks for your help, Predrag Le jeudi, 6 décembre 2012 16.23:48, vous avez écrit : > On 12/6/2012 3:26 AM, Predrag Viceic wrote: > > Anyways, I only use DLM to push fragments to users, they cannot > > customize the portal. > > In light of this point, I can offer one idea for how you could eliminate > the problem. Consider the pros & cons. > > You could export and review your fragment data, remove anything that > looks suspicious or unwanted, and re-initialize the database. (Actually > this advice applies to all the data... double-check and make sure you > have all the right data.) > > Normally we don't re-initialize the prod database because it wipes out > user layout customizations. If, as you say, users "cannot customize the > portal," this logic doesn't apply here. > > But don't forget about portlet preferences -- if your users can make > changes to these, that would be reset as well. > > And test it on a DEV environment first, certainly. > > drew wills -- 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
