Background of the issue:
I am trying to activate WPML CMS on my WordPress site. I encountered issues when activating the plugin, which seems to have compatibility problems with other plugins. The issue can be seen on this page: hidden link.
Symptoms:
When activating WPML CMS, it shows a WordPress critical error: 'There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.' The issue appears to be related to compatibility with the Imagededuper and WPBakery plugins.
Questions:
How can I resolve the critical error when activating WPML CMS?
What steps should I take to address compatibility issues with Imagededuper and WPBakery?
Does the error disappear once you disable this plugin for a moment?
If not, could you please create a copy or staging of the website and try running it with a minimal setup to see if the issue persists?
1) Deactivate any additional plugins that are unrelated to WPML and our add-ons.
2) If the issue goes away, start reactivating plugins one at a time or activate them in small groups. This way, check where the issue recurs to identify the plugin causing the issue.
3) If this doesn't resolve the issue, please switch to a standard theme like Twenty Twenty-One to see if the issue might be theme-related.
Once we identify the cause, we can attempt to replicate the issue and then escalate it internally. I will provide a test site with WPML in this case.
If you're unable to set up a copy of your website, please let me know, and I'll be happy to assist you.
Hi Andreas, I have tested this on production because i recently had issues on my staging.
The combination deduper and wpml cms def. is not working. I tried this exactly the way you described. Activated WPML cms and one by one activated other plugins.
The result remains the same. When I activate wpml cms, it messes up my website in combination with other plugins. If only the wpml plugin is dactivated I dont receive that error.
im preparing staging for you. i'll let you know and give you access.
Do you have a special procedure to get access? Or should I just create the user with full admin rights?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
I would like to offer to take a closer look and request temporary access (wp-admin and FTP) to the website to investigate the issue further.
The required fields are located below the comments section when you log in to leave the next reply. The information you provide is private, meaning only you and I can see and access it.
IMPORTANT
Please be sure to back up your website and database before granting us access.
If you can't see the "wp-admin / FTP" fields, your post and website credentials will be set to "PUBLIC." DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may need to install a plugin called "All In One WP Migration" to create a copy of the website so I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site from your server for this purpose.
If you are unable to provide such a copy of the website for testing, please let me know on this ticket.
The private reply form looks like this: hidden link
Click "I still need assistance" the next time you reply.
Video: hidden link
Please note that we are required to request this information individually on each ticket. We are not permitted to access any credentials that were not specifically submitted on this ticket using the private response form.
good morning. after de/re-activationg several plugins it seems to be working now. I am not sure if this was just a glitch as I was able to reproduce the issue (also with cache cleared) yesterday. Please do not make any changes for now.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
My apologies for the delay in answering, as I work from Tuesdays to Saturdays.
I have not visited your site yet, and I am glad to hear that you found a solution. In fact, sometimes we handle which such unexpected edge cases, where the only solution is deactivating and reactivating a specific plugin.
Unless the issue occurs again, you will be able to consider this as resolved.
