I would like to re-open the ticket N#14253705 as the many critical issues reported were not solve. Also, we would like to have support in English and in same time zone please.
To summarize and bring you up to date with the outstanding issues in hand, please refer to the details mentioned below or previous ticket details.
After updating to the latest version of WPML plugin (4.6.4) on august 4th, we encountered many major problems which broke our site and many and bugs that are still causing many problems and inconveniences and which we would like to you to investigate and resolve if possible asap. Please refer to screen captures for example of each issue.
Issues:
WordPress found an error with one of our extensions, "WPML Multilingual CMS"
Apparently, it is an issue with WMPL and Google Site Kit 1.106- which we were told by support will be addressed in the 4.6.5 update release.
Product translations were lost
Many translations were made long before the update and disappeared after updating.
Original language is wrong for several products.
The original language of some products were changed after the update.
Multiple duplicates of products in French were created.
Many duplicates of products were created in French, resulting in 5,208 elements and 404 errors. We only have about 150 products in each language.
French Product links are broken
Many product links in French were broken including those for product who were duplicated and as a result we have 404 errors and 1,4k non indexed pages. All links in English are ok.
Theme and plugin translation
This problem or feature was not installed by us, nor the next issue N#7 and would like it removed. WMPL seams to include sub-plug-ins that get automatically added with new updates that we don’t necessary need, want or know about.
It is also causing a bug for navigation as you can see on screen shot, the language is set to English but the side navigation is in French. This happens all the time. Another example is with the user settings with the language. Set to English but every time the user log-ins all the navigation is in French.
Sticky links
This problem or feature was not installed by us and would like it removed if there’s no major implication.
Menu language switcher
The menu language switcher of the pages has disappeared. I was added on Elementor template when the site was built and was working until the plugin update.
WPML Media Translation
We are having problems with this feature. We want to have a picture for English and one for French which is different. We do not want to duplicate media attachments nor featured images for translations. However, we cannot modify the setting for this option. We change it and it comes back to its default setting.
What we have done so far:
We’ve tested each plugin and we can confirm that WMPL is causing this issue.
We’ve also contacted WooCommerce and they say the problem seems to be coming from WPML
We’ve updated WPML to 4.6.5 and Issue n# 1 the Google Site Kit 1.106 was resolved. However, the other issues persist.
We’ve Deleted all cache files/cookies from our site.
We’ve Made a backup of our site and proceeded to WPML > Support > troubleshooting and tried the requested procedure recommend by support.
We’ve provided the debug information (42 error logs)
We’ve also duplicated the site and will be giving you access to a staging site for further investigation. However, it cannot be push into live site.
Thank you for your prompt assistance in this URGENT matter, I am sure you are aware of the importance of having a Functional and Bilingual eCommerce site in today’s economy.
Looking forward to hearing from you as soon as possible.
Hi there, thanks for reaching out to WPML support. I"m not able to reopen the previous ticket, but I'll be happy to go over the issues with you here. Please note that it is our policy to address one issue per chat/ticket, so I'll start here with the first issue you mentioned and as we move on, we can split this into new tickets as needed.
With version 4.6.5, are you seeing the following error in your debug log? An error of type E_ERROR was caused in line 3937 of the file .../wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php. Error message: Uncaught TypeError: Illegal offset type in isset or empty in .../wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:3937
Stack trace:.. ?
If so, please share a screenshot of your debug log with the error from today's dates so I can compare the error details. Thanks!
I'm not exactly sure what you are showing me, but that does not look like the error specifically related to Google Site Kit, and it doesn't look like the debug.log file. Please enable the debug log and confirm whether or not you see the specific error related to Google Site Kit, as that is the first issue you mentioned and we need to determine if it is still there. I paseted the error above and you can also see an example of the error here: https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/
If you need assistance activating debug log, please follow these steps:
WordPress includes a debug mode that helps reveal PHP problems. Let's enable this and see if there are any errors we can locate.
To enable it, open your wp-config.php file and look for
In this case the errors will be saved to a debug.log log file inside the /wp-content/directory.
The wp-config.php is located in your WordPress root directory. It’s the same file where the database configuration settings are. You will have to access it by FTP or SFTP in order to edit it.
If you open wp-config.php and that define statement is not there, you can add it right before this line:
/* That's all, stop editing! Happy blogging. */
Please note that you’ll see everything, not only related to our Plugins. This will most likely include messages from other plugins, your theme, and sometimes even WordPress core. The messages appear all over the place.
Sometimes they appear right on top, but they can also appear in the middle of the page.
After enabling the debug mode, please try to replicate the issue. Navigate to the page where the error message being displayed. The errors will be either displayed on the screen or logged in the debug.log log file inside the /wp-content/directory.
Paste the latest lines here. No need to paste the entire log file, just 50 lines or so will do. Please censor any sensitive information.
As per you question: With version 4.6.5, are you seeing the following error in your debug log?With version 4.6.5, are you seeing the following error in your debug log? An error of type E_ERROR was caused in line 3937 of the file .../wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php. Error message: Uncaught TypeError: Illegal offset type in isset or empty in .../wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:3937Stack trace:.. ?
I found:[03-Aug-2023 18:43:08 UTC] PHP Warning: Illegal offset type in isset or empty in /home/lwx5vkd85n8n/public_html/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 3937
Why I can't attached the debug log now? I have the debug file but the reply form does not permit me to attach it.
We don't need the entire debug log, just the latest error. You can send a screenshot under the size of 1MB if you want to share a picture of the latest error. But it sounds to me like you are no longer seeing the error related to Google Site Kit, which means it was resolved with 4.6.5. Since that seems to be resolved, we can look at the issue "Product translations were lost". This is not expected behavior. Do you have a backup that you can restore to restore the lost translations?
If not, please let me know exactly which translations are missing. Is it all languages? Is it posts, pages, products, custom post types? Is it strings? I'll need to know more detail about exactly what was lost in the update so that I can further troubleshoot. For the other issues you mentioned in the ticket summary, please open a separate ticket for each issue, unless you prefer to wait until we resolve the lost translations and then I can split this ticket to open a new one as we progress.
Screenshots of what is missing will be helpful for me to understand what you expect to see versus what you no longer see.
As for translations missing,
please refer to the first message #14352295 with prints screens
[08-Sep-2023 18:40:08 UTC] PHP Notice: Undefined offset: 1 in /home/lwx5vkd85n8n/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/module.php on line 381
[08-Sep-2023 18:40:08 UTC] PHP Notice: Undefined offset: 1 in /home/lwx5vkd85n8n/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/module.php on line 381
[08-Sep-2023 18:42:20 UTC] PHP Notice: Undefined index: product_id in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce-multilingual/inc/class-wcml-cart.php on line 314
[08-Sep-2023 18:42:20 UTC] PHP Notice: Undefined index: product_id in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce-multilingual/inc/class-wcml-cart.php on line 337
[08-Sep-2023 18:42:20 UTC] PHP Notice: Undefined index: variation_id in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce-multilingual/inc/class-wcml-cart.php on line 391
[08-Sep-2023 18:42:20 UTC] PHP Notice: Undefined index: product_id in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce-multilingual/inc/class-wcml-cart.php on line 391
[08-Sep-2023 18:42:20 UTC] PHP Notice: Undefined index: quantity in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce-multilingual/inc/class-wcml-cart.php on line 433
[08-Sep-2023 18:42:20 UTC] PHP Notice: Undefined index: product_id in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce-multilingual/inc/class-wcml-cart.php on line 499
[08-Sep-2023 18:42:20 UTC] PHP Notice: Undefined index: variation_id in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce-multilingual/inc/class-wcml-cart.php on line 500
[08-Sep-2023 18:42:20 UTC] PHP Notice: Undefined index: variation in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce-multilingual/inc/class-wcml-cart.php on line 501
[08-Sep-2023 18:42:20 UTC] PHP Notice: Undefined index: data in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php on line 232
[08-Sep-2023 18:42:20 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_tax_class() on null in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php:232
Stack trace:
#0 /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php(658): WC_Cart_Totals->get_items_from_cart()
#1 /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php(150): WC_Cart_Totals->calculate_item_totals()
#2 /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php(141): WC_Cart_Totals->calculate()
#3 /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce/includes/class-wc-cart.php(1406): WC_Cart_Totals->__construct(Object(WC_Cart))
#4 /home/lwx5vkd85n8n/public_html/wp-includes/class-wp-hook.php(308): WC_Cart->calculate_totals()
#5 /home/lwx5vkd85n8n/public_html/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(NULL, Array)
#6 /home/lwx5vkd85n8n/public_html/wp-includes/plugin.php(517): WP_Hook->d in /home/lwx5vkd85n8n/public_html/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php on line 232
[08-Sep-2023 18:51:00 UTC] PHP Notice: Undefined index: host in /home/lwx5vkd85n8n/public_html/wp-includes/canonical.php on line 691
[08-Sep-2023 18:51:00 UTC] PHP Notice: Undefined index: host in /home/lwx5vkd85n8n/public_html/wp-includes/canonical.php on line 702
[08-Sep-2023 18:51:00 UTC] PHP Notice: Undefined index: host in /home/lwx5vkd85n8n/public_html/wp-includes/canonical.php on line 705
[08-Sep-2023 18:55:28 UTC] PHP Warning: filesize(): stat failed for /home/lwx5vkd85n8n/public_html/wp-content/cache/object/bae/18c/bae18c06631a01d62ae261935627436f.php in /home/lwx5vkd85n8n/public_html/wp-content/plugins/w3-total-cache/Cache_File.php on line 159
[08-Sep-2023 18:55:28 UTC] PHP Warning: filesize(): stat failed for /home/lwx5vkd85n8n/public_html/wp-content/cache/object/7ec/d89/7ecd89fff1db7fe47adb50ea6f8def26.php in /home/lwx5vkd85n8n/public_html/wp-content/plugins/w3-total-cache/Cache_File.php on line 159
[08-Sep-2023 19:07:35 UTC] PHP Notice: Undefined offset: 1 in /home/lwx5vkd85n8n/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/module.php on line 381
[08-Sep-2023 19:07:35 UTC] PHP Notice: Undefined offset: 1 in /home/lwx5vkd85n8n/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/module.php on line 381
[08-Sep-2023 19:12:53 UTC] PHP Notice: Undefined offset: 1 in /home/lwx5vkd85n8n/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/module.php on line 381
[08-Sep-2023 19:12:53 UTC] PHP Notice: Undefined offset: 1 in /home/lwx5vkd85n8n/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/module.php on line 381
[08-Sep-2023 19:12:53 UTC] PHP Notice: Undefined offset: 1 in /home/lwx5vkd85n8n/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/module.php on line 381
[08-Sep-2023 19:12:53 UTC] PHP Notice: Undefined offset: 1 in /home/lwx5vkd85n8n/public_html/wp-content/plugins/elementor-pro/modules/woocommerce/module.php on line 381
[08-Sep-2023 19:36:58 UTC] PHP Notice: Undefined index: host in /home/lwx5vkd85n8n/public_html/wp-includes/canonical.php on line 691
[08-Sep-2023 19:36:58 UTC] PHP Notice: Undefined index: host in /home/lwx5vkd85n8n/public_html/wp-includes/canonical.php on line 702
[08-Sep-2023 19:36:58 UTC] PHP Notice: Undefined index: host in /home/lwx5vkd85n8n/public_html/wp-includes/canonical.php on line 705
I don't see any Fatal Error in what you are sharing from the debug log, only notices. So I will assume the Google Site Kit error is resolved with 4.6.5. Back to the missing translations. It's not very clear to me from the screenshots, and since I don't speak French, I can't read through the ticket. I can try to figure out that it appears the content is there, but now it is all assigned to one language, and the translations are not linked. Is that what you are referring to? If that is the case, you can resolve it by editing the translated page and in the Languages box, select "this is a translation of" and select the page it should be connected to. This is not something that would regularly occur in an update, so it's possible something got corrupted in your database during the update. The best way for us to try and see what happened is to restore a backup in a staging site of before the update, and then let us run the update so we can see what changes in the database. Do you have that as an option?
As per your investigation, concerning the Google Site Kit error we will take note that according to your conclusions the error has been resolved with 4.6.5.
As per the missing translations:
Most of all the 20 pages of translations appearing int the translation section of WPML, had already being assigned, approved, and translated previously to the update.
After the update, they reappeared in the list of translations, some of them not assigned and some to be translated again and with the original language changed and all assigned to one language, French.
As you can see on the screen capture N#1 herein enclosed, the 1st product in the list is in English and its translation is underneath in French
And just in case it’s related somehow:
This Issue is also linked to the issue n#3 which you will also notice that its original language is in English as you can also clearly see in Screen Capture N#2 from the product page, but is showing as ‘’français’’ = French in the translation list and # 6 as per the navigation language which cannot be change to English
As per resolving this issue as suggested, this is not possible since we cannot edit the translated page nor the Languages box”. It does not give the option to select "this is a translation of" and select the page it should be connected to. Furthermore, going through 20 pages +of translations is not really a viable option. Specially if we don’t know the cause of this issue and if it will re occur.
Having said that, further investigation would be need and you can go ahead and restore a backup from WP/Settings/ Updraft plus/ Jun 29, 2023 15:43 in the staging site we setup for your testing purposes.
Great, I'll be happy to run the restore and then try to update to see what I can find. Please send credentials in the attached fields in the next reply.
Please note that we may not be able to resolve this without manually editing the content if the issue turns out to be a database corruption, but I will do my best to determine what is happening. The reason you can't select "this is a translation of" is likely because you need to first change the language of the page to a secondary language.
I'll look deeper into this one I have access to the test site. Thanks!
Thank you, I received the credentials. Can you please confirm that you have sent the access to the dvelopment site and not production?
Also, please let me know if I can install a plugin to access the database and a file management plugin as needed so that I can take a look and see if I can find any errors after I run the update.
Lastly, I may need to disable theme/plugins and run the update again to compare, and make sure there is no conflicting plugins. Please let me know if I have your permission to do that at hidden link as well.
The credential I sent is a temporary WordPress admin access for WordPress / server access and LIVE site
Here is link for the staging site (development site) which you can use same credetials: hidden link
As per installing a plugin to access the database, can you advise which one please?
For the file management plugin, we already have WP file manager so that you can take a look at the error log files after you run the update.(you can also find the one from august after update to compare as well)
As per disabling theme/plugins and running the update again in staging site, you can go ahead.
Thanks so much for permission to test. On the staging site, I deactivated everything except WooCommerce and WPML core and ran the updates at Plugins -> Add New -> Commercial. (Clicked check for updates, and updated core and string translation). I then checked the list of products and can see the same number of products in each language before the update. I can also see the specific product you sent a screenshot of "Moisturizer and sealant for CPAP masks with aloe by CPAPology" is still set to English.hidden link
So, since it worked in minimal settings, it's likely that somethign either conflicted with the updated, or something was corrupted in the database. Do you want to restore a backup on your live site and try updating the way I did and see if the issue is resolved, or if it returns?
Another option is to restore the backup on the staging site and you can try updating the way you ddi on the live site and see if you are able to reproduce the issue there. If so, I would install the Adminer plugin to look further into the database.
Thanks, Lauren for explaining the steps you took to try to reproduce this issue and eventually fix this problem, really appreciate the time to explain.
Before hand, I just wanted to make sure that you are testing the correct database. As mentioned, the previous database backup with the WPML version (4.6.4) must be uploaded from WP/Settings/ Updraft plus/ Jun 29, 2023 15:43 in the staging site for your testing purposes, since it’s the previous backup before the (4.6.5) update that cause this issue that needs to be uses for testing. Here you will find our actual number of products (150) in English and not 5,208 as seen in the staging site.
If this is the not the case, you can go ahead with option 2 as suggested and restore the backup (Jun 29, 2023) on the staging site and update to 4.6.5 or 4.6.6. and see if you are able to reproduce the issue . You can also go ahead and install the Adminer plugin to look further into the database.
If you tested the correct database, you could go ahead and restore the backup (Jun 29, 2023 ) on our live site and update as you did in the staging site to see if the issue is resolved, or if it returns.
I’m also wondering what could have conflicted with the updated, or corrupted the database? Just so we can keep a look out for that.
I've been trying to run the backup but nothing is working. It just keeps spinning with the following error messages:
Download plugins (Jun 29, 2023 15:43):
plugins:
Remote fetch failed
No local copy present.
Can you please run the restore on the test site and let me know once it's done so I can then try updating WPML?
Thanks.
