1. Home
  2. Portal
  3. Need some basic help to understand how to upgrade from 7.0 to 7.4?

Need some basic help to understand how to upgrade from 7.0 to 7.4?

Jamie Sammons, modified 3 Years ago.
Need some basic help to understand how to upgrade from 7.0 to 7.4?
New Member Posts: 7 Join Date: 2/10/22 Recent Posts

Hello guys !

I'm new to liferay and and I'm learning it the hard way.

My task is to take 3 maven projects "wars" (two themes and 1 "portlet" form) in 7.0 and to upgrade them in 7.4.

So far I succeed to upgrade the database, and to deploy the 3 projects in a 7.4 liferay tomcat bundle (I just replaced in some xml/properties 7.0.0 by 7.4.0).

Of course nothing is working properly I have some errors.

I'm wondering what is the best way to upgrade the code without trying to correct the errors one by one...

So far I tried  :

  • To use Eclispse LifeRay Upgrade Plan
  • To use generator-liferay-theme

But I'm little bit stucked I can't find a way to make them work.

Any tips are welcome :)

Thanks by advance!

upgrade
Jamie Sammons, modified 3 Years ago.
RE: Need some basic help to understand how to upgrade from 7.0 to 7.4?
New Member Posts: 7 Join Date: 2/10/22 Recent Posts

I confirmed 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.