CK MacLeod

Bad news: The error is turning up again… even after the attempt to fix it.

Great plugin – works quite well out of the box. Support is responsive, too.

Thanks Kris,

I’m a colleague of @leebrewerftl’s, and have applied your recommended fix.

FYI, the DB_COLLATE line in our wp-config.php was
define( 'DB_COLLATE', '' );

We’ll give it a little time to make sure the errors stay away, but looks good so far.

Also, your plugin is great, even the free version. ?? I’ll make sure that we’ve rated it.

• This reply was modified 1 month, 3 weeks ago by CK MacLeod.

Sorry for the delay in replying: Yes, the issue appears to have been fixed.

Actually, the fix does not seem to work. To double-check, I re-installed the version from the link above, made sure I’d removed our own CSS fix code, cleared browser and site caches, and the pretty player loses opacity. When I restore our fix, it comes back.

Sorry, I did not realize you were actually awaiting a reply.

I replaced the prior 4.02 with the new one. Maybe because the version # hasn’t changed – I haven’t looked into the details – I needed to clear caches before the fix took effect.

I’ll check further with colleagues when they return to work next week.

Thanks!

• This reply was modified 9 months, 2 weeks ago by CK MacLeod.

The update worked in our staging environment – but not in our live environment. When trying to save settings we still get the “Error Saving Settings,” and the aforementioned 400 error in DevTools Console: [siteurl]/wp-json/wc/v3/wc_stripe/settings?_locale=user

Oops… somehow the installation missed the update or update notice. I’ve replaced 3.7.1 (reverted) with 3.7.2, and all is good.

Sorry!

Sorry, one last note: The logged errors are, as you probably know, common for PHP 8.1, which is sensitive to undefined variables

I’ll note also that reverting to the old version of class.client.autolinks.php also resolved additional errors we were getting – and that were putting up some front end critical errors – that on the surface did not look likely to be connected.

…wondering if I should start a separate thread.

• This reply was modified 1 year, 11 months ago by CK MacLeod.
• This reply was modified 1 year, 11 months ago by CK MacLeod.

I suspect that the fix, whatever it was, is the source of a huge upsurge of errors – about 100 per second – of the following type that we are now seeing in our PHP logs:

[13-Apr-2023 15:56:14 UTC] PHP Warning: Undefined variable $case in /var/web/site/public_html/wp-content/plugins/simple-tags/inc/class.client.autolinks.php on line 839
[13-Apr-2023 15:56:14 UTC] PHP Warning: Undefined variable $rel in /var/web/site/public_html/wp-content/plugins/simple-tags/inc/class.client.autolinks.php on line 839
[13-Apr-2023 15:56:14 UTC] PHP Warning: Undefined variable $case in /var/web/site/public_html/wp-content/plugins/simple-tags/inc/class.client.autolinks.php on line 839
[13-Apr-2023 15:56:14 UTC] PHP Warning: Undefined variable $rel in /var/web/site/public_html/wp-content/plugins/simple-tags/inc/class.client.autolinks.php on line 839

Deleted – fixed – not your plugin.

Also getting similar issues:

js?v=3.exp&key=AIzaSyAurX0cbiQ5BWsRx4GqQXJMmeqgAn_4nNI&libraries=places:109 

Uncaught TypeError: Cannot read properties of null (reading 'addEventListener')
    at _.wf (js?v=3.exp&key=AIzaSyAurX0cbiQ5BWsRx4GqQXJMmeqgAn_4nNI&libraries=places:109:208)
    at _.nf.addDomListener (js?v=3.exp&key=AIzaSyAurX0cbiQ5BWsRx4GqQXJMmeqgAn_4nNI&libraries=places:274:337)
    at String.<anonymous> (map_data.js:4:72)
    at Function.each (jquery.min.js:2:3003)
    at HTMLDocument.<anonymous> (map_data.js:2:41)
    at HTMLDocument.dispatch (jquery.min.js:2:43064)
    at v.handle (jquery.min.js:2:41048)
    at Object.trigger (jquery.min.js:2:71515)
    at HTMLDocument.<anonymous> (jquery.min.js:2:72110)
    at Function.each (jquery.min.js:2:3003)

I’ve had issues in the past with the Customizer failing under certain scenarios, but never producing 404s, and never with core updates and theme installation.

Oddly enough the access log for this site at the host is in Chinese. I’ll see what more they can tell me. If it is some host weirdness – would not be the absolutely first time – it still seems odd that some difference between 5.9 and 5.9.3 would trigger it.