Critical error with all latest versions
-
Hello, I have a critical error on a page where the plugin is used to display some podcasts. I have tried to roll back until version 2.19.1. and it randomly works fine and then a few moments/hours later display the critical error again. That happens with all versions between 2.19.1. and the latest, which makes me think these versions are not stable anymore :/
If I disable the plugin, the critical error message / visual bug disappears for good.
Can you help me out with that ?
Thanks
The page I need help with: [log in to see the link]
-
Hi, @alexis888!
Sorry to hear you got this critical error. Could you try to check your server logs? They should show the file/line when the error happens. Also, if you can’t find those logs, you can temporarily try to enable displaying errors on your site. Add (or edit) this string in your wp-config.php file:define( 'WP_DEBUG', true );
Hope this helps,
Sergiy, development team.Hello @zahardoc! thanks for your answer.
Here you go with the debug logs :
[14-Apr-2023 04:58:14 UTC] PHP Notice: La fonction ID a été appelée de fa?on <strong>incorrecte</strong>. Les propriétés du produit ne doivent pas être accessible directement. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/oceanwp/page.php'), get_template_part, locate_template, load_template, require('/themes/oceanwp/partials/page/layout.php'), get_template_part, locate_template, load_template, require('/themes/oceanwp/partials/page/article.php'), the_content, apply_filters('the_content'), WP_Hook->apply_filters, Elementor\Frontend->apply_builder_in_content, Elementor\Frontend->get_builder_content, Elementor\Core\Base\Document->print_elements_with_wrapper, Elementor\Core\Base\Document->print_elements, Elementor\Element_Base->print_element, Elementor\Element_Base->print_content, Elementor\Element_Base->print_element, Elementor\Element_Base->print_content, Elementor\Element_Base->print_element, Elementor\Widget_Base->print_content, Elementor\Widget_Base->render_content, Elementor\Co in /home/uabezuwx/uvpr.fr/wp-includes/functions.php on line 5865 [14-Apr-2023 04:58:14 UTC] PHP Notice: La fonction ID a été appelée de fa?on <strong>incorrecte</strong>. Les propriétés du produit ne doivent pas être accessible directement. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/oceanwp/page.php'), get_template_part, locate_template, load_template, require('/themes/oceanwp/partials/page/layout.php'), get_template_part, locate_template, load_template, require('/themes/oceanwp/partials/page/article.php'), the_content, apply_filters('the_content'), WP_Hook->apply_filters, Elementor\Frontend->apply_builder_in_content, Elementor\Frontend->get_builder_content, Elementor\Core\Base\Document->print_elements_with_wrapper, Elementor\Core\Base\Document->print_elements, Elementor\Element_Base->print_element, Elementor\Element_Base->print_content, Elementor\Element_Base->print_element, Elementor\Element_Base->print_content, Elementor\Element_Base->print_element, Elementor\Widget_Base->print_content, Elementor\Widget_Base->render_content, Elementor\Co in /home/uabezuwx/uvpr.fr/wp-includes/functions.php on line 5865 [14-Apr-2023 04:58:14 UTC] PHP Notice: La fonction ID a été appelée de fa?on <strong>incorrecte</strong>. Les propriétés du produit ne doivent pas être accessible directement. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/oceanwp/page.php'), get_template_part, locate_template, load_template, require('/themes/oceanwp/partials/page/layout.php'), get_template_part, locate_template, load_template, require('/themes/oceanwp/partials/page/article.php'), the_content, apply_filters('the_content'), WP_Hook->apply_filters, Elementor\Frontend->apply_builder_in_content, Elementor\Frontend->get_builder_content, Elementor\Core\Base\Document->print_elements_with_wrapper, Elementor\Core\Base\Document->print_elements, Elementor\Element_Base->print_element, Elementor\Element_Base->print_content, Elementor\Element_Base->print_element, Elementor\Element_Base->print_content, Elementor\Element_Base->print_element, Elementor\Widget_Base->print_content, Elementor\Widget_Base->render_content, Elementor\Co in /home/uabezuwx/uvpr.fr/wp-includes/functions.php on line 5865 [14-Apr-2023 04:58:14 UTC] PHP Notice: La fonction ID a été appelée de fa?on <strong>incorrecte</strong>. Les propriétés du produit ne doivent pas être accessible directement. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/oceanwp/page.php'), get_template_part, locate_template, load_template, require('/themes/oceanwp/partials/page/layout.php'), get_template_part, locate_template, load_template, require('/themes/oceanwp/partials/page/article.php'), the_content, apply_filters('the_content'), WP_Hook->apply_filters, Elementor\Frontend->apply_builder_in_content, Elementor\Frontend->get_builder_content, Elementor\Core\Base\Document->print_elements_with_wrapper, Elementor\Core\Base\Document->print_elements, Elementor\Element_Base->print_element, Elementor\Element_Base->print_content, Elementor\Element_Base->print_element, Elementor\Element_Base->print_content, Elementor\Element_Base->print_element, Elementor\Widget_Base->print_content, Elementor\Widget_Base->render_content, Elementor\Co in /home/uabezuwx/uvpr.fr/wp-includes/functions.php on line 5865 [14-Apr-2023 04:58:34 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 182154176 bytes) in /home/uabezuwx/uvpr.fr/wp-includes/Requests/src/Transport/Curl.php on line 481 [14-Apr-2023 04:59:01 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 182153704 bytes) in /home/uabezuwx/uvpr.fr/wp-includes/Requests/src/Requests.php on line 740 [14-Apr-2023 04:59:07 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 182153704 bytes) in /home/uabezuwx/uvpr.fr/wp-includes/Requests/src/Requests.php on line 740 [14-Apr-2023 05:02:25 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 182154176 bytes) in /home/uabezuwx/uvpr.fr/wp-includes/Requests/src/Transport/Curl.php on line 481 [14-Apr-2023 05:02:43 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 182153704 bytes) in /home/uabezuwx/uvpr.fr/wp-includes/Requests/src/Requests.php on line 740
Hi @alexis888,
Logs show there is a problem with your server memory. For some reason, the request takes too much memory. Unfortunately, I can’t say what exactly you should do to fix it, and I’m not sure if it is SSP plugin related.What I would suggest is to try:
1. Switch the theme and check if it helps.
2. Try to disable plugins one by one and check which plugin might take so much memory.
3. Try to change Elementor blocks ( remove and add them to check if any of the Elementor blocks causes that issue ).
4. Try to increase your PHPmemory_limit
setting ( ask your hosting provider ).Hope this helps,
Sergiy.Hello @zahardoc ,
thanks for your answer.I tried steps one to 3.
1 – switching theme to Twenty Twenty three : error still here unless I disable SSP
2 –
2.A – Critical Error still here unless I disable SSP or CookieYes | GDPR Cookie ConsentThen I tried switching to a different Cookie plugin I use without issue on other websites : GDPR Cookie Compliance Plugin (CCPA ready)
The critical error but there is still several bugs, see 2.B.
So first it seems there is a conflict between SSP and CookieYes | GDPR Cookie Consent and GDPR Cookie Compliance Plugin (CCPA ready)
2.B – If no cookie plugin is enabled and only SSP I don’t have the critical error bug but :
- the whole block with the loop displaying the podcasts is not displayed at all
- I can’t edit the page where podcasts are displayed with element or as the ? Edit the page with Elementor ? link in the top bar isn’t displayed, .
- my menu doesn’t work anymore on that specific page
3 – I removed all blocks on the page except the custom loop displaying the podcasts episodes from SSP, still bugging like explained above in 2.B.
Same thing with the custom loop block removed and put again.??4 – seems to be a temporary fix, it might fix the issue (making it possible to run a script using to much memory) but not the cause (the actual script using to much memory) so I’d prefer the issue to be fixed in the plugin / script rather than / before asking my hosting provider who might tell me that there is an issue anyway.
As I said in the original message if I disable SSP plugin, the critical error message / visual bug disappears for good. And the page where the plugin displays podcasts is the only page on the website where I can see this critical error, no other page has the issue.
So it looks like it is SSP that cause the problem.
Don’t you think?Hi @alexis888,
I tried to investigate your issue but unfortunately, I couldn’t reproduce it.
I think it has something to do with your Elementor loop settings, maybe something goes wrong there. I would suggest hiring a developer to take a deeper look into this.
Kind regards,
Sergiy, development team.
- The topic ‘Critical error with all latest versions’ is closed to new replies.