Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: RE: Upgrade from 7.3 to 7.4?
First I want to say the upgrade from 7.3.5 to 7.3.7 was super smooth! Thanks to the dev team. I had set aside a whole day to troubleshoot the db upgrade process but it just worked! Must admit I am a bit non-plussed and worried there is something I am missing :)
Just want to check other peoples experiences going frm 7,3 to 7.4? I got the list of breaking changes https://learn.liferay.com/dxp/latest/en/liferay-internals/reference/7-4-breaking-changes.html
Anything else I should know about?
thanks
My expectation: The smaller the steps are, the better the experience. Make sure to always upgrade to the latest available GA version though: it also contains fixes to upgrade routines
I've not heard of any problems with the upgrade so far. From gut feeling, most of the problems have been in systems that have been around for ages, and collected some cruft before upgrading. Not to mention those where people manipulated the database manually.
Thanks you Olaf for the reply!
You are totally right of course the development started like 5 years ago with it seems some little hacks here and there.
It's really painful to learn liferay and in the same time to migrate "an old project".
So to give some feedbacks: I finally decided to start from scratch. I made on assumption on some properties to generate the theme to extend and I iterated from it with a lot of copy and paste from the orginal source code.
So far I have two issues :
First)
The store for the document is DB. As I said I dumped the DB, create a new one, and I played the "portal-tools-db-upgrade-client" on it. I can see my documents but I still have some errors on some pages like :
=> request['theme-display'] [in template "20116#20152#1009391" at line 1, column 26]
----
Tip: It's the final [] step that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: #assign images_folder = request["them... [in template "20116#20152#1009391" at line 1, column 1]
----I'm trying to find what is going on but so far I don't have a good lead.
Second)
On the pages configuration we have a custom layout. After migration I don't see it anymore, I don't know why.
Any helps on the two issues are welcome.
@Olaf Kock What are upgrade routines?
Are there upgrade instructions from 7.2 to 7.4?
My questions about 7.3 to 7.4 mainly revolve around web content. There's the potential for a lot of pain there.
Powered by Liferay™