Migration to Joomla 4 - Forum | JoomShaper
Solved SP Page Builder

Migration to Joomla 4

Asked by francesco1980 4 years ago Last activity 4 years ago

I've got two warning messages about potential update problems in the pre-update check regarding this components
System - SP PageBuilder Plugin 2.0
System - SP Page Builder Pro Updater PLugin 1.1

While SP Page Builder component 3.8.6 is considered ready to migrate

I've cloned my site so I ready to test anything without fear.

Could you suggest what to do to remove those warnings?

Thank you for your support

Accepted answer

Marked as the solution

8 more replies

francesco1980 Asked this

Thank you for your answer.
I disabled the mentioned plugin and completed the migration following the instruction.
After the migration I followed the post migration instructions:

  • cleared cache
  • made global control and found a table to unlock j39_sppagebuilder
  • unlocked the table as requested
  • made a global control again without errors

But the front end site doesn't work.
Every page show this erro message
Cannot access protected property Joomla\CMS\Menu\MenuItem::$params

Could you plese help?

Toufiq Senior Staff

Will you please provide me the Joomla administrator access to check the issue?

francesco1980 Asked this

Plase find the requested info in the hidden content area

Paul Frankowski Senior Staff

Ciao Francesco. Yes, you can ignore them and upgrade Joomla to 4.x, please read what we written here

foto_8418_2022.png

francesco1980 Asked this

I'm sorry Paul
But I disabled those plugin before upgrading and I don't know if this has caused the problem on the front-end side.
I tried to enable them after the migration but it doesn't solve the problem.
I still get "Cannot access protected property Joomla\CMS\Menu\MenuItem::$params" on every page

Toufiq Senior Staff

Please check now. You didn't update your template before update Joomla 4. Now it has been updated. Thanks

francesco1980 Asked this

I'm sorry Touqif. I didn't notice that the template was in the section "Update information Unavailable" of the Pre-update check page.
Now I have downloaded the 2.0 version of the template and will repeate the migration process in the production environment.
Thank you for your support.

Log in to reply.