PHP Warning

Hey @jimk1416,

Thanks for bringing this to our attention. We will run some test on our servers to see if we can duplicate the issue and provide a fix in the next update.

You can also try PHP version 8.1. A PHP Warning is not a fatal error and will not cause any issues on the site. If you’re seeing it on the frontend, this means you have debug turned on which should be turned off unless it is a staging or development site.

Best regards,

Hey @wpcodeus

Thanks for the quick reply. I’ll keep an eye on it.

Hello @jimk1416,

We were not able to duplicate this on our servers, however, we did add an additional check to ensure that the index 0 exists before trying to access it. This change will be include in the next release.

Since we’re not able to duplicate on our end, if you could try to replace line 75 with the following to ensure it fixes the issue for you that would be extremely helpful on our end:

if(is_array($query->query_vars['taxonomy']) && isset($query->query_vars['taxonomy'][0]) && in_array($query->query_vars['taxonomy'][0], array_keys($taxonomies))) {

Best regards,

Hey @wpcodeus

I updated line 75 and uploaded the file. Will monitor.

I’m not sure exactly what action produces the error.
I can’t seem to do anything that immediately generates the error but if I check back the error is there.

Hello @jimk1416,

If you’re still receiving the warning after changing the file then it most likely is coming from your hosting setup.

I recommend reaching out to your hosting company and see if they are able to assist you.

If you’re using a caching plugin, make sure to purge it after you update the file.

As mentioned, this isn’t an error for say but a warning of an array displaying empty.

You can also try changing your PHP versions as mentioned before. 8.1 and 7.4 are still the most stable.

Hey @wpcodeus

Understood. So far so good I’ll report back on Monday. We’ll see how it goes for 2 days.
Thanks

Hey @wpcodeus

No errors to report after 2 days so I think you resolved this issue. Looking forward to the next update with the fix.

Thanks.