Advertisement
Extreme Failure updating from J3.10.12t to J4.4
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.
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.
-
- Joomla! Apprentice
- Posts: 11
- Joined: Fri Aug 30, 2024 9:44 am
Extreme Failure updating from J3.10.12t to J4.4
I find myself in a bit of an issue. I took over a company website that was handled by an agency until not long ago. We wanted to finally update it to Joomla 4 like we did for all our other websites with no issue.
I took a backup using Akeeba, installed it on a local MAMP, tested the update after removing extensions that wouldn't work or updating the ones that needed to be compatible. The upgrade worked perfectly on the local installation.
I felt confident doing it on the live site, following the same steps: update/removal for extensions that needed it, fixed the database which required it, checked the PHP requirements. Once i started the update to J4.4 at around 70% i got a warning of failed checksum and then the website completely crashed, giving a 500 Unknown column 'fp.featured_up' in 'field list' error.
I panicked then restored the backup I had taken for the local test, since it was only 2 days old, and the website was restored.
Today I checked again what the Joomla Update tab was telling me and again I noticed database warnings that needed fix. Only this time when I went to Extensions -> Manage-> Database and did a Fix like it was recommended, the site crashed again.
Here's where I think something went wrong now: I restored the same backup once again, because it's a live site that is needed for work, but I simply put the kickstart installer and backup archive in the folder without deleting the files. This has usually worked in the past, but now I'm wondering if it was very stupid because the front end of the site was restored, however the backend keeps giving me a series of errors like "0 Class "JFormFieldList" not found"
and doesn't load anything.
Current PHP version is 8.0, we did not have FPA installed
I took a backup using Akeeba, installed it on a local MAMP, tested the update after removing extensions that wouldn't work or updating the ones that needed to be compatible. The upgrade worked perfectly on the local installation.
I felt confident doing it on the live site, following the same steps: update/removal for extensions that needed it, fixed the database which required it, checked the PHP requirements. Once i started the update to J4.4 at around 70% i got a warning of failed checksum and then the website completely crashed, giving a 500 Unknown column 'fp.featured_up' in 'field list' error.
I panicked then restored the backup I had taken for the local test, since it was only 2 days old, and the website was restored.
Today I checked again what the Joomla Update tab was telling me and again I noticed database warnings that needed fix. Only this time when I went to Extensions -> Manage-> Database and did a Fix like it was recommended, the site crashed again.
Here's where I think something went wrong now: I restored the same backup once again, because it's a live site that is needed for work, but I simply put the kickstart installer and backup archive in the folder without deleting the files. This has usually worked in the past, but now I'm wondering if it was very stupid because the front end of the site was restored, however the backend keeps giving me a series of errors like "0 Class "JFormFieldList" not found"
and doesn't load anything.
Current PHP version is 8.0, we did not have FPA installed
Advertisement
- toivo
- Joomla! Master
- Posts: 17789
- Joined: Thu Feb 15, 2007 5:48 am
- Location: Sydney, Australia
Re: Extreme Failure updating from J3.10.12t to J4.4
Your gut feeling is correct. It is necessary to restore into an empty folder. Otherwise the results are unpredictable because of the mixture of files and folders from different versions.
Toivo Talikka, Global Moderator
- Webdongle
- Joomla! Master
- Posts: 44567
- Joined: Sat Apr 05, 2008 9:58 pm
Re: Extreme Failure updating from J3.10.12t to J4.4
Akeeba backup needs to be restored to an empty folder and empty database. Do you have access to a machine with windows OS. If you have you could try wamp https://wampserver.aviatechno.net/ . With wamp you can have several versions of Joomla (just create seperate folders in wamp's /www folder). You can also change php versions on the fly. Also, when installing the backup (or installing Joomla), the install auto creates the backup.
Running the fpa on the live site as well as the test site would be helpful.
Running the fpa on the live site as well as the test site would be helpful.
http://www.weblinksonline.co.uk/
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
-
- Joomla! Apprentice
- Posts: 11
- Joined: Fri Aug 30, 2024 9:44 am
Re: Extreme Failure updating from J3.10.12t to J4.4
So what could I do now? I have access to both hosting, database and ftp folders, but this is getting close to the end of my knowledge.
Joomla is installed in a public_html folder, could I simply delete all files from the folder and install the backup again?
The database is what stumps me, can I just create a new one, restore the backup connecting to that one and delete the old one?
Please excuse me if they are stupid questions, I just would like not be yelled at by a superior and I don't want to cause further issues.
-
- Joomla! Apprentice
- Posts: 11
- Joined: Fri Aug 30, 2024 9:44 am
Re: Extreme Failure updating from J3.10.12t to J4.4
I can use WAMP but I don't understand what that would do, sorry. The local installation had no issue, it's the live one that failed multiple times...Webdongle wrote: ↑Fri Aug 30, 2024 10:28 am Akeeba backup needs to be restored to an empty folder and empty database. Do you have access to a machine with windows OS. If you have you could try wamp https://wampserver.aviatechno.net/ . With wamp you can have several versions of Joomla (just create seperate folders in wamp's /www folder). You can also change php versions on the fly. Also, when installing the backup (or installing Joomla), the install auto creates the backup.
Running the fpa on the live site as well as the test site would be helpful.
I will try to install and run fpa and post the results, as long as that doesn't end up breaking something else. At the moment the website is visible to viewers which is the good thing, although I don't understand why that works but not the backend
- Webdongle
- Joomla! Master
- Posts: 44567
- Joined: Sat Apr 05, 2008 9:58 pm
Re: Extreme Failure updating from J3.10.12t to J4.4
Yes delete the folders/files. With the database, use phpMyAdmin to edit. Select all and 'Drop' with selected.
http://www.weblinksonline.co.uk/
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
-
- Joomla! Apprentice
- Posts: 11
- Joined: Fri Aug 30, 2024 9:44 am
Re: Extreme Failure updating from J3.10.12t to J4.4
I feel a bit silly even asking but better safe than sorry: will the Drop option completely delete the database and eliminate the issue? I'm assuming I should do this before/at the same time as deleting the folders/files where joomla is installed and then restore the backup as usual, selecting that same database?
Thank you for your help so far.
-
- Joomla! Champion
- Posts: 6348
- Joined: Tue Aug 23, 2005 1:56 pm
- Location: South coast, UK
- Contact:
Re: Extreme Failure updating from J3.10.12t to J4.4
The drop option empties the DB not delete it. Once you have dropped all content from The DB it should be good to reuse.
https://gadsolutions.biz Electrical services
https://electrical-testing-safety.co.uk Testing services
https://electrical-testing-safety.co.uk Testing services
- toivo
- Joomla! Master
- Posts: 17789
- Joined: Thu Feb 15, 2007 5:48 am
- Location: Sydney, Australia
Re: Extreme Failure updating from J3.10.12t to J4.4
Just noticed this question. The public_html folder could have other files, installed by your host. If your cPanel or a similar page provided by your host has the option to create a new folder inside public_html, install Joomla into public_html/mysite and set the Document Root of your domain to point to that folder. It will then be easier to maintain each instance of Joomla in a separate folder, especially if you would like to have a development site in a subdomain like test.example.com.
Toivo Talikka, Global Moderator
-
- Joomla! Apprentice
- Posts: 11
- Joined: Fri Aug 30, 2024 9:44 am
Re: Extreme Failure updating from J3.10.12t to J4.4
Coming back after the weekend.
It seems like the db is definitely screwed up, although I can't say for sure if it happened during the first update to J4 or the second time when I tried to fix the database after the backup. The number of tables in the live database is different than the ones in the backup.
From what I can see on the local installation, there seems to be some obsolete files from J2.5 still there; I see from the migration docs that you're supposed to clean up PKG_JOOMLA, however it won't let me do it. However I can use "fix database" on the local installation resulting in no issue.
The only difference between the dev environment and the live one is the phpmyadmin version, the local one is 5.2 and live one is 4.9.7; it also says the PHP version is 7.4.29 compared to the 8.0.3 that is selected.
I don't know if these things made the live website behave differently on upgrade compared to the local one, but at this point I don't know if emptying the DB and the files and install the back up will solve the issue.
It seems like the db is definitely screwed up, although I can't say for sure if it happened during the first update to J4 or the second time when I tried to fix the database after the backup. The number of tables in the live database is different than the ones in the backup.
From what I can see on the local installation, there seems to be some obsolete files from J2.5 still there; I see from the migration docs that you're supposed to clean up PKG_JOOMLA, however it won't let me do it. However I can use "fix database" on the local installation resulting in no issue.
The only difference between the dev environment and the live one is the phpmyadmin version, the local one is 5.2 and live one is 4.9.7; it also says the PHP version is 7.4.29 compared to the 8.0.3 that is selected.
I don't know if these things made the live website behave differently on upgrade compared to the local one, but at this point I don't know if emptying the DB and the files and install the back up will solve the issue.
-
- Joomla! Apprentice
- Posts: 11
- Joined: Fri Aug 30, 2024 9:44 am
Re: Extreme Failure updating from J3.10.12t to J4.4
Yes comparing to the backup it seems to have other files than just joomla folders, because from the ftp i see 3 folders i don't have on the backup; i'm assuming it's left over from when the website was managed by the agency, but without knowing what it is I wouldn't want to touch them. Thank you for the advice, I will try to see how to change the document root.toivo wrote: ↑Mon Sep 02, 2024 11:43 amJust noticed this question. The public_html folder could have other files, installed by your host. If your cPanel or a similar page provided by your host has the option to create a new folder inside public_html, install Joomla into public_html/mysite and set the Document Root of your domain to point to that folder. It will then be easier to maintain each instance of Joomla in a separate folder, especially if you would like to have a development site in a subdomain like test.example.com.
- Webdongle
- Joomla! Master
- Posts: 44567
- Joined: Sat Apr 05, 2008 9:58 pm
Re: Extreme Failure updating from J3.10.12t to J4.4
Follow
User avatar
User avatar
toivo's instructions
User avatar
User avatar
toivo's instructions
http://www.weblinksonline.co.uk/
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
-
- Joomla! Apprentice
- Posts: 11
- Joined: Fri Aug 30, 2024 9:44 am
Re: Extreme Failure updating from J3.10.12t to J4.4
I managed to replicate the error in a local environment and here's the FPA result ( the order of things: tried update from J.3.10.12 to J4.4.8 -> i'm assuming that the database schema didn't fix correctly and got a Error 500-> restored backup -> tried to fix database again -> bunch of errors -> frontend is visible but backend is broken)
I will follow the instructions given by the users before, but if anyone notices other errors, I'd be happy to hear it. SSL is not enabled because of the local environment, live site is enabled.
I will follow the instructions given by the users before, but if anyone notices other errors, I'd be happy to hear it. SSL is not enabled because of the local environment, live site is enabled.
Forum Post Assistant (v1.6.7) : 4-Sep-2024 wrote:Last PHP Error(s) Reported :: wrote:[04-Sep-2024 09:02:34 UTC] PHP Warning: foreach() argument must be of type array|object, bool given in /Applications/MAMP/htdocs/localtest/administrator/components/com_content/src/Model/ArticlesModel.php on line 650Basic Environment :: wrote:Joomla! Instance :: Joomla! 3.10.12-Stable (Daraja) 8-July-2023
Joomla! Platform :: Joomla Platform 13.1.0-Stable (Curiosity) 24-Apr-2013
Joomla! Configured :: Yes | Writable (644) |
Configuration Options :: Offline: false | SEF: true | SEF Suffix: false | SEF ReWrite: true | .htaccess/web.config: Yes | GZip: false | Cache: false | CacheTime: 15 | CacheHandler: file | CachePlatformPrefix: false | FTP Layer: false | Proxy: false | LiveSite: | Session lifetime: 15 | 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.12: Yes | Database Supports J! 3.10.12: Yes | Database Credentials Present: Yes |
Host Configuration :: OS: Darwin | OS Version: 21.6.0 | Technology: x86_64 | Web Server: Apache/2.4.54 (Unix) OpenSSL/1.0.2u PHP/8.0.3 mod_wsgi/3.5 Python/2.7.18 mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_perl/2.0.11 Perl/v5.30.1 | Encoding: gzip, deflate, br, zstd | System TMP Writable: Yes | Free Disk Space : 67.15 GiB |
PHP Configuration :: Version: 8.0.3 | PHP API: apache2handler | Session Path Writable: Yes | Display Errors: 0 | Error Reporting: 32767 | Log Errors To: /Applications/MAMP/logs/php_error.log | Last Known Error: 04th September 2024 09:02:34. | Register Globals: | Magic Quotes: | Safe Mode: | Allow url fopen: 1 | Open Base: | Uploads: 1 | Max. Upload Size: 32M | Max. POST Size: 8M | Max. Input Time: 60 | Max. Execution Time: 30 | Memory Limit: 128M
Database Configuration :: Version: 5.7.39 (Client:mysqlnd 8.0.3) | Database Size: 12.16 MiB | #of Tables with config prefix: 96 | #of other Tables: 0 | User Privileges : GRANT ALLDetailed Environment :: wrote:PHP Extensions :: Core (8.0.3) | date (8.0.3) | libxml (8.0.3) | openssl (8.0.3) | pcre (8.0.3) | sqlite3 (8.0.3) | zlib (8.0.3) | bcmath (8.0.3) | bz2 (8.0.3) | calendar (8.0.3) | ctype (8.0.3) | curl (8.0.3) | dom (20031129) | hash (8.0.3) | fileinfo (8.0.3) | filter (8.0.3) | ftp (8.0.3) | gd (8.0.3) | gettext (8.0.3) | SPL (8.0.3) | iconv (8.0.3) | intl (8.0.3) | json (8.0.3) | ldap (8.0.3) | mbstring (8.0.3) | session (8.0.3) | standard (8.0.3) | mysqlnd (mysqlnd 8.0.3) | PDO (8.0.3) | pdo_mysql (8.0.3) | pdo_sqlite (8.0.3) | Phar (8.0.3) | posix (8.0.3) | Reflection (8.0.3) | mysqli (8.0.3) | SimpleXML (8.0.3) | soap (8.0.3) | sockets (8.0.3) | sodium (8.0.3) | exif (8.0.3) | tokenizer (8.0.3) | xml (8.0.3) | xmlreader (8.0.3) | xmlwriter (8.0.3) | xsl (8.0.3) | zip (1.19.2) | apache2handler (8.0.3) | imap (8.0.3) | pgsql (8.0.3) | pdo_pgsql (8.0.3) | Zend Engine (4.0.3) |
Potential Missing Extensions ::
Switch User Environment :: PHP CGI: No | Server SU: No | PHP SU: No | Potential Ownership Issues: No
Apache Modules :: core | mod_so | http_core | mod_ssl | prefork | mod_access_compat | mod_actions | mod_alias | mod_allowmethods | mod_auth_basic | mod_auth_digest | mod_auth_form | mod_authn_anon | mod_authn_core | mod_authn_dbd | mod_authn_dbm | mod_authn_file | mod_authn_socache | mod_authz_core | mod_authz_dbd | mod_authz_dbm | mod_authz_groupfile | mod_authz_host | mod_authz_owner | mod_authz_user | mod_autoindex | mod_bucketeer | mod_buffer | mod_cache | mod_case_filter_in | mod_case_filter | mod_cern_meta | mod_cgi | mod_cgid | mod_charset_lite | mod_dav | mod_dbd | mod_deflate | mod_dir | mod_dumpio | mod_echo | mod_env | mod_expires | mod_ext_filter | mod_fastcgi | mod_file_cache | mod_filter | mod_headers | mod_http2 | mod_include | mod_info | mod_lbmethod_bybusyness | mod_lbmethod_byrequests | mod_lbmethod_bytraffic | mod_log_config | mod_log_debug | mod_logio | mod_macro | mod_mime_magic | mod_mime | mod_negotiation | mod_perl | mod_proxy | mod_ratelimit | mod_remoteip | mod_reqtimeout | mod_request | mod_rewrite | mod_sed | mod_session | mod_setenvif | mod_slotmem_shm | mod_socache_dbm | mod_socache_memcache | mod_socache_shmcb | mod_speling | mod_status | mod_substitute | mod_unixd | mod_userdir | mod_usertrack | mod_version | mod_vhost_alias | mod_watchdog | mod_wsgi | mod_xsendfile | mod_php | Apache/2.4.54 (Unix) OpenSSL/1.0.2u PHP/8.0.3 mod_wsgi/3.5 Python/2.7.18 mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_perl/2.0.11 Perl/v5.30.1 |
Potential Missing Modules ::
Folder Permissions :: wrote:Core Folders :: images/ (755) | components/ (755) | modules/ (755) | plugins/ (755) | language/ (755) | templates/ (755) | cache/ (755) | logs/ (755) | tmp/ (755) | administrator/components/ (755) | administrator/modules/ (755) | administrator/language/ (755) | administrator/templates/ (755) | administrator/logs/ (755) |
Elevated Permissions (First 10) ::Database Information :: wrote:Database statistics :: Uptime: 88592 | Threads: 1 | Questions: 26371 | Slow queries: 0 | Opens: 1573 | Flush tables: 1 | Open tables: 597 | Queries per second avg: 0.297 |Extensions Discovered :: wrote:Components :: Site ::
Core :: com_mailto (3.0.0) 1 | com_wrapper (3.0.0) 1 |
3rd Party::
Components :: Admin ::
Core :: com_checkin (3.0.0) 1 | com_modules (3.0.0) 1 | com_scheduler (4.1.0) ? | com_redirect (3.0.0) 1 | com_admin (3.0.0) 1 | com_workflow (4.0.0) ? | com_cpanel (3.0.0) 1 | com_mails (4.0.0) ? | com_config (3.0.0) 1 | com_cache (3.0.0) 1 | com_actionlogs (3.9.0) 1 | com_plugins (3.0.0) 1 | com_categories (3.0.0) 1 | com_installer (3.0.0) 1 | com_media (3.0.0) 1 | com_ajax (3.2.0) 1 | com_banners (3.0.0) 1 | com_newsfeeds (3.0.0) 1 | com_postinstall (3.2.0) 1 | com_messages (3.0.0) 1 | com_login (3.0.0) 1 | com_content (3.0.0) 1 | com_languages (3.0.0) 1 | com_search (3.0.0) 1 | com_tags (3.1.0) 1 | com_joomlaupdate (3.10.1) 1 | com_guidedtours (4.3.0) ? | com_associations (3.7.0) 1 | com_wrapper (4.0.0) 1 | com_contenthistory (3.2.0) 1 | com_menus (3.0.0) 1 | com_fields (3.7.0) 1 | com_users (3.0.0) 1 | com_finder (4.0.0) ? | com_privacy (3.9.0) 1 | com_templates (3.0.0) 1 |
3rd Party:: Akeeba (8.3.3) 1 |
Modules :: Site ::
Core :: mod_tags_similar (3.1.0) 1 | mod_random_image (3.0.0) 1 | mod_syndicate (3.0.0) 1 | mod_wrapper (3.0.0) 1 | mod_breadcrumbs (3.0.0) 1 | mod_articles_archive (3.0.0) 1 | mod_banners (3.0.0) 1 | mod_footer (3.0.0) 1 | mod_menu (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_articles_categories (3.0.0) 1 | mod_languages (3.5.0) 1 | mod_articles_latest (3.0.0) 1 | mod_whosonline (3.0.0) 1 | mod_login (3.0.0) 1 | mod_stats (3.0.0) 1 | mod_articles_category (3.0.0) 1 | mod_custom (3.0.0) 1 | mod_articles_news (3.0.0) 1 | mod_related_items (3.0.0) 1 | mod_finder (3.0.0) ? | mod_tags_popular (3.1.0) 1 | mod_users_latest (3.0.0) 1 | mod_search (3.0.0) 1 | mod_articles_popular (3.0.0) 1 |
3rd Party:: Builder (2.3.15) 1 |
Modules :: Admin ::
Core :: mod_quickicon (3.0.0) 1 | mod_latest (3.0.0) 1 | mod_status (3.0.0) 1 | mod_multilangstatus (3.0.0) 1 | mod_post_installation_messages (4.0.0) ? | mod_privacy_dashboard (3.9.0) 1 | mod_privacy_status (4.0.0) ? | mod_toolbar (3.0.0) 1 | mod_stats_admin (3.0.0) 1 | mod_sampledata (3.8.0) 1 | mod_menu (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_title (3.0.0) 1 | mod_guidedtours (4.3.0) ? | mod_version (3.0.0) 1 | mod_popular (3.0.0) 1 | mod_latestactions (3.9.0) 1 | mod_login (3.0.0) 1 | mod_user (4.0.0) ? | mod_custom (3.0.0) 1 | mod_logged (3.0.0) 1 | mod_submenu (3.0.0) 1 | mod_loginsupport (4.0.0) ? | mod_frontend (4.0.0) ? | mod_messages (4.0.0) ? |
3rd Party:: MOD_YOOTHEME_LINK (4.4.8) ? |
Libraries ::
Core ::
3rd Party:: file_fof30 (3.6.2) ? | file_fof40 (4.1.3) ? |
Plugins ::
Core :: plg_quickicon_joomlaupdate (3.0.0) 1 | plg_quickicon_privacycheck (3.9.0) 1 | plg_quickicon_downloadkey (4.0.0) ? | plg_quickicon_overridecheck (4.0.0) ? | plg_quickicon_phpversioncheck (3.7.0) 1 | plg_quickicon_eos310 (3.10.0) 1 | plg_quickicon_extensionupdate (3.0.0) 1 | plg_quickicon_eos (4.4.0) ? | plg_webservices_messages (4.0.0) ? | plg_webservices_privacy (4.0.0) ? | plg_webservices_config (4.0.0) ? | plg_webservices_plugins (4.0.0) ? | plg_webservices_content (4.0.0) ? | plg_webservices_banners (4.0.0) ? | plg_webservices_languages (4.0.0) ? | plg_webservices_tags (4.0.0) ? | plg_webservices_users (4.0.0) ? | plg_webservices_redirect (4.0.0) ? | plg_webservices_menus (4.0.0) ? | plg_webservices_templates (4.0.0) ? | plg_webservices_modules (4.0.0) ? | plg_webservices_installer (4.0.0) ? | plg_webservices_newsfeeds (4.0.0) ? | plg_webservices_media (4.1.0) ? | plg_extension_namespacemap (4.0.0) ? | plg_extension_finder (4.0.0) ? | plg_extension_joomla (3.0.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_privacy_actionlogs (3.9.0) 1 | plg_sampledata_multilang (4.0.0) ? | plg_api-authentication_token (4.0.0) ? | plg_api-authentication_basic (4.0.0) ? | plg_twofactorauth_yubikey (3.2.0) 0 | plg_twofactorauth_totp (3.2.0) 0 | plg_media-action_rotate (4.0.0) ? | plg_media-action_crop (4.0.0) ? | plg_media-action_resize (4.0.0) ? | plg_content_vote (3.0.0) 1 | plg_content_emailcloak (3.0.0) 1 | plg_content_confirmconsent (3.9.0) 0 | plg_content_pagenavigation (3.0.0) 0 | plg_content_finder (3.0.0) ? | plg_content_fields (3.7.0) 1 | plg_content_pagebreak (3.0.0) 1 | plg_content_loadmodule (3.0.0) 1 | plg_content_joomla (3.0.0) 1 | plg_user_token (3.9.0) ? | plg_user_contactcreator (3.0.0) 0 | plg_user_terms (3.9.0) 0 | plg_user_profile (3.0.0) 0 | plg_user_joomla (3.0.0) 1 | plg_filesystem_local (4.0.0) ? | plg_multifactorauth_yubikey (3.2.0) ? | plg_multifactorauth_fixed (4.2.0) ? | plg_multifactorauth_webauthn (4.2.0) ? | plg_multifactorauth_totp (3.2.0) ? | plg_multifactorauth_email (4.2.0) ? | plg_captcha_recaptcha_invisible (3.8) 0 | plg_captcha_recaptcha (3.4.0) 1 | plg_search_contacts (3.0.0) 1 | plg_search_content (3.0.0) 1 | plg_search_tags (3.0.0) 0 | plg_search_categories (3.0.0) 1 | plg_search_newsfeeds (3.0.0) 1 | plg_system_sessiongc (3.8.6) 1 | plg_system_shortcut (4.2.0) ? | plg_system_cache (3.0.0) 0 | plg_system_task_notification (4.1) ? | plg_system_logrotation (3.9.0) 1 | plg_system_highlight (3.0.0) 1 | plg_system_updatenotification (3.5.0) ? | plg_system_guidedtours (4.3.0) ? | plg_system_privacyconsent (3.9.0) 0 | plg_system_p3p (3.0.0) 1 | plg_system_logout (3.0.0) 1 | plg_system_languagecode (3.0.0) 0 | plg_system_httpheaders (4.0.0) ? | plg_system_languagefilter (3.0.0) 0 | plg_system_webauthn (4.0.0) ? | plg_system_redirect (3.0.0) 1 | plg_system_schedulerunner (4.1) ? | plg_system_jooa11y (4.2.0) ? | plg_system_log (3.0.0) 1 | plg_system_fields (3.7.0) 1 | plg_system_skipto (4.0.0) ? | plg_system_remember (3.0.0) 1 | plg_system_sef (3.0.0) 1 | plg_system_accessibility (4.0.0) ? | plg_system_stats (3.5.0) ? | PLG_SYSTEM_ACTIONLOGS (3.9.0) 0 | plg_system_debug (3.0.0) 0 | plg_finder_contacts (3.0.0) ? | plg_finder_content (3.0.0) ? | plg_finder_tags (3.0.0) ? | plg_finder_categories (3.0.0) ? | plg_finder_newsfeeds (3.0.0) ? | plg_workflow_publishing (4.0.0) ? | plg_workflow_notification (4.0.0) ? | plg_workflow_featuring (4.0.0) ? | plg_task_requests (4.1) ? | plg_task_site_status (4.1) ? | plg_task_demo_tasks (4.1) ? | plg_task_check_files (4.1) ? | PLG_ACTIONLOG_JOOMLA (3.9.0) 1 | plg_editors-xtd_module (3.5.0) ? | plg_editors-xtd_image (3.0.0) 1 | plg_editors-xtd_menu (3.7.0) 1 | plg_editors-xtd_readmore (3.0.0) 1 | plg_editors-xtd_fields (3.7.0) 1 | plg_editors-xtd_pagebreak (3.0.0) 1 | plg_editors-xtd_article (3.0.0) 1 | plg_fields_imagelist (3.7.0) 1 | plg_fields_usergrouplist (3.7.0) 1 | plg_fields_calendar (3.7.0) 1 | plg_fields_radio (3.7.0) 1 | plg_fields_repeatable (3.9.0) 1 | plg_fields_color (3.7.0) 1 | plg_fields_subform (4.0.0) ? | plg_fields_user (3.7.0) 1 | plg_fields_url (3.7.0) 1 | plg_fields_checkboxes (3.7.0) 1 | plg_fields_textarea (3.7.0) 1 | plg_fields_list (3.7.0) 1 | plg_fields_integer (3.7.0) 1 | plg_fields_text (3.7.0) 1 | plg_fields_editor (3.7.0) 1 | plg_fields_media (3.7.0) 1 | plg_fields_sql (3.7.0) 1 | plg_behaviour_compat (4.4.0) ? | plg_behaviour_versionable (4.0.0) ? | plg_behaviour_taggable (4.0.0) ? | plg_installer_override (4.0.0) ? | plg_installer_packageinstaller (3.6.0) 1 | PLG_INSTALLER_FOLDERINSTALLER (3.6.0) 1 | PLG_INSTALLER_URLINSTALLER (3.6.0) 1 | plg_installer_webinstaller (2.1.2) 1 | plg_authentication_ldap (3.0.0) 0 | plg_authentication_cookie (3.0.0) 1 | plg_authentication_joomla (3.0.0) 1 | plg_authentication_gmail (3.0.0) 0 |
3rd Party:: plg_quickicon_akeebabackup (8.3.3) 0 | plg_editors_codemirror (5.60.0) 1 | plg_editors_tinymce (4.5.12) 1 | System - YOOtheme Framework (2.3.15) 1 | PLG_SYSTEM_BACKUPONUPDATE (8.3.3) 0 | PLG_SYSTEM_AKVERSIONCHECK (8.3.3) 1 | PLG_ACTIONLOG_AKEEBABACKUP (8.3.3) 0 | Fields - YOOtheme Location (4.4.8) ? | Installer - YOOtheme (1.0.7) ? |Templates Discovered :: wrote:Templates :: Site :: yootheme (2.3.15) 1 | protostar (1.0) 1 | cassiopeia (1.0) ? | beez3 (3.1.0) 1 |
Templates :: Admin :: atum (1.0) ? | hathor (3.0.0) 1 | isis (1.0) 1 |
- AMurray
- Joomla! Master
- Posts: 10196
- Joined: Sat Feb 13, 2010 7:35 am
- Location: Australia
Re: Extreme Failure updating from J3.10.12t to J4.4
This update seem to have seriously failed. FPA report shows the Joomla version as 3.10.12 but you have a mix of 3.10 and 4.x/5.x templates. Protostar, beez3,Hathor, Isis are from Joomla 3.x or earlier. Cassiopeia and Atum are J4/J5.
I don't know how you 'updated' but you should let Joomla Update take care of the full process. See https://docs.joomla.org/Joomla_3.x_to_4 ... _Migration for additional help, ensuring you have followed this to the letter.
Also the Yootheme template may have been a contributing factor - the FPA shows v2.3.15 of "Yootheme" (which I assume is "Yootheme Pro" (https://yootheme.com/page-builder) which includes the page builder and template.
Update Yootheme 2.3.15 if required (that seems to be at least 4 years out of date). The most recent release is v4.4.8 (Aug 2024), according to the Yootheme website changelog for that template (https://yootheme.com/support/yootheme-pro/changelog)).
Switch to the default template (Cassiopeia) and see if that gives you a working site, then work to fix Yootheme with an updated version if it is available or remove that completely if not.
I would restore a backup and start over, and remove Yootheme completely The compromise may be rebuilding the site after a successful update but I think the only work involved would be reconfiguring the modules to the correct template module positions.
I don't know how you 'updated' but you should let Joomla Update take care of the full process. See https://docs.joomla.org/Joomla_3.x_to_4 ... _Migration for additional help, ensuring you have followed this to the letter.
Also the Yootheme template may have been a contributing factor - the FPA shows v2.3.15 of "Yootheme" (which I assume is "Yootheme Pro" (https://yootheme.com/page-builder) which includes the page builder and template.
Update Yootheme 2.3.15 if required (that seems to be at least 4 years out of date). The most recent release is v4.4.8 (Aug 2024), according to the Yootheme website changelog for that template (https://yootheme.com/support/yootheme-pro/changelog)).
Switch to the default template (Cassiopeia) and see if that gives you a working site, then work to fix Yootheme with an updated version if it is available or remove that completely if not.
I would restore a backup and start over, and remove Yootheme completely The compromise may be rebuilding the site after a successful update but I think the only work involved would be reconfiguring the modules to the correct template module positions.
Regards - A Murray
General Support Moderator
General Support Moderator
-
- Joomla! Apprentice
- Posts: 11
- Joined: Fri Aug 30, 2024 9:44 am
Re: Extreme Failure updating from J3.10.12t to J4.4
I did update Yootheme to the latest version before trying the migration, like I did with every other extension - either I removed the ones that weren't compatible anymore or I updated them to be compatible. The version that you are now seeing is the one from the restored backup, which I had taken before updating the template or other extensions. The Joomla Update component was showing all green and only one yellow when I first tried the update (PHP Output buffering was On rather than off which I couldn't figure out how to change).AMurray wrote: ↑Sun Sep 15, 2024 5:08 am This update seem to have seriously failed. FPA report shows the Joomla version as 3.10.12 but you have a mix of 3.10 and 4.x/5.x templates. Protostar, beez3,Hathor, Isis are from Joomla 3.x or earlier. Cassiopeia and Atum are J4/J5.
I don't know how you 'updated' but you should let Joomla Update take care of the full process. See https://docs.joomla.org/Joomla_3.x_to_4 ... _Migration for additional help, ensuring you have followed this to the letter.
Also the Yootheme template may have been a contributing factor - the FPA shows v2.3.15 of "Yootheme" (which I assume is "Yootheme Pro" (https://yootheme.com/page-builder) which includes the page builder and template.
Update Yootheme 2.3.15 if required (that seems to be at least 4 years out of date). The most recent release is v4.4.8 (Aug 2024), according to the Yootheme website changelog for that template (https://yootheme.com/support/yootheme-pro/changelog)).
Switch to the default template (Cassiopeia) and see if that gives you a working site, then work to fix Yootheme with an updated version if it is available or remove that completely if not.
I would restore a backup and start over, and remove Yootheme completely The compromise may be rebuilding the site after a successful update but I think the only work involved would be reconfiguring the modules to the correct template module positions.
All other websites migrated from J3.10.12 to J4 without any issue and we use the same hosting company, PHP settings and Yootheme Pro for all of them, without any issue. The only difference with this one was that this was very old and had been initially created with J2, so my guess is that the database schema didn't fix properly (none of the other websites needed a database fix).
- AMurray
- Joomla! Master
- Posts: 10196
- Joined: Sat Feb 13, 2010 7:35 am
- Location: Australia
Re: Extreme Failure updating from J3.10.12t to J4.4
Output buffering should be settable either in your web hosting administration area or directly in the Php.ini file on your web server. Although the recommended setting is Off, it's not going to prevent the site working if it is On.
Regards - A Murray
General Support Moderator
General Support Moderator
-
- Joomla! Apprentice
- Posts: 11
- Joined: Fri Aug 30, 2024 9:44 am
Re: Extreme Failure updating from J3.10.12t to J4.4
That's what I figured, but it was pretty much the only thing showing yellow - that and to uninstall PKJ_JOOMLA which I couldn't do (figured out how later) but when i tried locally the first time the migration completed without issue even with that so my money is still on the database being the issue, but since I don't know why the database fix didn't work properly the first time but did on the local site I'm a bit wary. Will try a wipe out of the joomla files and a database drop in a new days and try to re-install the backup again and cross my fingers.
Advertisement