Search results

No worries - it happens. I'm a software QA in my day job, so have seen my fair share of odd happenings. Good hunting though, well done!

Thank you so much for your help and prompt responses with this, much appreciated. The new update has been installed and all appears to be working. :cool:

Yes, it looks like everything's working as it should be. I've still got some of the edits in the pub file such as the 'try' and 'catch' additions. Would you recommend that I just alter the header('link:' line of code and revert the rest to how they were originally?

ok, I've amended that line of code.

staging.thecuriouscreative.co.uk everything except for Flyingpress is loaded currently, so no doubt you'll have a field-day!

This works (y)

I've had a look through the various logs, and I'm not seeing any errors that relate to the plugin. Speaking of plugins, I've been doing some fiddling around deactivating everything and then re-activating to see what might happen. Unsurprisingly, with every plugin deactivated except for AppForCF...

Unfortunately not no. I can only get it working if I leave those two original lines commented out.

Ok, so with the two lines left commented out and the new code added, everything continues to work. With the new code and the two lines uncommented, the 500 error returns.

Yep, that worked!

You might hate it even more that when I turned on WP Debugging earlier, no error messages were being shown for the plugin ;-) Will try again once the staging site is operational.

Nope, unfortunately deleting that code has made no difference. I've just spun up a staging version of the site so can do some proper testing. Just waiting for the SSL to sort itself out!

Disabling that option has made no difference, unfortunately. I also un-ticked all of the options on the plugin's main setup page, and still encountered the 500 error.

Yes, I believe that option was enabled out of the box. Let me just update the plugin to the new version again and I'll try and run it without that option switched on, just in case.

parsing the file returns: 103.21.244.0; 2a06:98c0::; ;

Sure, leave it with me. Will get back to you shortly.

disable_classes is: 'no value' disable_functions is: 'opcache_get_status'

Looking through phpinfo, output_handler shows 'no value'.

We've also experienced this issue. We initially thought it was contained to Woocommerce pages as the 500 error originally only appears when attempting to login via the /my-account URL, however after disabling caching (Flyingpress), it occurred site-wide. PHP version: 8.3.22 No logs as yet as...