Critical Error | Invalid require_once() call

  • Resolved klein1

    (@klein1)


    1 year, 5 months ago

    Hi guys,

    your latest update (9.0.25) has a fatal error in it’s code, which makes the wordpress page fail to load.
    I don’t know if this only affects me, if not, here is my fix.

    Error log:
    [11-Oct-2023 08:26:04 UTC] PHP Fatal error: require_once(): Failed opening required ‘/home/XXX/public_html/wp-content/plugins/wp-google-maps/includes/../class.selector-to-xpath.php’ (include_path=’.:/opt/alt/php73/usr/share/pear’) in /home/XXX/public_html/wp-content/plugins/wp-google-maps/includes/class.dom-element.php on line 8

    I already found the issue and was able to solve this by editing the includes/class.dom-element.php

    Issuer: Bad require_once() call in class.dom-element.php:15
    require_once(plugin_dir_path(__FILE__) . ‘../class.selector-to-xpath.php’);

    How have I fixed this?
    require_once(plugin_dir_path(__FILE__) . ‘class.selector-to-xpath.php’);

    • This topic was modified 1 year, 5 months ago by klein1.
    • This topic was modified 1 year, 5 months ago by klein1. Reason: Formatting
Viewing 13 replies - 1 through 13 (of 13 total)

  • Can confirm it’s a wider issue – also had it happen on one of our sites (deactivated the rest pre-update out of caution).

    Hello everyone, I have the same problem when updating.

    Same here on all websites, please fix this as soon as possible.

    • This reply was modified 1 year, 5 months ago by fruchtfliege.

    Can confirm. Rolled back to 9.0.24

    Plugin Author DylanAuty

    (@dylanauty)

    Hi @klein1,

    Thank you for reporting the issue and the solution. We are deploying a patch for this at the moment. I will update this thread once that has been completed.

    Thread Starter klein1

    (@klein1)

    Hi @dylanauty
    Thank you for your fast response in this problem.

    I have also created a pull request
    Critical error fixed due to require_once() call with wrong path by KleinDevDE · Pull Request #1055 · CodeCabin/wp-google-maps (github.com)

    • This reply was modified 1 year, 5 months ago by klein1. Reason: Fixed spelling
    Plugin Author DylanAuty

    (@dylanauty)

    Hi @klein1,

    Thank you for the PR, I’ve looked that over and merged it into core. I will update the public repo later today as well.

    I’d also like to confirm that the update has been released, it may become available at different times for people in this thread due to the way WordPress delivers updates but you all should see it shortly.

    For those interested, more context as to how the issue slipped through on our side can be found in a comment on the PR from @klein1.

    Our apologies for the inconvenience and frustration this has caused. Thank you all for your patience.

    Tagging you all to ensure you are notified: @nicksatkovich @fruchtfliege @carret @toncijajic

    @dylanauty on the sites with the Pro Add-on, we get this fatal error after updating to 9.0.26:

    Fatal error: Uncaught Error: Class 'WPGMZA\ProSettingsMigrator' not found in /srv/htdocs/wp-content/plugins/wp-google-maps-pro/includes/class.pro-map.php:32 Stack trace: #0 /srv/htdocs/wp-content/plugins/wp-google-maps-pro/includes/class.pro-map.php(361): WPGMZA\ProMap->__construct(Array, NULL) #1 /wordpress/core/6.3.1/wp-includes/class-wp-hook.php(310): WPGMZA\{closure}(Array) #2 /wordpress/core/6.3.1/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array) #3 [internal function]: apply_filters('wpgmza_create_W...', Array) #4 /srv/htdocs/wp-content/plugins/wp-google-maps/includes/class.factory.php(47): call_user_func_array('apply_filters', Array) #5 /srv/htdocs/wp-content/plugins/wp-google-maps/includes/class.database.php(319): WPGMZA\Factory::createInstance(Array) #6 /srv/htdocs/wp-content/plugins/wp-google-maps/includes/class.plugin.php(310): WPGMZA\Database->onFirstRun() #7 /srv/htdocs/wp-content/plugins/wp-google-maps/includes/class.plugin.php(253): WPGMZA\Plugin->onFirstRun() #8 /srv/htdocs/wp-content/plugins/wp-google-maps/includes/class.plugin.php(1185): WPGMZA\Plugin->onActivated() #9 /wordpress/core/6.3.1/wp-includes/class-wp-hook.php(310): WPGMZA\{closure}('') #10 /wordpress/core/6.3.1/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters('', Array) #11 /wordpress/core/6.3.1/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #12 /wordpress/core/6.3.1/wp-admin/plugins.php(194): do_action('activate_wp-goo...') #13 {main} thrown in /srv/htdocs/wp-content/plugins/wp-google-maps-pro/includes/class.pro-map.php on line 32
    Plugin Author DylanAuty

    (@dylanauty)

    Hi @toncijajic,

    Unfortunately we aren’t allowed to discuss any Pro related issues within these forums, as per the www.remarpro.com guidelines (which only allows us to address basic version issues).

    With that said, this doesn’t appear to be related to the issue in this thread, but of course, we’d like to get this resolved for you as soon as possible. Please can I ask you to reach out to us on our website so that someone from the team can get this resolved as soon as possible.

    @dylanauty the reported error is caused by trying to activate the base plugin post-update. So, not a Pro plugin issue, but a base plugin issue with sites that have a Pro plugin alongside it.

    Want me to open a separate thread for it?

    Plugin Author DylanAuty

    (@dylanauty)

    Hey @toncijajic,

    Thank you for the additional information, but yes, unfortunately because of the specific combination (Pro needing to be present as well), and the fact that the error is coming from a Pro file (even if it is triggered by basic), we must move further discussion off of www.remarpro.com.

    I realize that may be inconvenient, but it is something which is actively enforced by the WordPress moderation team, and may result in this thread being closed prematurely if we do not do so.

    Thread Starter klein1

    (@klein1)

    @dylanauty you’re welcome
    And thank you again for the very fast response and the fast release ??

    I close the thread, respectively mark it as solved

    Plugin Author DylanAuty

    (@dylanauty)

    Thank you for all your help @klein1 > Have a great day.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Critical Error | Invalid require_once() call’ is closed to new replies.