Thanks for the information!

Hi Paul, Yes a clean install is also a good option. I gues we in Europe have become upgrade freeks specialy on devises and software. like we starting a new race to the next version every time. And you are so right, everything is working well and there is no hurry at all. Nothings broke and the sun is shining, I going have a sit outside. Have a nice weekend!

Hi Rashida,
thanks for your inquiries.
Obviously I'm working on a test environment that is the exact copy of the published site.
The current environment is:
PHP Built On Windows NT 10.0 build 19041 (Windows 10) AMD64
Database Type mysql
Database Version 5.5.5-10.4.19-MariaDB
Database Collation utf8mb4_general_ci
Database Connection Collation utf8mb4_general_ci
PHP Version 7.4.20
Web Server Apache/2.4.48 (Win64) OpenSSL/1.1.1k PHP/7.4.20
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.10.2 Stable [ Daraja ] 12-September-2021 11:01 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36

Template:
shaper_helixultimate Template 2.0.5 Feb 2018 JoomShaper.com
System - Helix Ultimate Framework Plugin 2.0.5 Feb 2018 JoomShaper.com

SP page builder:
Search - SP Page Builder Plugin 1.5 July 2015 JoomShaper
Smart Search - SP Page Builder Plugin 1.6.1 March 2018 JoomShaper
SP Page Builder Administrator Component 3.7.15 Sep 2014 JoomShaper
SP Page Builder Admin Menu Administrator Module 1.4 August 2014 JoomShaper
SP Simple Portfolio - SP Page Builder Plugin 1.1 Mar 2019 JoomShaper
System - SP Page Builder Pro Updater Plugin 1.1 Jul 2015 JoomShaper.com
System - SP PageBuilder Plugin 1.4 Sep 2016 JoomShaper.com

When I do the Pre-Update Check routine for Joomla 4.0.3
I pass the checks on:
Required PHP & Database Settings
Recommended PHP Settings
And the modules that not need update are:
Extension Name Extension Type Installed Version Joomla 3.10.2 Joomla 4.0.3
Com. Ver. Comp. Ver.
SP Page Builder Component 3.7.15 3.7.15 3.7.15
SP Simple Portfolio Component 2.0.5 2.0.5 2.0.5
Installer - Install from Web Plugin 2.1.2 2.1.2 2.1.2
SP Easy Image Gallery Component 2.0.0 2.0.0 2.0.0
System - Helix Ultimate Framework Plugin 2.0.5 2.0.5 2.0.5
MouseOverZoom Plugin 1.3.3 1.3.3 1.3.3

But in the “Unavailable Update Information reports” remain:
Extension Name Extension Installed Joomla 3.10.2 Joomla 4.0.3
SP Page Builder Admin Menu Module 1.4 No comp. inf. No comp. inf.
shaper_helixultimate Template 2.0.5 1.0.1 No comp. inf.
SP Easy Image Gallery Module Module 2.0.0 1.5.2 No comp. inf.
SP Simple Map Module 1.3 No comp. inf. No comp. inf.
SP Accordion module Module 2.8.0 No comp. inf. No comp. inf.
System - SP PageBuilder [Potential Upgrade Issue] [More Information] Plugin 1.4 No comp. inf. No comp. inf.
System - SP Page Builder Pro Updater [Potential Upgrade Issue] [More Information] Plugin 1.1 No comp. inf. No comp. inf.
Search - SP Page Builder Plugin 1.5 No comp. inf. No comp. inf.
Smart Search - SP Page Builder Plugin 1.6.1 No comp. inf. No comp. inf.
vi-solutions Library Library 1.6.1 No comp. inf. No comp. inf.
SP Simple Portfolio - SP Page Builder Plugin 1.1 No comp. inf. No comp. inf.
SP Simple Portfolio Module Module 2.0 1.9 No comp. inf.
System - SP Cookie Consent [Potential Upgrade Issue] [More Information] Plugin 1.0.0 1.0 No comp. inf.

Starting the ugrade the operation fails with this error message:
“An error has occurred.
0 Call to undefined method Joomla\CMS\Application\AdministratorApplication::isAdmin()”

I don't know if I have to uninstall all modules for which there are no compatibility information available, but in this case what guarantee do I have that everything will continue to work fine?
La verifica di aggiornamento non danno nessuna segnalazione

Thanks
Any suggestions will be valuable
Ugo

Paul

I am agree with you about the opportunity to postpone the upgrade waiting for a stable version of joomla 4.x.x.
However, the compatibility problem will come back sooner or later and I would like to solve it with peace of mind and not in the middle of the migration.

Hi Paul, as you suggested, I have disabled all modules for which no compatibility information was available except shaper_helixultimate because it is the default template. Otherwise I would just have to disable vi-solutions Library
In the pre update check phase, I received the same list of modules with the information not available, and the migration gave the same error.
I believe that in order to have reliable feedback I have to uninstall the modules, but in that way I don’t know if the site is still usable.
I started building the site with joomla and helixultimate using a quick start package and subsequently bought the SP page builder pro twice.
But I see that there are modules of old versions.
Can they be removed or do I risk losing my job?
Why does the installation package not clean up the environment by replacing obsolete modules?
I tried to install jooma 4.0.2 with helixutimate 2.0.5 and later I also installed sp page builder pto 3.7.5. and it seems to work fine.
I also exported and imported the pages created with SP page builder (with a little work it is possible to fix them), the big problem are the articles for which rewriting is unthinkable.

Thanks for your information Paul.
I'll wait ......

Hi Paul,

You guys really need to do something on your communication. In the happy emails we read that, the world is so beautifull with the new helixultimate, followed by new templates new tepmlates and more and more new templates. maybe the "new template" team should first work on fixter? or arino?