Title: Bug with Elementor Update
Last modified: January 29, 2020

---

# Bug with Elementor Update

 *  [locomint85](https://wordpress.org/support/users/locomint85/)
 * (@locomint85)
 * [6 years, 4 months ago](https://wordpress.org/support/topic/bug-with-elementor-update/)
 * With new update of Elementor (2.8.5), my version of Ocean Extra (1.5.20) crash
   the Elementor page (not loading the page).
    If I disable the plugin, it’s ok.
 * Only Elementor / Elementor Pro and Ocean Extra activate.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [azumadigital](https://wordpress.org/support/users/azumadigital/)
 * (@azumadigital)
 * [6 years, 4 months ago](https://wordpress.org/support/topic/bug-with-elementor-update/#post-12383082)
 * Yes, this is an never ending story with OceanWP and Elementor… it seams that 
   OceanWP is not 100% compatible with Elementor nor Elementor PRO. Period!
    I have
   the same problem and even though I have sent the details to OceanWP’s support
   team the problem is still there, just waiting to show up with every Elementor
   and Ocean Extra and Ocean Elementor Widgets update… this is insane!!! The solution
   I found until now was to go with Elementor in safe mode, but this is not ok.
 *  Plugin Author [Amit Singh](https://wordpress.org/support/users/apprimit/)
 * (@apprimit)
 * [6 years, 4 months ago](https://wordpress.org/support/topic/bug-with-elementor-update/#post-12384095)
 * Hello,
 * I tested the theme with the latest version of Elementor but don’t have any error.
   Can you please share the error log and Elementor system info so that I can check
   it?
 *  [azumadigital](https://wordpress.org/support/users/azumadigital/)
 * (@azumadigital)
 * [6 years, 4 months ago](https://wordpress.org/support/topic/bug-with-elementor-update/#post-12402041)
 * Hello Amit,
 * Problems solved.
    It was the server’s RAM limit that prevented Elementor widgets
   to load.
 * Thank you.
 *  [explanetome](https://wordpress.org/support/users/explanetome/)
 * (@explanetome)
 * [6 years, 3 months ago](https://wordpress.org/support/topic/bug-with-elementor-update/#post-12535267)
 * Hi all,
 * After an Elementor update have a fatal error with Ocean Extra.
    PHP version is
   ok Have then updated Ocean WP Cannot reactivate Ocean Extra Have checked all 
   the options in script and style menu of elementor Still cannot reactivate Ocean
   Extra
 * What should I do now ?
 * Here is the message :
 * Warning: require_once(/home/sophieelds/www/wp-content/plugins/ocean-extra//includes/
   panel/theme-panel.php): failed to open stream: No such file or directory in /
   home/******/www/wp-content/plugins/ocean-extra/ocean-extra.php on line 119
 * Fatal error: require_once(): Failed opening required ‘/home/******/www/wp-content/
   plugins/ocean-extra//includes/panel/theme-panel.php’ (include_path=’.:/usr/local/
   php7.0/lib/php’) in /home/******/www/wp-content/plugins/ocean-extra/ocean-extra.
   php on line 119
 * WordPress version 5.3.2
    Thème actuel : OceanWP (version 1.7.1) Extension actuelle:
   Ocean Extra (version 1.6.0) PHP version 7.0.33
 * Thanks for your help !
    -  This reply was modified 6 years, 3 months ago by [explanetome](https://wordpress.org/support/users/explanetome/).

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Bug with Elementor Update’ is closed to new replies.

 * ![](https://ps.w.org/ocean-extra/assets/icon.svg?rev=2814940)
 * [Ocean Extra](https://wordpress.org/plugins/ocean-extra/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ocean-extra/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ocean-extra/)
 * [Active Topics](https://wordpress.org/support/plugin/ocean-extra/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ocean-extra/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ocean-extra/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [explanetome](https://wordpress.org/support/users/explanetome/)
 * Last activity: [6 years, 3 months ago](https://wordpress.org/support/topic/bug-with-elementor-update/#post-12535267)
 * Status: not resolved