Albert Peschar

That quote is about critical errors. This concerns a warning which is not a critical error.

It is up to custom error handling code, such as that implemented by Query Monitor, to respect error suppression. But something changed in PHP 8 that means that Query Monitor’s code needs to be updated in order to correctly detect suppressed errors.

I’ve left a note on Query Monitor’s support forum.

If they get around to updating this, it should make sure that these suppressed errors show up as such in Query Monitor.

This is not a bug. At least not in this plugin.

The “@” error suppression operator is used to prevent this warning from being logged, as it is expected during normal operation. Query Monitor apparently does not respect this.

This is not a bug. At least not in this plugin.

The “@” error suppression operator is used to prevent this warning from being logged, as it is expected during normal operation. Query Monitor apparently does not respect this.

Hi @alx359,

This should be fixed in version 2.14.

–Albert

Hi @tingwe,

This is harmless, but it is indeed unintended. This should be fixed now in the latest version of PhastPress (2.13).

–Albert

Thanks for reporting this bug.

I’ve just released PhastPress 2.12 which should resolve the issue.

Hi @shirtguy72,

Thanks for reporting this bug.

I’ve just released PhastPress 2.12 which should resolve the issue.? Let me know if it doesn’t work for you.

–Albert

Usually this is due to a server configuration error which causes this URL to be unreachable:

yoursite.com/wp-content/plugins/phastpress/phast.php/data

Your hosting provider should be able to correct this issue.

If you provide the URL to a site where the problem is visible, I can check it for you.

Your server (Nginx) is configured not to support additional parameters after PHP script filenames. That’s why this URL does not work as it should:

https://demo3.vincentczb.top/wp-content/plugins/phastpress/phast.php/c2VydmljZT1idW5kbGVyJnI9QUs2UXRlNkRxMmMmcj1CNTFxbjJHQmZKYyZyPVhXcm4wdkpaWUp3JnI9bHZmaWlrWmtUeWMmcj10MllwUVgzZWtNYw.q.js

You can adjust your server configuration according to Nginx’s example:

https://www.nginx.com/resources/wiki/start/topics/examples/phpfcgi/

The important part is fastcgi_split_path_info.

This is usually a server configuration issue that causes URLs in /wp-content/plugins/phastpress/phast.php/something not to work.

If you link your actual site with the issue I can check whether this is the case.

It looks like the JavaScript in the plugin fails to correctly determine the URL to the marker image.

Usually that is because the script tries to find its own <script> tag and uses the URL; but this doesn’t work because PhastPress changes the URL.

You can either disable PhastPress for this script and see if that helps (see the instructions in the FAQ) or hire a developer to debug the way that the script determines the URL for the marker image.

I’m afraid I can’t help until I see the actual errors somewhere, and can see the WordPress error log as well as the request/response logs in the browser.

You can try setting up another testing site and using the migration tool to move there, and seeing if you can reproduce the problem there.

Apparently it should have been fixed already in Local WP.

https://community.localwp.com/t/missing-pdo-extension-for-php-8-1-under-linux/33367/4

If you’re running the latest version, perhaps try the beta if available. Otherwise, you could ask Local WP to add this extension if it turns out that they haven’t, after all.

Looks like this is a paid plugin and not publicly available to download.

I can help if you provide a Duplicator archive of a site (could be yours or a testing site) that is displaying the problem.

Your server configuration is preventing access to this URL:

https://livingtowersflkeys.com/wp-content/plugins/phastpress/phast.php

Access to this URL is required for PhastPress to operate. Contact your hosting provider to unblock this URL.