- Item seller digitalpoint
- Featured
New Update gave 500 server error
- Thread starter grafwebcuso
- Start date
Anything if the guts of the methods are wrapped in try/catch?
PHP:
public function handleScriptLoaderTag($tag, $handle, $src)
{
try {
if (is_string($src) && strlen($src) > 3)
{
$this->preload['<' . sanitize_url($src) . '>;as=script;rel=preload'] = true;
}
}
catch(\Exception $e){
wp_die($e->getMessage());
}
return $tag;
}
public function handleStyleLoaderTag($tag, $handle, $href)
{
try {
if (is_string($href) && strlen($href) > 3 && strpos($href, '/ie.css') === false)
{
$this->preload['<' . sanitize_url($href) . '>;as=style;rel=preload'] = true;
}
}
catch(\Exception $e){
wp_die($e->getMessage());
}
return $tag;
}grafwebcuso
New member
Will there be an update that does not throw the error? I am running PHP 8.3
Still trying to pinpoint it exactly. Haven’t been able to replicate it on my end, so limited to what others can give me (as far as info).
Unfortunately not no. I can only get it working if I leave those two original lines commented out.
Any chance you have access to PHP error log and/or WordPress debugging log?
Another option might be to install this plugin:
wordpress.org
Will capture PHP errors and let you view them in Admin bar...
Query Monitor – The developer tools panel for WordPress
Query Monitor is the developer tools panel for WordPress and WooCommerce.
Will capture PHP errors and let you view them in Admin bar...
What happens if you comment just this line (none of the other ones)?
PHP:
// add_action('wp_print_footer_scripts', [$this, 'handlePrintFooterScripts'], 9999999);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, everything worked. However, there are a few plugins that, when enabled as well, caused the 500 error to return. Some examples are: Fluent Forms Pro, Kadence Blocks Pro, and WooCommerce.
Leave it with me while I try your most recent two posts.
Leave it with me while I try your most recent two posts.
Do you have an example URL of your site (even if the plugin is disabled currently)? One possibility might be that your web server has a limitation on the size of the HTTP response headers (normally there's a limitation on the request headers, but not response headers). If that's the case, then the issue would be upstream of WordPress/PHP stack, so PHP isn't going to throw an error (would be coming from web server itself). Seeing combination of plugins causing the issue, but not individual ones may be something along the lines of different plugins are adding HTTP response headers, but it's only when the total size of all the response headers gets larger than a certain amount, the web server decides it's not doing it.
...although that wouldn't explain it happening even with the preload resources option disabled (headers are only added when it's enabled). So maybe that whole thought is irrelevant.
Still would be interested in the URL if possible... curious if there's an insane amount of individual JavaScript and CSS files that might be too many to realistically preload.
...although that wouldn't explain it happening even with the preload resources option disabled (headers are only added when it's enabled). So maybe that whole thought is irrelevant.
Still would be interested in the URL if possible... curious if there's an insane amount of individual JavaScript and CSS files that might be too many to realistically preload.
This works 👍
staging.thecuriouscreative.co.uk
everything except for Flyingpress is loaded currently, so no doubt you'll have a field-day!
So I was able to get a 502 error from Cloudflare... Basically I took all the scripts and CSS you have on that page and then preloaded each of them 10 times. Was just seeing if Cloudflare's side has a limit on HTTP response headers (apparently they do when it gets very, very big).
Given that, it probably does make sense to limit how many resources are preloaded (regardless if the limitation is certain web server configs or a proxy like Cloudflare). So one more thing to test if you have the time...
Change this:
PHP:
header('Link: ' . implode(',', array_keys($this->preload)), false);...to this:
PHP:
header('Link: ' . implode(',', array_slice(array_keys($this->preload), 0, 10)), false);Will limit preloading to 10 items (a site is going to start seeing diminishing returns if they are preloading a zillion files even if their site needs them).
Do things work as expected for you? Just want to make sure whatever was affecting you was indeed that.
You can, but they also don’t hurt anything. Going to push out the update to WordPress.org momentarily (within the hour).
@grafwebcuso @JHewess update should be rolled out on wordpress.org now, so normal update in admin should sort it out.
No worries… and also sorry about the trouble.
Makes sense now why only a couple people saw it and I couldn’t replicate it though (only on sites loading a ton of individual JavaScript and CSS files causing the headers in HTTP response to be overloaded… not technically a PHP error to be logged or seen). 😬
Similar threads
