Upgrade from 4.2.1

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	12:00 – 16:00	10:00 – 14:00	10:00 – 14:00	9:00 – 13:00	9:00 – 13:00	-
-	17:00 – 21:00	15:00 – 19:00	15:00 – 19:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Europe/Bucharest (GMT+02:00)

Tagged: Exception

This topic contains 6 replies, has 0 voices.

Last updated by Mihai Apetrei 1 hour, 2 minutes ago.

Assisted by: Mihai Apetrei.

Author	Posts
January 17, 2025 at 1:28 pm #16606291
damirG-2	Background of the issue: I need to upgrade from WPML version 4.2.1 on my site hidden link. I want to know if there are any known issues when upgrading from this old version to the new one and the best practices to avoid issues. I plan to make a copy of my database before proceeding with the upgrade. Symptoms: No specific issue or error message mentioned. Questions: Are there any known issues when upgrading from WPML version 4.2.1 to the latest version? What is the best practice to upgrade WPML to avoid issues? Can I upgrade WPML via WP Admin?
January 17, 2025 at 3:21 pm #16607040
Mihai Apetrei Supporter Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00)	Hi there.   That is definitely a pretty old version. There are no specific issues regarding updating from this particular version. You will need first to create a full website backup and then update the WPML plugins to the latest version. Please take a look at the recommendations inside this ticket: - https://wpml.org/forums/topic/update-from-old-version  That should guide you correctly on gradually updating WPML to the latest versions. PS: Please don't forget about the backup first; that's critical when you use an older version like the one installed on your site. Kind regards, Mihai Apetrei
January 17, 2025 at 3:26 pm #16607081
damirG-2	Thanks for your reply. About this point: "I recommend that you update to each new major version (3.9, 4.0, 4.1, 4.2 and 4.3)." I have already upgrade to latest WP version, but if I upgrade from 4.2.1 to 4.6.15 by upgrading first to 4.3, 4.4, 4.5 and then 4.6, I wonder if WP will break since I am running on a new version. Thanks
January 17, 2025 at 3:35 pm #16607165
damirG-2	One more question. I suppose that I need to manually download older versions (4.3, 4.4 and 4.5) and then install by uploading the plugin? While the last 4.6 I can via WP Admin. I suppose I can also disable plugin and then upgrade for avoid issue with new WP version.
January 17, 2025 at 4:55 pm #16607604
Mihai Apetrei Supporter Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00)	Hi there. I am not sure if WP will break; I don't think it should but please do create a full website backup first so that you can have a safety net no matter what happens. And yes, you would have to manually download the major versions, then install and activate them, then disable them, one by one. I hope that you will find this information helpful.
January 20, 2025 at 4:34 am #16611636
damirG-2	Hi, I upgrade successfully, and the only page that seems to break after upgrading WPML is the page that show posts by category, like this one hidden link Any idea what could be? Thanks
January 20, 2025 at 10:24 pm #16615706
Mihai Apetrei Supporter Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00)	Hi there, and welcome back. I'm happy to hear that you were able to make good progress on this. I recommend that you enable the WordPress debug feature and recreate the issue. This will help you determine if you're receiving a specific error message instead of the general "fatal error" message. By doing this, you can check for any PHP errors that might be occurring. Here’s how to enable debugging: 1. Edit the `wp-config.php` file in your WordPress directory. 2. Add the following lines: define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', false ); define( 'WP_DEBUG_DISPLAY', true ); Once you’ve made these changes, please reproduce the issue again. After that, check if you see any additional information. You might get a more detailed error message. Then, if you have more information, you can try to see if you can find any existing tickets with that exact error together with a resolution from our colleagues, and if you can't find any, please open a new ticket for this specific issue so that we can properly focus on one issue per ticket. Per our Support Policy, we can handle only one issue per ticket. Continuing with one issue per ticket helps supporters focus on one issue at once and enables other users to find solutions to their questions faster. Thank you very much for your understanding and cooperation.