Divi Error as of 10/15/2024

  • Resolved mach4design

    (@mach4design)


    1 month, 1 week ago

    Hello,
    We were getting a critical error message trying to use the front End Builder of Divi. Both on the front end as well as in the page edit mode. After some troubleshooting, this is what our Tech Team found (below). It had been working fine up until today 10/15/024.

    All other plugins are up to date.

    Any suggestions?

    I have managed to get the divi builder to load, but I have discovered there is a problem with the?wp-google-maps?? plugin.? Here are the details:

    I was able to find the error with a stack trace.  This lead me to determine the problem was not the divi builder itself but the wp-google-maps plugin.

    There was an update available for this plugin, so I took a backup of the site and I applied it.  It did not change the issue. 

    The error showed the same plugin, here is part of the error output:
    [15-Oct-2024 14:41:03 UTC] PHP Fatal error:  Uncaught Error: Call to a member function getCurrentPage() on null in /var/www/html/wp-content/plugins/wp-google-maps/includes/class.google-maps-api-loader.php:156
    #0 /var/www/html/wp-content/plugins/wp-google-maps/includes/class.google-maps-api-loader.php(188): WPGMZA\GoogleMapsAPILoader->getGoogleMapsAPIParams()
    #1 /var/www/html/wp-content/plugins/wp-google-maps-pro/legacy-core.php(215): WPGMZA\GoogleMapsAPILoader->registerGoogleMaps()

    I then disabled this plugin, and now the divi builder works.

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

  • I have the exact same error here using the Divi Builder plugin (Version 4.27.2).

    If I use the Divi Safe Mode (DIVI -> Support center -> Enable Safe Mode), I still can edit the page visually.

    Divi Builder plugin (Version 4.27.2)
    WP Go Maps (Version 9.0.41)
    WP Go Maps – Pro Add-on (Version 8.1.22)
    PHP 7.4
    WordPress 6.6.1
    (If that matters, the site is hosted on WP Engine)

    [15-Oct-2024 19:50:11 UTC] PHP Fatal error:  Uncaught Error: Call to a member function getCurrentPage() on null in /.../wp-content/plugins/wp-google-maps/includes/class.google-maps-api-loader.php:156
    Stack trace:
    #0 /.../wp-content/plugins/wp-google-maps/includes/class.google-maps-api-loader.php(188): WPGMZA\GoogleMapsAPILoader->getGoogleMapsAPIParams()
    #1 /.../wp-content/plugins/wp-google-maps-pro/legacy-core.php(214): WPGMZA\GoogleMapsAPILoader->registerGoogleMaps()
    #2 /.../wp-includes/class-wp-hook.php(324): wpgmza_enqueue_scripts('')
    #3 /.../wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
    #4 /.../wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #5 /.../wp-includes/script-loader.php(2263): do_action('wp_enqueue_scri...')
    #6 /.../wp-includes/class-wp-hook.php(324): wp_enqueue_scripts('')
    #7 /.../wp-includes/cl in /.../wp-content/plugins/wp-google-maps/includes/class.google-maps-api-loader.php on line 156
    Thread Starter mach4design

    (@mach4design)

    @lolcabanon By any chance are you also running divi-widget-builder??

    We’re seeing an issue with that as well, even though WP Go Maps is deactivated.

    Thanks!

    @mach4design no!

    Plugin Author DylanAuty

    (@dylanauty)

    Hi @mach4design & @lolcabanon

    We are sorry for the inconvenience this has caused.

    Thank you both for bringing this to our attention, we have identified the cause of this issue. In our latest updates we release a patch which disabled some of our modules from loading in Divi, as they are not needed and can lead to some performance impact when using the page builder.

    Unfortunately, it seems that if the supporting add-ons are not fully up to date, this crash can occur. We had tested this in a controlled environment, but did not experience the same issue, although we can see how this might happen in some cases.

    With that said, we will be releasing a priority update to the basic plugin which will handle this more gracefully, and prevent the error from occurring. We expect a patch to become available within the next hour or two.

    I’ll update this thread as soon as the update is released.

    Plugin Author DylanAuty

    (@dylanauty)

    Hi all,

    We have just updated the plugin to resolve this issue in instances where the add-ons are not fully up to date. Please update to version 9.0.43 to resolve the issue.

    Additionally, if you haven’t already, please reach out to us on our website so that we can get your add-ons up to date as well.

    Please do let me know if you are still experiencing issues after updating. ??

    @mach4design @lolcabanon

    lolcabanon

    (@lolcabanon)

    Hey @dylanauty ! Wonderful, thanks for the quick fix. I have updated manually since the update was not showing (probably because of the WP.ORG vs WPEngine thing going on) and it solved the issue.

    I am not sure to follow along about the add-on update… The update will not show up in the WP admin interface? It’s my client’s site, so I guess I should reach to him so that I can get the email address that bought the Pro license in the first place? The goal would be to upgrade from 8.x to 9.x?

    Thanks again! ??

    Plugin Author DylanAuty

    (@dylanauty)

    Hi @lolcabanon,

    Fantastic, I’m glad to hear this has been resolved, thank you for letting me know.

    With regards to the Pro update, unfortunately, as per the www.ads-software.com guidelines, we are not allowed to discuss or provide any support for Premium add-ons via these threads, meaning the best way forward would be for you to contact us on our website.

    That will allow us to assist you directly and explain some of the details. I do apologize for the run around in that regard.

    Hope to hear from you soon!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.