Menu problem after upgrade from 3.10 to 4.2.3

Need help upgrading your Joomla! website or converting to Joomla! 4.x?

Moderator: General Support Moderators

Forum rules
Forum Rules
Absolute Beginner's Guide to Joomla! <-- please read before posting, this means YOU.
Forum Post Assistant - If you are serious about wanting help, you will use this tool to help you post.
Windows Defender SmartScreen Issues <-- please read this if using Windows 10.
Post Reply
cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Sat Oct 01, 2022 5:06 pm

Hello,
I uninstalled the custom templates, only the standard templates are installed:
+ Beez3
+ Hathor Administrator Template
+ ISIS Administrator Template
+ Protostar
Protostar is default.
I uninstalled everything that was displayed as a possible problem by "Pre-Update Check". Except for three problems that I cannot uninstall. See "01-Beforeupgrade.jpg"
The frontend does not work at all.
On the backend, the menu covers the upper part ... see "02-finger-upgrade.jpg".
I do not know how what to do now……
Regards
Christian
You do not have the required permissions to view the files attached to this post.

User avatar
ceford
Joomla! Ace
Joomla! Ace
Posts: 1381
Joined: Mon Feb 24, 2014 10:38 pm
Location: Edinburgh, Scotland
Contact:

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by ceford » Sat Oct 01, 2022 6:52 pm

Open administrator/logs/joomla_update.php with a text editor and scroll down to the bottom. You should see about 400 sql statements followed by some other messages. What do you see?

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Sun Oct 02, 2022 6:28 am

The file was in "C:\xampp\htdocs\TC2\logs".
The content is:

#
#<?php die('Forbidden.'); ?>
#Date: 2022-10-01 16:55:46 UTC
#Software: Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT

