Title: Fatal PHP Error Last modified: February 26, 2024 --- # Fatal PHP Error * Resolved [Tara Claeys](https://wordpress.org/support/users/taraclaeys/) * (@taraclaeys) * [2 years, 3 months ago](https://wordpress.org/support/topic/fatal-php-error-39/) * Hello, * I have received a notification from our webhost, Kinsta of the following: * _PHP Fatal error: Uncaught Exception: WPGMZA\Marker ID ’10’ not found in /www/*****/ public/wp-content/plugins/wp-google-maps/includes/class.crud.php:414_ * I have updated the plugin and processed the migration to Atlas Novus as advised in the Dashboard, but the error is still being found. * Please let me know if you are aware of this and have a fix coming, or if you can recommend a solution. * Thank you! * Tara * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffatal-php-error-39%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 11 replies - 1 through 11 (of 11 total) * Plugin Author [DylanAuty](https://wordpress.org/support/users/dylanauty/) * (@dylanauty) * [2 years, 3 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17455072) * Hi Tara (@taraclaeys), * Thank you for getting in touch, we do appreciate your time. Our apologies for the trouble you are experiencing. * The error you mentioned is not a widespread issue, and instead is usually something we see if/when a marker is being accessed in the background incorrectly. This can happen for a few reasons, and it varies between installations when it does occur. In some cases, these kinds of reports can also be a result of a marker being deleted while it is being accessed by another user, for example. * One way that we can debug this a bit further is by taking a closer look at the full error log for this issue, these are usually available from your host or hosting control panel, by looking for (or requesting) your PHP error logs. These logs will contain more insight into the error, along with a history of events that took place, leading up to the error. * Could I ask that you request/download these on your side and send them over to us by opening a support ticket on [our website?](https://www.wpgmaps.com/contact-us/) This will allow me to help you get this resolved as soon as possible. * I look forward to hearing back from you. * [dennycy](https://wordpress.org/support/users/dennycy/) * (@dennycy) * [2 years, 3 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17455547) * Same for me also; * PHP Fatal error: Uncaught Exception: WPGMZA\Marker ID ‘6’ not found in /www/**\***/ public/wp-content/plugins/wp-google-maps/includes/class.crud.php:414 * Plugin Author [DylanAuty](https://wordpress.org/support/users/dylanauty/) * (@dylanauty) * [2 years, 3 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17456417) * Hi [@dennycy](https://wordpress.org/support/users/dennycy/), * I am sorry to hear you are also having trouble. As mentioned in my last reply, this usually only happens when an unexpected read of a marker occurs (sometimes due to background processes), where the marker no longer exists. * Unfortunately, we cannot confirm this without the additional PHP error log stack, usually included in a more comprehensive error log file which should be accessible via your hosting control panel. * If you could send that over to us on [our website](https://www.wpgmaps.com/contact-us/), we can take a closer look and assist in finding the reason for the exception being reported. * [johnwpc](https://wordpress.org/support/users/johnwpc/) * (@johnwpc) * [2 years, 3 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17456906) * Same issue here also on three separate websites. * Plugin Author [DylanAuty](https://wordpress.org/support/users/dylanauty/) * (@dylanauty) * [2 years, 3 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17458582) * Hi [@johnwpc](https://wordpress.org/support/users/johnwpc/), * Unfortunately, we cannot provide any additional insight until we receive PHP error logs from affected sites. We do need to take a look at the call stack, which showcases a series of events that took place prior to the exception being thrown. * To clarify, this is a failsafe built into the plugin which will prevent missing markers from being loaded onto a map. In other words, if a marker is deleted and it then accessed, the exception prevents it from being loaded. * [Ravi Makwana](https://wordpress.org/support/users/ravimakwana/) * (@ravimakwana) * [2 years, 3 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17458735) * I’m also facing the same issue: * Please check the log: * 2024/02/28 07:13:18 [error] 75941#75941: *123993 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught Exception: WPGMZA\ProMarker ID ’10’ not found in /www/se_664/public/wp-content/plugins/wp-google-maps/includes/class.crud.php: 414 Stack trace: 0 /www/se_664/public/wp-content/plugins/wp-google-maps/includes/ class.crud.php(85): WPGMZA\Crud->read(‘single-read’) 1 /www/se_664/public/wp- content/plugins/wp-google-maps/includes/class.marker.php(29): WPGMZA\Crud->__construct(‘ wpha_wpgmza’, ’10’, ‘single-read’) 2 /www/se_664/public/wp-content/plugins/wp- google-maps-pro/includes/class.pro-marker.php(28): WPGMZA\Marker->__construct(’ 10’, ‘single-read’) 3 /www/se_664/public/wp-content/plugins/wp-google-maps-pro/ includes/class.pro-marker.php(464): WPGMZA\ProMarker->__construct(’10’, ‘single- read’, false) 4 /www/se_664/public/wp-includes/class-wp-hook.php(324): WPGMZA{ closure}(’10’, ‘single-read’, false) 5 /www/se_664/public/w” while reading response header from upstream, client: 94.102.51.144, server: [http://www.sustainableengineering.co.nz](http://www.sustainableengineering.co.nz), request: “GET /wp-json/wpgmzA/v1/markers?_method=get&random=/wpgmza/v1/markers/ 10 HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php8.0-fpm-sustainableengineering. sock:”, host: “www.sustainableengineering.co.nz:17270”, referrer: “[http://sustainableengineering.biz/wp-json/wpgmzA/v1/markers?_method=get&random=/wpgmza/v1/markers/10”](http://sustainableengineering.biz/wp-json/wpgmzA/v1/markers?_method=get&random=/wpgmza/v1/markers/10”); * Plugin Author [DylanAuty](https://wordpress.org/support/users/dylanauty/) * (@dylanauty) * [2 years, 2 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17461753) * Hi [@ravimakwana](https://wordpress.org/support/users/ravimakwana/), * Thank you for sharing your logs and issue with us. * Taking a look at your error log, we can see a public request to your WordPress REST API at the following path: * ```wp-block-code wp-json/wpgmzA/v1/markers?__method=get&random=/wpgmza/v1/markers/10 ``` * This request path is not a standard request, meaning our **plugin is not calling this internally**. This is what leads us to believe that a 3rd party is attempting to access your REST API. * Coincidentally, they have targeted marker ID **10** which fails, and the error is thrown because the marker does not exist. It’s not clear what that 3rd party is attempting to do. They may be testing for a weakness in the website, or they may be attempting to scrape the marker data. * The plugin should not fail in this circumstance, but it’s worth mentioning that this is isolated to a single request, and it does not originate from our plugin. * With that said, I’ve logged the failure, along with your log and we’ll release an update to handle this more gracefully. We expect an update for this edge-case to be released early next week. * [reubenpearse](https://wordpress.org/support/users/reubenpearse/) * (@reubenpearse) * [2 years, 2 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17463690) * We are seeing similar spurious traffic on our website. I believe these are attackers looking to exploit the vulnerability detailed here: * [https://wpscan.com/vulnerability/f5687d0e-98ca-4449-98d6-7170c97c8f54/](https://wpscan.com/vulnerability/f5687d0e-98ca-4449-98d6-7170c97c8f54/) * If you’re on the latest version of WP Go Maps (9.0.32) then you should be safe, but you’ll still get PHP fatal errors until the plugin handles this scenario more gracefully. * Plugin Author [DylanAuty](https://wordpress.org/support/users/dylanauty/) * (@dylanauty) * [2 years, 2 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17465078) * Hey [@reubenpearse](https://wordpress.org/support/users/reubenpearse/), * Yes, we believe you are correct in saying that this is a pen-test based on that report. The plugin is safe from the root issue, but the REST API endpoint is not dealing with the missing marker ID’s correctly. * We’ve already prepared an internal build which solves this and makes handling more graceful. That build is going into testing today with our team and we expect it will be released early next week. * Plugin Author [DylanAuty](https://wordpress.org/support/users/dylanauty/) * (@dylanauty) * [2 years, 2 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17470883) * Hi everyone, * I’d like to give you all an update on the status of this issue. We finalized a release which should solve this issue along with various other issues within our systems. * That version moved to testing late last week and the tests have passed. We are finalizing a few last changes, and we expect to release an update within the next day or two, pending the final changes mentioned. * I will **update this thread** as soon as the update has been released. Thank you very much for your patience and understanding. * Plugin Author [DylanAuty](https://wordpress.org/support/users/dylanauty/) * (@dylanauty) * [2 years, 2 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17474701) * Hi everyone, * Just a quick update to let you all know that we have just released an update ( 9.0.33) which will handle these REST API errors more gracefully, which should prevent those errors from being thrown. * I will be marking this as resolved, but if you do still have trouble please do reach out to us [on our website](https://www.wpgmaps.com/contact-us/), or in a new thread and I’d be happy to assist! Viewing 11 replies - 1 through 11 (of 11 total) The topic ‘Fatal PHP Error’ is closed to new replies. * ![](https://ps.w.org/wp-google-maps/assets/icon-256x256.png?rev=3058363) * [WP Go Maps - Most Popular Map Plugin](https://wordpress.org/plugins/wp-google-maps/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-google-maps/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-google-maps/) * [Active Topics](https://wordpress.org/support/plugin/wp-google-maps/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-google-maps/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-google-maps/reviews/) * 13 replies * 6 participants * Last reply from: [DylanAuty](https://wordpress.org/support/users/dylanauty/) * Last activity: [2 years, 2 months ago](https://wordpress.org/support/topic/fatal-php-error-39/#post-17474701) * Status: resolved