Critical Error: PolylAI + Elementor
-
I’m getting a critical error message in translated pages using Polylang + PolylAI + OpenAI API + Elementor. Is this being addressed as a priority in Source Code SRL?
Otherwise we will seek another solution, becouse this is a priority for us.
We are using Linguise, but the quality of the translations is very poor. We know that ChatGPT has a satisfactory quality for translations, which is why we are testing your plugin.
Screenshot PolyAI Critical Error 01: https://imgur.com/BvnVbUL
Screenshot PolyAI Critical Error 02: https://imgur.com/5WtNFzC
Screenshot PolyAI Critical Error 03 https://imgur.com/Ulf9Hh6
Obs: We can’t mantain Polylang active, becouse it’s conflict with Linguise. If you need it to be active to analyse the error, please let us know.
Thanks!The page I need help with: [log in to see the link]
-
Hi Ricardo,
our plugin is based on Polylang so it can’t work without it. The critical error shows up with Polylang activated? To get more information we should see the exact error, and for that you 2 ways:
- check the error log of the web server (usually available in the hosting panel)
- otherwise edit the file wp-config.php and write this string:
define( 'WP_DEBUG', true );IMPORTANT: make sure there is not already the string
define( 'WP_DEBUG', false );it it’s already there just change the value fromfalsetotrue.Then try again and let me know the exact error that will be reported in the page.
Hi there!
ChatGPT o3-mini have identified the root cause of the fatal error on translated pages: the plugin is rewriting the
_elementor_page_settingsmeta field, causing a type mismatch inmanager.php:255. This results in the error “Cannot access offset of type string on string” because_elementor_page_settingsis stored as a string instead of an array.I’m also using HubSpot/Leadin, which might be contributing to the conflict, but the issue only occurs on pages translated by the AI plugin. It appears the metadata is being altered or translated when it shouldn’t be.
Could you please address this so that
_elementor_page_settingsremains in the correct format? Or provide guidance on how to exclude_elementor_page_settings(and any other Elementor meta fields) from the translation process? That would help prevent this fatal error on translated pages.
Here is the error:
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/u345464178/domains/abovenet.com.br/public_html/wp-content/plugins/elementor/core/settings/page/manager.php:255 Stack trace: #0 /home/u345464178/domains/abovenet.com.br/public_html/wp-content/plugins/elementor/core/settings/base/manager.php(313): Elementor\Core\Settings\Page\Manager->get_saved_settings() #1 /home/u345464178/domains/abovenet.com.br/public_html/wp-content/plugins/elementor/core/settings/base/manager.php(104): Elementor\Core\Settings\Base\Manager->create_model() #2 /home/u345464178/domains/abovenet.com.br/public_html/wp-content/plugins/leadin/public/class-pagehooks.php(96): Elementor\Core\Settings\Base\Manager->get_model() #3 /home/u345464178/domains/abovenet.com.br/public_html/wp-includes/class-wp-hook.php(324): Leadin\PageHooks->add_page_analytics() #4 /home/u345464178/domains/abovenet.com.br/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #5 /home/u345464178/domains/abovenet.com.br/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #6 /home/u345464178/domains/abovenet.com.br/public_html/wp-includes/general-template.php(3064): do_action() #7 /home/u345464178/domains/abovenet.com.br/public_html/wp-content/themes/astra/header.php(31): wp_head() #8 /home/u345464178/domains/abovenet.com.br/public_html/wp-includes/template.php(810): require_once(‘/home/u34546417…’) #9 /home/u345464178/domains/abovenet.com.br/public_html/wp-includes/template.php(745): load_template() #10 /home/u345464178/domains/abovenet.com.br/public_html/wp-includes/general-template.php(48): locate_template() #11 /home/u345464178/domains/abovenet.com.br/public_html/wp-content/themes/astra/page.php(20): get_header() #12 /home/u345464178/domains/abovenet.com.br/public_html/wp-includes/template-loader.php(106): include(‘/home/u34546417…’) #13 /home/u345464178/domains/abovenet.com.br/public_html/wp-blog-header.php(19): require_once(‘/home/u34546417…’) #14 /home/u345464178/domains/abovenet.com.br/public_html/index.php(17): require(‘/home/u34546417…’) #15 {main} thrown in /home/u345464178/domains/abovenet.com.br/public_html/wp-content/plugins/elementor/core/settings/page/manager.php on line 255Thank you for your assistance, and I look forward to your update.
Working on this!
Hi Diego! Can you give us an idea of the deadline for completing this fix, please?
Hi Ricardo, I was going to release a big update so I had to add the fix in this release, I think I’ll be able to release it in a couple of days.
Ciao Diego! Great, grazie mille!
We’re a bit late because we’re fixing and tweaking but we’re doing our best to be fast, thanks for your patience!
Hi Diego!
I’m considering upgrading to the Pro version of AI Translator for Polylang, but I need to confirm if it supports a “Bulk Translation” feature. Our website has a large number of pages, posts and products, so we’d like an automated way to translate them in the background without having to manually click on each page/post/product.
We can definitely set up a cron job as required. Could you please let me know if the Pro version offers automatic or bulk translation? If so, how does it work—do we enqueue posts/pages, or is there a separate interface for it?
Any news on the bug fix?
Thanks!Hi!
Any news on the bug fix?
Sorry I forgot to write here, the bug has been fixed and the fix was published saturday, check the version 1.3.1
It’s a big update, and a lot of logic has been completely rewritten and improved. If you find any issues, please feel free to report them.
I’m considering upgrading to the Pro version of AI Translator for Polylang, but I need to confirm if it supports a “Bulk Translation” feature. Our website has a large number of pages, posts and products, so we’d like an automated way to translate them in the background without having to manually click on each page/post/product.
The bulk translation has been quite requested, so we just started adding it. I think it can be released in about a week.
Hi Diego!
I’m trying to test, but I’m missing something in the process. Do I need to click in the Polylang “+” and them in the “Translate” buttom from PolyAI Translator or I don’t need to click in the “+” to create the English page?
If I translate ir directly, the translation does not leave the queue.Please guide me on the correct sequence to perform the translations.
Thanks!Well, that’s actually correct because the free version has one language only other the main one. In case you can now use the Cloud version (available since 1.3.0) where you can purchase credits for translations in cloud (so not using your keys) and have all the functionalities of the Premium version.
-
This reply was modified 1 year, 1 month ago by
Diego.
Hi Diego!
The test in the screenshot 2 above is with PolylAI Cloud and I’m not being able to make the translations work. Can you guide me step by step? I need to make the test work before we upgrade.
Thank you!Oh, sorry I didn’t notice it was a cloud request. I’m not able to find the translation request, this is weird. Please write to [email protected] and provide the license key you got by email when you purchased credits, so I can inspect the issue.
The topic ‘Critical Error: PolylAI + Elementor’ is closed to new replies.