Joomla 3 To Joomla 4 Problems - Question | JoomShaper

Joomla 3 To Joomla 4 Problems

Carlos Arango

Carlos Arango

General 2 years ago

We had a web site jesuitas.co in Jommla 3 using Gazzette template and we need to update the site to Joomla 4…. Actual site in Joomla 3 with Gazzette and SP page Builder 3.8.9 : http://jesuitas.co

After migration the gazzete adons crash and we check the forums and was a lot of information about fails because gazette was not prepare to evolve to new sp page builer yet. We decide to change the template to nuron template and use sp page builde 4.0.8.

New Site already Migrate to Joomla 4 using Nuron and Sp Page Builder 4.0.8 http://nuevo.jesuitas.co

But we have 2 big problems not solved:

1- SP page Builder doesn work. It was working in 3.8.8 but when we upgrade to 4.0.8 theres a blink and a white page is show and There is also an error in System / Database

2- When you create an article in joomla 4 when you save there’s an error

Save failed with the following error: Field 'id' doesn't have a default value

The only way to go out is press the cancel option ..and after click there’s not the latest article show in the list but when you check database the articles are there but unaccesible from articles in Joomla.

Se attached file in: https://nuevo.jesuitas.co/problems/jesuitas_j3_to_j4_problems.pdf

0
2 Answers
Carlos Arango
Carlos Arango
Accepted Answer
2 years ago #108848

Stilll not response

0
Rashida Rahman
Rashida Rahman
Accepted Answer
Support Agent 2 years ago #108887

Hi,

Sorry for your issue and delayed response. You may try the following:

Please uninstall your SP Page Builder by 1st unpublishing your module/extension (from the Extensions\Modules tab) and trashing it.

Then go to Extensions tab again and navigate to "Manage" and find your SP Page Builder extension, then unpublish it and then 'Uninstall' from menu option.

Download a fresh copy / package of the SP Page Builder Extension from JoomShaper's Extensions Download page and reinstall, then recreate a module, and its content.

PS: you are basically then disassociating the original database associated with the template and allowing the Extension upon new installation to recreate a new / blank database that will work with current version of template

Hope this helps!

Note: Please take a full site backup before trying anything!

Best Regards

0