Yet another Liferay Upgrade X-File




written by Marco Ferretti on February 20, 2012, at 02:22 PM

Yesterday I was testing the upgrade of one of the Liferay instances I ( sort of ) manage. Everything has gone sweet ( meaning I had no major failures ) during the upgrades until I actually started testing the content of some pages. One of the standard tests I do is open a web-content for editing, check that everything runs fine, make a small change, change the version, publish, check the published content and then revert. Image my face when I opened the a content for editing and all the images where ... gone! Absolutely gone ! I closed the content and checked the website and the images where there. I thought it must have been just fantastic luck, so I restarted the server and tried another content . Here we go again : in editing mode I cannot see the images any longer.

It took me some time but then I found out that, for some strange reason, the images url where not resolved due to an error in variable sobstitution : the groupid attribute was set ( in the pages where the problem arose ) as @group_id@; this was ok viewing the content, not so ok editing it .

I solved this thanks to the support of the #liferay channel on freenode, namely thanks to the patience of adaro.

The solution consists in upgrading the content in the databse. Here's the script I used on a PostgreSQL database:

update journalarticle set content = REPLACE(content, '@group_id@', trim(to_char(groupId, '99999999999999999')));

Now the question, at least for me, is how is it that it was working on 5.2.3 and it is not on 6.0.6 ? Looks like the folks @Liferay have some issues with regression tests ...

Anyway : my problem was totally random : another instance of Liferay did not show the same problems ... but I decided to blog about it for (a) future reference in case something like this happens to me again, and (b) if somebody happens to have the same problem .

Cheers !

Leave a comment

Name (required)
E-mail (required, will not be published)
Website
Comment

Enter value: Captcha