#Fields: datetime priority clientip category message
2022-10-01T16:55:45+00:00 INFO ::1 update Update started by user Super User (191). Old version is 3.10.11.
2022-10-01T16:55:47+00:00 INFO ::1 update Downloading update file from https://s3-us-west-2.amazonaws.com/joom ... f14412fb3f.
2022-10-01T16:55:52+00:00 INFO ::1 update File Joomla_4.2.3-Stable-Update_Package.zip downloaded.
2022-10-01T16:55:52+00:00 INFO ::1 update Starting installation of new version.
2022-10-01T16:56:42+00:00 INFO ::1 update Finalising installation.
2022-10-01T16:56:42+00:00 INFO ::1 update Start of SQL updates.
2022-10-01T16:56:42+00:00 INFO ::1 update The current database version (schema) is 3.10.7-2022-03-18.
2022-10-01T16:56:42+00:00 INFO ::1 update Ran query from file 4.0.0-2018-03-05. Query text: ALTER TABLE `#__extensions` DROP COLUMN `system_data` ;.
2022-10-01T16:56:42+00:00 INFO ::1 update Ran query from file 4.0.0-2018-03-05. Query text: INSERT INTO `#__extensions` (`name`, `type`, `element`, `folder`, `client_id`, `.
2022-10-01T16:56:42+00:00 INFO ::1 update Ran query from file 4.0.0-2018-03-05. Query text: DELETE FROM `#__extensions` WHERE `type` = 'library' AND `element` = 'phputf8';.
2022-10-01T16:56:42+00:00 INFO ::1 update Ran query from file 4.0.0-2018-03-05. Query text: DELETE FROM `#__extensions` WHERE `type` = 'plugin' AND `element` = 'p3p' AND `f.
2022-10-01T16:56:42+00:00 INFO ::1 update Ran query from file 4.0.0-2018-03-05. Query text: ALTER TABLE `#__user_keys` DROP COLUMN `invalid` ;.
2022-10-01T16:56:42+00:00 INFO ::1 update Ran query from file 4.0.0-2018-03-05. Query text: INSERT INTO `#__extensions` (`name`, `type`, `element`, `folder`, `client_id`, `.

After that, nothing else

User avatar
ceford
Joomla! Ace
Joomla! Ace
Posts: 1381
Joined: Mon Feb 24, 2014 10:38 pm
Location: Edinburgh, Scotland
Contact:

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by ceford » Sun Oct 02, 2022 9:05 am

That is the wrong place for the logs files, which may suggest the paths are wrong in your configuration.php file. The queries that should have been executed are in administrator/components/com_admin/sql/updates/mysql. The one that failed and the following one are these:

Code: Select all

INSERT INTO `#__extensions` (`name`, `type`, `element`, `folder`, `client_id`, `enabled`, `access`, `protected`, `manifest_cache`, `params`, `custom_data`, `checked_out`, `checked_out_time`, `ordering`, `state`) VALUES
('atum', 'template', 'atum', '', 1, 1, 1, 0, '{}', '{}', '', 0, '0000-00-00 00:00:00', 0, 0),
('cassiopeia', 'template', 'cassiopeia', '', 0, 1, 1, 0, '{}', '{}', '', 0, '0000-00-00 00:00:00', 0, 0);

-- The following statement had to be modified for 4.1 by adding the `inheritable` and `parent` columns.
-- See https://github.com/joomla/joomla-cms/pull/36585
INSERT INTO `#__template_styles` (`template`, `client_id`, `home`, `title`, `inheritable`, `parent`, `params`) VALUES
('atum', 1, (CASE WHEN (SELECT b.`count` FROM (SELECT count(a.`id`) AS `count` FROM `#__template_styles` a WHERE a.`home` = '1' AND a.`client_id` = 1 AND a.`template` IN ('isis', 'hathor')) AS b) = 0 THEN '0' ELSE '1' END), 'atum - Default', 1, '', '{}'),
('cassiopeia', 0, (CASE WHEN (SELECT d.`count` FROM (SELECT count(c.`id`) AS `count` FROM `#__template_styles` c WHERE c.`home` = '1' AND c.`client_id` = 0 AND c.`template` IN ('protostar', 'beez3')) AS d) = 0 THEN '0' ELSE '1' END), 'cassiopeia - Default', 1, '', '{}');
Have a look at the extensions and template_styles tables in your database with phpMyAdmin. If these two entries are present then you may not have emptied your database prior to restoring a previous backup.

Anyway, you need to empty the database, remove all site files and restore your previous backup.

But first, run the Forum Post Assistant and post the public results here. You may have poor php settings.

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Sun Oct 02, 2022 10:41 am

Thank you very much for your post!

Before upgrading my production site to J4, I am doing upgrade tests with a VM that runs XAMPP. After fail of a step, I trash that VM and start-over with the VM before the upgrade. So I have no issues with some leftover somewhere.

I attached the FPA output
You do not have the required permissions to view the files attached to this post.

User avatar
AMurray
Joomla! Exemplar
Joomla! Exemplar
Posts: 8172
Joined: Sat Feb 13, 2010 7:35 am
Location: Australia

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by AMurray » Sun Oct 02, 2022 1:00 pm

please follow the instructions and copy the FPA output into a reply in this post. It's not something you attach to a reply.
Regards - A Murray

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Sun Oct 02, 2022 3:39 pm

The attachment is apparently only visible after log in
Anyways, here is the output of FPA before upgrade:
Forum Post Assistant (v1.6.5) : 2-Oct-2022 wrote:
Basic Environment :: wrote:Joomla! Instance :: Joomla! 3.10.11-Stable (Daraja) 14-August-2022
Joomla! Platform :: Joomla Platform 13.1.0-Stable (Curiosity) 24-Apr-2013
Joomla! Configured :: Yes | Read-Only (444) |
Configuration Options :: Offline: false | SEF: true | SEF Suffix: false | SEF ReWrite: false | .htaccess/web.config: No | GZip: false | Cache: false | CacheTime: 15 | CacheHandler: file | CachePlatformPrefix: false | FTP Layer: false | Proxy: false | LiveSite: | Session lifetime: 60 | Session handler: database | Shared sessions: false | SSL: 0 | Error Reporting: default | Site Debug: false | Language Debug: false | Default Access: Public | Unicode Slugs: false | dbConnection Type: mysqli | PHP Supports J! 3.10.11: Yes | Database Supports J! 3.10.11: Yes | Database Credentials Present: Password missing |

Host Configuration :: OS: Windows NT | OS Version: 10.0 | Technology: AMD64 | Web Server: Apache/2.4.53 (Win64) OpenSSL/1.1.1n PHP/8.1.6 | Encoding: gzip, deflate, br | System TMP Writable: Yes | Free Disk Space : 42.45 GiB |

PHP Configuration :: Version: 8.1.6 | PHP API: apache2handler | Session Path Writable: Yes | Display Errors: 0 | Error Reporting: 22527 | Log Errors To: C:\xampp\php\logs\php_error_log | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: | Allow url fopen: 1 | Open Base: | Uploads: 1 | Max. Upload Size: 40M | Max. POST Size: 40M | Max. Input Time: 60 | Max. Execution Time: 120 | Memory Limit: 512M

Database Configuration :: Version: 10.4.24-MariaDB (Client:mysqlnd 8.1.6) | Database Size: 11.57 MiB | #of Tables with config prefix:  146 | #of other Tables:  0 | User Privileges : GRANT PROXY
Detailed Environment :: wrote:PHP Extensions :: Core (8.1.6) | bcmath (8.1.6) | calendar (8.1.6) | ctype (8.1.6) | date (8.1.6) | filter (8.1.6) | hash (8.1.6) | iconv (8.1.6) | json (8.1.6) | SPL (8.1.6) | pcre (8.1.6) | readline (8.1.6) | Reflection (8.1.6) | session (8.1.6) | standard (8.1.6) | mysqlnd (mysqlnd 8.1.6) | tokenizer (8.1.6) | zip (1.19.5) | zlib (8.1.6) | libxml (8.1.6) | dom (20031129) | PDO (8.1.6) | bz2 (8.1.6) | SimpleXML (8.1.6) | xml (8.1.6) | xmlreader (8.1.6) | xmlwriter (8.1.6) | apache2handler (8.1.6) | openssl (8.1.6) | curl (8.1.6) | fileinfo (8.1.6) | gettext (8.1.6) | mbstring (8.1.6) | exif (8.1.6) | mysqli (8.1.6) | pdo_mysql (8.1.6) | pdo_sqlite (8.1.6) | Phar (8.1.6) | ftp (8.1.6) | Zend Engine (4.1.6) |
Potential Missing Extensions ::

Switch User Environment :: PHP CGI: No | Server SU: No | PHP SU: No | Potential Ownership Issues: No

Apache Modules :: core | mod_win32 | mpm_winnt | http_core | mod_so | mod_access_compat | mod_actions | mod_alias | mod_allowmethods | mod_asis | mod_auth_basic | mod_authn_core | mod_authn_file | mod_authz_core | mod_authz_groupfile | mod_authz_host | mod_authz_user | mod_autoindex | mod_cgi | mod_dav_lock | mod_dir | mod_env | mod_headers | mod_include | mod_info | mod_isapi | mod_log_config | mod_cache_disk | mod_mime | mod_negotiation | mod_proxy | mod_proxy_ajp | mod_rewrite | mod_setenvif | mod_socache_shmcb | mod_ssl | mod_status | mod_version | mod_php | Apache/2.4.53 (Win64) OpenSSL/1.1.1n PHP/8.1.6 |
Potential Missing Modules :: mod_expires | mod_deflate |
Folder Permissions :: wrote:Core Folders :: images/ (Writable) | components/ (Writable) | modules/ (Writable) | plugins/ (Writable) | language/ (Writable) | templates/ (Writable) | cache/ (Writable) | logs/ (Writable) | tmp/ (Writable) | administrator/components/ (Writable) | administrator/modules/ (Writable) | administrator/language/ (Writable) | administrator/templates/ (Writable) | administrator/logs/ (Writable) |
Database Information :: wrote:Database statistics :: Uptime: 426997 | Threads: 6 | Questions: 37998 | Slow queries: 0 | Opens: 885 | Flush tables: 1 | Open tables: 191 | Queries per second avg: 0.088 |
Extensions Discovered :: wrote:Components :: Site ::
Core :: com_mailto (3.0.0) 1 | com_wrapper (3.0.0) 1 |
3rd Party::

Components :: Admin ::
Core :: com_actionlogs (3.9.0) 1 | com_admin (3.0.0) 1 | com_ajax (3.2.0) 1 | com_associations (3.7.0) 1 | com_banners (3.0.0) 1 | com_cache (3.0.0) 1 | com_categories (3.0.0) 1 | com_checkin (3.0.0) 1 | com_config (3.0.0) 1 | com_content (3.0.0) 1 | com_contenthistory (3.2.0) 1 | com_cpanel (3.0.0) 1 | com_fields (3.7.0) 1 | com_finder (3.0.0) 1 | com_installer (3.0.0) 1 | com_joomlaupdate (3.10.1) 1 | com_languages (3.0.0) 1 | com_login (3.0.0) 1 | com_media (3.0.0) 1 | com_menus (3.0.0) 1 | com_messages (3.0.0) 1 | com_modules (3.0.0) 1 | com_newsfeeds (3.0.0) 1 | com_plugins (3.0.0) 1 | com_postinstall (3.2.0) 1 | com_privacy (3.9.0) 1 | com_redirect (3.0.0) 1 | com_search (3.0.0) 1 | com_tags (3.1.0) 1 | com_templates (3.0.0) 1 | com_users (3.0.0) 1 | com_weblinks (4.0.1) 1 |
3rd Party:: Droptables (3.9.2) 1 | Editors-xtd - Droptables (3.9.2) ? | Content - droptables (3.9.2) ? | Joomunited updater (1.0.0) ? | Droptables frontend (3.9.2) ? | Quick Logout (1.8.0) ? | com_rsform (3.1.1) 1 |

Modules :: Site ::
Core :: mod_articles_archive (3.0.0) 1 | mod_articles_categories (3.0.0) 1 | mod_articles_category (3.0.0) 1 | mod_articles_latest (3.0.0) 1 | mod_articles_news (3.0.0) 1 | mod_articles_popular (3.0.0) 1 | mod_banners (3.0.0) 1 | mod_breadcrumbs (3.0.0) 1 | mod_custom (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_finder (3.0.0) 1 | mod_footer (3.0.0) 1 | mod_languages (3.5.0) 1 | mod_login (3.0.0) 1 | mod_menu (3.0.0) 1 | mod_random_image (3.0.0) 1 | mod_related_items (3.0.0) 1 | mod_search (3.0.0) 1 | mod_stats (3.0.0) 1 | mod_syndicate (3.0.0) 1 | mod_tags_popular (3.1.0) 1 | mod_tags_similar (3.1.0) 1 | mod_users_latest (3.0.0) 1 | mod_weblinks (4.0.1) 1 | mod_whosonline (3.0.0) 1 | mod_wrapper (3.0.0) 1 |
3rd Party:: mod_j2store_products (3.1) ? | Art Universal Lightbox (1.5.3) 1 | RSForm! Pro Module (3.0.1) 1 | JJ Social Slider (3.0.0) 1 |

Modules :: Admin ::
Core :: mod_custom (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_latest (3.0.0) 1 | mod_latestactions (3.9.0) 1 | mod_logged (3.0.0) 1 | mod_login (3.0.0) 1 | mod_menu (3.0.0) 1 | mod_multilangstatus (3.0.0) 1 | mod_popular (3.0.0) 1 | mod_privacy_dashboard (3.9.0) 1 | mod_quickicon (3.0.0) 1 | mod_sampledata (3.8.0) 1 | mod_stats_admin (3.0.0) 1 | mod_status (3.0.0) 1 | mod_submenu (3.0.0) 1 | mod_title (3.0.0) 1 | mod_toolbar (3.0.0) 1 | mod_version (3.0.0) 1 |
3rd Party:: Ark Editor Control Panel (1.0.0) ? |

Libraries ::
Core ::
3rd Party:: file_fof30 (3.7.4) ? | file_fof40 (4.1.3) ? |

Plugins ::
Core :: PLG_ACTIONLOG_JOOMLA (3.9.0) 1 | plg_authentication_cookie (3.0.0) 1 | plg_authentication_gmail (3.0.0) 0 | plg_authentication_joomla (3.0.0) 1 | plg_authentication_ldap (3.0.0) 0 | plg_captcha_recaptcha (3.4.0) 1 | plg_captcha_recaptcha_invisible (3.8) 0 | plg_content_confirmconsent (3.9.0) 0 | plg_content_emailcloak (3.0.0) 1 | plg_content_fields (3.7.0) 1 | plg_content_finder (3.0.0) 1 | plg_content_joomla (3.0.0) 1 | plg_content_loadmodule (3.0.0) 1 | plg_content_pagebreak (3.0.0) 1 | plg_content_pagenavigation (3.0.0) 1 | plg_content_vote (3.0.0) 0 | plg_editors-xtd_article (3.0.0) 1 | plg_editors-xtd_fields (3.7.0) 1 | plg_editors-xtd_image (3.0.0) 1 | plg_editors-xtd_menu (3.7.0) 1 | plg_editors-xtd_module (3.5.0) 1 | plg_editors-xtd_pagebreak (3.0.0) 1 | plg_editors-xtd_readmore (3.0.0) 1 | plg_editors-xtd_weblink (4.0.1) 0 | plg_extension_joomla (3.0.0) 1 | plg_fields_calendar (3.7.0) 1 | plg_fields_checkboxes (3.7.0) 1 | plg_fields_color (3.7.0) 1 | plg_fields_editor (3.7.0) 1 | plg_fields_imagelist (3.7.0) 1 | plg_fields_integer (3.7.0) 1 | plg_fields_list (3.7.0) 1 | plg_fields_media (3.7.0) 1 | plg_fields_radio (3.7.0) 1 | plg_fields_repeatable (3.9.0) 1 | plg_fields_sql (3.7.0) 1 | plg_fields_text (3.7.0) 1 | plg_fields_textarea (3.7.0) 1 | plg_fields_url (3.7.0) 1 | plg_fields_user (3.7.0) 1 | plg_fields_usergrouplist (3.7.0) 1 | plg_finder_categories (3.0.0) 1 | plg_finder_contacts (3.0.0) 1 | plg_finder_content (3.0.0) 1 | plg_finder_newsfeeds (3.0.0) 1 | plg_finder_tags (3.0.0) 1 | plg_finder_weblinks (4.0.1) 1 | PLG_INSTALLER_FOLDERINSTALLER (3.6.0) 1 | plg_installer_packageinstaller (3.6.0) 1 | PLG_INSTALLER_URLINSTALLER (3.6.0) 1 | plg_installer_webinstaller (2.1.2) 1 | plg_privacy_actionlogs (3.9.0) 1 | plg_privacy_consents (3.9.0) 1 | plg_privacy_content (3.9.0) 1 | plg_privacy_message (3.9.0) 1 | plg_privacy_user (3.9.0) 1 | plg_quickicon_eos310 (3.10.0) 1 | plg_quickicon_extensionupdate (3.0.0) 1 | plg_quickicon_joomlaupdate (3.0.0) 1 | plg_quickicon_phpversioncheck (3.7.0) 1 | plg_quickicon_privacycheck (3.9.0) 1 | plg_search_categories (3.0.0) 1 | plg_search_contacts (3.0.0) 1 | plg_search_content (3.0.0) 1 | plg_search_newsfeeds (3.0.0) 1 | plg_search_tags (3.0.0) 0 | plg_search_weblinks (4.0.1) 1 | PLG_SYSTEM_ACTIONLOGS (3.9.0) 0 | plg_system_cache (3.0.0) 0 | plg_system_debug (3.0.0) 1 | plg_system_fields (3.7.0) 1 | plg_system_highlight (3.0.0) 1 | plg_system_languagecode (3.0.0) 0 | plg_system_languagefilter (3.0.0) 1 | plg_system_log (3.0.0) 1 | plg_system_logout (3.0.0) 1 | plg_system_logrotation (3.9.0) 1 | plg_system_p3p (3.0.0) 1 | plg_system_privacyconsent (3.9.0) 0 | plg_system_redirect (3.0.0) 1 | plg_system_remember (3.0.0) 1 | plg_system_sef (3.0.0) 1 | plg_system_sessiongc (3.8.6) 1 | plg_system_stats (3.5.0) 1 | plg_system_updatenotification (3.5.0) 1 | plg_system_weblinks (4.0.1) 0 | plg_twofactorauth_totp (3.2.0) 0 | plg_twofactorauth_yubikey (3.2.0) 0 | plg_user_contactcreator (3.0.0) 0 | plg_user_joomla (3.0.0) 1 | plg_user_profile (3.0.0) 1 | plg_user_terms (3.9.0) 0 |
3rd Party:: plg_editors_codemirror (5.60.0) 1 | plg_editors_tinymce (4.5.12) 1 | plg_installer_rsform (1.0.0) 1 | System - bo:VideoJS (1.0.0) 0 | System - RSForm! Pro Delete Submiss (1.0.0) ? | System - RSForm! Pro reCAPTCHA v2 (3.1.0) 1 |
Templates Discovered :: wrote:Templates :: Site :: beez3 (3.1.0) 1 | protostar (1.0) 1 |
Templates :: Admin :: hathor (3.0.0) 1 | isis (1.0) 1 |

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Sun Oct 02, 2022 3:53 pm

Thank you for pointing me to the SQL statements that are used to upgrade the database.

I run the following command (the command which ceford told that failed) manually on phpmyadamin:

INSERT INTO `#__extensions` (`name`, `type`, `element`, `folder`, `client_id`, `enabled`, `access`, `protected`, `manifest_cache`, `params`, `custom_data`, `checked_out`, `checked_out_time`, `ordering`, `state`) VALUES
('atum', 'template', 'atum', '', 1, 1, 1, 0, '{}', '{}', '', 0, '0000-00-00 00:00:00', 0, 0),
('cassiopeia', 'template', 'cassiopeia', '', 0, 1, 1, 0, '{}', '{}', '', 0, '0000-00-00 00:00:00', 0, 0);


The command did run without error.
After that, I did run all the other commands that are aftter that in the script “4.0.0-2018-03-05.sql” (the script that failed according to “joomla_update.php“.

They all run w/o error except the following:
-- From 4.0.0-2017-06-03.sql
-- The following two statements were modified for 4.1.1 by adding the "/** CAN FAIL **/" installer hint.
-- See https://github.com/joomla/joomla-cms/pull/37156
ALTER TABLE `wnspl_extensions` ADD COLUMN `changelogurl` text AFTER `element` /** CAN FAIL **/;


The error message was:

MySQL meldet: Dokumentation
#1067 - Fehlerhafter Vorgabewert (DEFAULT) für 'checked_out_time'

In the comments is written that these command could fail, so no problem.

After I run the afore-said script, the menu of the back-end looked much better.See attachment.

Maybe the computing of the scripts stopped because of the above error?

What is the next script that should be run?
You do not have the required permissions to view the files attached to this post.

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Mon Oct 03, 2022 9:16 am

Sorry guys, I had a cross-postiing that I didn't mention in the German forum. I closed the German thread.

If I set (in php.ini) "$debug = '1';" and "$error_reporting = 'maximum';" then I get, when loging into the backend then the following call stack is displayed:

An error has occurred.
500 Unknown column 'fp.featured_up' in 'field list'
Call stack
# Function Location
1 () JROOT\administrator\modules\mod_latest\src\Helper\LatestHelper.php:89
2 Joomla\Module\Latest\Administrator\Helper\LatestHelper::getList() JROOT\administrator\modules\mod_latest\mod_latest.php:19
3 include() JROOT\libraries\src\Dispatcher\ModuleDispatcher.php:52
4 Joomla\CMS\Dispatcher\ModuleDispatcher::Joomla\CMS\Dispatcher\{closure}() JROOT\libraries\src\Dispatcher\ModuleDispatcher.php:55
5 Joomla\CMS\Dispatcher\ModuleDispatcher->dispatch() JROOT\libraries\src\Helper\ModuleHelper.php:281
6 Joomla\CMS\Helper\ModuleHelper::renderRawModule() JROOT\libraries\src\Helper\ModuleHelper.php:161
7 Joomla\CMS\Helper\ModuleHelper::renderModule() JROOT\administrator\components\com_cpanel\tmpl\cpanel\default.php:61
8 include() JROOT\libraries\src\MVC\View\HtmlView.php:410
9 Joomla\CMS\MVC\View\HtmlView->loadTemplate() JROOT\libraries\src\MVC\View\HtmlView.php:203
10 Joomla\CMS\MVC\View\HtmlView->display() JROOT\administrator\components\com_cpanel\src\View\Cpanel\HtmlView.php:156
11 Joomla\Component\Cpanel\Administrator\View\Cpanel\HtmlView->display() JROOT\libraries\src\MVC\Controller\BaseController.php:639
12 Joomla\CMS\MVC\Controller\BaseController->display() JROOT\administrator\components\com_cpanel\src\Controller\DisplayController.php:56
13 Joomla\Component\Cpanel\Administrator\Controller\DisplayController->display() JROOT\libraries\src\MVC\Controller\BaseController.php:672
14 Joomla\CMS\MVC\Controller\BaseController->execute() JROOT\libraries\src\Dispatcher\ComponentDispatcher.php:143
15 Joomla\CMS\Dispatcher\ComponentDispatcher->dispatch() JROOT\libraries\src\Component\ComponentHelper.php:355
16 Joomla\CMS\Component\ComponentHelper::renderComponent() JROOT\libraries\src\Application\AdministratorApplication.php:143
17 Joomla\CMS\Application\AdministratorApplication->dispatch() JROOT\libraries\src\Application\AdministratorApplication.php:186
18 Joomla\CMS\Application\AdministratorApplication->doExecute() JROOT\libraries\src\Application\CMSApplication.php:294
19 Joomla\CMS\Application\CMSApplication->execute() JROOT\administrator\includes\app.php:61
20 require_once() JROOT\administrator\index.php:32

User avatar
ceford
Joomla! Ace
Joomla! Ace
Posts: 1381
Joined: Mon Feb 24, 2014 10:38 pm
Location: Edinburgh, Scotland
Contact:

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by ceford » Mon Oct 03, 2022 9:42 am

This is no surprise because hardly any of the 400 sql statements were run during your update. I don't know if this will do any good but if you can navigate to System / Database you might be able to select Joomla CMS and select the Update Structure button.

Probably best to delete everything (files and database tables), restore your backup and try again.

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Mon Oct 03, 2022 5:55 pm

I deleted everything and did it again but same result.
The last entry in the loge file is:
2022-10-01T16:56:42+00:00 INFO ::1 update Ran query from file 4.0.0-2018-03-05. Query text: INSERT INTO `#__extensions` (`name`, `type`, `element`, `folder`, `client_id`, `.
In the log file there is not more information what the reason is why the querry/update stops.
Is there maybe a trace log that I have to switch on or something else to find out why it stops?

User avatar
ceford
Joomla! Ace
Joomla! Ace
Posts: 1381
Joined: Mon Feb 24, 2014 10:38 pm
Location: Edinburgh, Scotland
Contact:

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by ceford » Mon Oct 03, 2022 7:00 pm

Go back to your backup and disable all third party plugins before starting the upgrade process. Look in the error logs if it fails again, this one: C:\xampp\php\logs\php_error_log

I am not sure if you should set $debug = true; and $error_reporting = 'maximum'; in configuration.php. Try it both ways.

Have you tried installing a clean J.4.2.3 instance in your VM?

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Tue Oct 04, 2022 6:50 am

<<Go back to your backup and disable all third party plugins before starting the upgrade process. Look in the error logs if it fails again, this one: C:\xampp\php\logs\php_error_log<<
Didn’t help The result is the same.
I have no file “php_error_log” on the whole drive C…
I have not changed any settings of XAMPP at all. I took a clean and fresh Win11 VM, installed latest XAMPP and then “installed” my J3 site with Akeeba…

<<I am not sure if you should set $debug = true; and $error_reporting = 'maximum'; in configuration.php. Try it both ways.<<
I did set above parameters but no additional information generated…

<<Have you tried installing a clean J.4.2.3 instance in your VM?<<
Yep, works like a charm.

I am losing my illusions about open source….

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Tue Oct 04, 2022 7:20 am

In my opinion, it is a database issue.
The problem is when running the following two following SQL INSERT statements:

Insert #1:
INSERT INTO `#__extensions` (`name`, `type`, `element`, `folder`, `client_id`, `enabled`, `access`, `protected`, `manifest_cache`, `params`, `custom_data`, `checked_out`, `checked_out_time`, `ordering`, `state`) VALUES
('atum', 'template', 'atum', '', 1, 1, 1, 0, '{}', '{}', '', 0, '0000-00-00 00:00:00', 0, 0),
('cassiopeia', 'template', 'cassiopeia', '', 0, 1, 1, 0, '{}', '{}', '', 0, '0000-00-00 00:00:00', 0, 0);

Insert #2:
INSERT INTO `#__template_styles` (`template`, `client_id`, `home`, `title`, `inheritable`, `parent`, `params`) VALUES
('atum', 1, (CASE WHEN (SELECT b.`count` FROM (SELECT count(a.`id`) AS `count` FROM `#__template_styles` a WHERE a.`home` = '1' AND a.`client_id` = 1 AND a.`template` IN ('isis', 'hathor')) AS b) = 0 THEN '0' ELSE '1' END), 'atum - Default', 1, '', '{}'),
('cassiopeia', 0, (CASE WHEN (SELECT d.`count` FROM (SELECT count(c.`id`) AS `count` FROM `#__template_styles` c WHERE c.`home` = '1' AND c.`client_id` = 0 AND c.`template` IN ('protostar', 'beez3')) AS d) = 0 THEN '0' ELSE '1' END), 'cassiopeia - Default', 1, '', '{}');

Insert #1 is executed, the two new data sets “atum” and “cassiopeia” are present in the table “#__extensions” afterwards (not present before upgrade).

Insert #2 is not executed, the two new data sets “atum” and “cassiopeia” have not been added to the table “`#__template_styles” afterwards.

The question is why is the insert #2 is not executed (which subsequently stops the entire upgrade process of the database)?

I deleted the two new data sets “atum” and “cassiopeia” and then did run the insert #1 manually with phpMyAdmin. The insert works with two warnings:
Warning: #1264 Out of range value for column 'checked_out_time' at row 1.
Warning: #1264 Out of range value for column 'checked_out_time' at row 2.
A real error is not thrown, but a warning. It seems that this is sufficient to stop the upgrade process. I wonder if there is “hidden” switch to tell the system to ignore warnings or even “errors”

User avatar
ceford
Joomla! Ace
Joomla! Ace
Posts: 1381
Joined: Mon Feb 24, 2014 10:38 pm
Location: Edinburgh, Scotland
Contact:

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by ceford » Tue Oct 04, 2022 8:39 am

I think the problem is in the date format in insert #1: '0000-00-00 00:00:00'

The warning is coming from MySQL/MariaDB and I guess for most of us warnings are switched off but not for you. So the warning is fed back to Joomla which takes it as an indication that something has gone wrong and aborts.

I am really clutching at straws here: look for a way to switch off MariaDB warnings.

Anyone else know something about this?

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Tue Oct 04, 2022 9:20 am

I changed in my.sql the setting from

sql_mode=NO_ZERO_IN_DATE,NO_ZERO_DATE,NO_ENGINE_SUBSTITUTION

to

sql_mode=NO_ENGINE_SUBSTITUTION

did not help

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Wed Oct 05, 2022 2:38 pm

I deinstalled ALL extensions to have only extensions from Joomla.
Upgrade still fails...
What should I do now?

User avatar
ceford
Joomla! Ace
Joomla! Ace
Posts: 1381
Joined: Mon Feb 24, 2014 10:38 pm
Location: Edinburgh, Scotland
Contact:

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by ceford » Wed Oct 05, 2022 4:14 pm

I agree it is a database problem - returning an error or warning will break the script. I looked at this:

https://mariadb.com/kb/en/sql-mode/

but did not see any way to disable the warning.

As a test with phpMyAdmin, take your insert #2 statements and try with '0000-00-00 00:00:00' changed to NULL (not quoted)

Do you still get the Warning: #1264 message?

Also you could try with INSERT IGNORE INTO ... but that would be more of a problem to fix globally.

I read somewhere recently that MariaDb is increasingly diverging from MySQL - it could be Joomla needs a fix to solve this problem.

A potential workaround: download the update file, unzip it in a temporary location, change those '0000-...' dates to NULL in all of the SQL files, compress the files to recreate the zip, and use the upload method to do the update. I have no idea if this will work!

User avatar
ceford
Joomla! Ace
Joomla! Ace
Posts: 1381
Joined: Mon Feb 24, 2014 10:38 pm
Location: Edinburgh, Scotland
Contact:

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by ceford » Wed Oct 05, 2022 7:34 pm


cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Thu Oct 06, 2022 12:27 pm

Hi,

<<As a test with phpMyAdmin, take your insert #2 statements and try with '0000-00-00 00:00:00' changed to NULL (not quoted)
Do you still get the Warning: #1264 message?<<
Then I get error „#1048“ „Field 'checked_out_time' is not allowed to be NULL.

<<A potential workaround: download the update file, unzip it in a temporary location, change those '0000-...' dates to NULL in all of the SQL files, compress the files to recreate the zip, and use the upload method to do the update. I have no idea if this will work!<<
This leads to error 1264, see above.
I did something different, I substituted '0000-...' with ''. Same result.

User avatar
ceford
Joomla! Ace
Joomla! Ace
Posts: 1381
Joined: Mon Feb 24, 2014 10:38 pm
Location: Edinburgh, Scotland
Contact:

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by ceford » Thu Oct 06, 2022 2:51 pm

You could change the dates to 1971-01-01 00:00:00

Try and report back.

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Fri Oct 07, 2022 3:10 pm

Hi, just tried that, unfortunately, same result... :-(

cjweiland
Joomla! Apprentice
Joomla! Apprentice
Posts: 14
Joined: Sat Oct 01, 2022 5:02 pm

Re: Menu problem after upgrade from 3.10 to 4.2.3

Post by cjweiland » Wed Oct 26, 2022 5:04 am

Hi ceford, thanks a lot for your help!

Unfortunately, upgrade is not possible and the site has to recreated from scratch and the old content imported.

In the light of the late problems, we will do that using Wordpress.

Joomla seems no to be the right product for us...


Post Reply

Return to “Migrating and Upgrading to Joomla! 4.x”