Search results

  1. digitalpoint

    Export and import all CF settings

    There is the existing backup/restore option, but that's more for rule definitions than settings. It has crossed my mind that a function to copy settings from zone A to zone B might be useful, I just never went down that road because no one asked for it yet. :) That being said, I'm not sure I...
  2. digitalpoint

    New Update gave 500 server error

    Sites that have a ton of individual JavaScript and CSS files loading for a single page view ended up having so many files trying to be preloaded that it would run up against limits on the HTTP response size being imposed by certain web servers and/or frontend proxies (like Cloudflare). You need...
  3. digitalpoint

    New Update gave 500 server error

    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...
  4. digitalpoint

    New Update gave 500 server error

    @grafwebcuso @JHewess update should be rolled out on wordpress.org now, so normal update in admin should sort it out.
  5. digitalpoint

    New Update gave 500 server error

    You can, but they also don’t hurt anything. Going to push out the update to WordPress.org momentarily (within the hour).
  6. digitalpoint

    New Update gave 500 server error

    Do things work as expected for you? Just want to make sure whatever was affecting you was indeed that.
  7. digitalpoint

    New Update gave 500 server error

    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...
  8. digitalpoint

    New Update gave 500 server error

    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...
  9. digitalpoint

    New Update gave 500 server error

    What happens if you comment just this line (none of the other ones)? // add_action('wp_print_footer_scripts', [$this, 'handlePrintFooterScripts'], 9999999);
  10. digitalpoint

    New Update gave 500 server error

    Another option might be to install this plugin: https://wordpress.org/plugins/query-monitor/ Will capture PHP errors and let you view them in Admin bar...
  11. digitalpoint

    New Update gave 500 server error

    Any chance you have access to PHP error log and/or WordPress debugging log?
  12. digitalpoint

    New Update gave 500 server error

    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).
  13. digitalpoint

    New Update gave 500 server error

    Anything if the guts of the methods are wrapped in try/catch? public function handleScriptLoaderTag($tag, $handle, $src) { try { if (is_string($src) && strlen($src) > 3) { $this->preload['<' . sanitize_url($src) . '>;as=script;rel=preload']...
  14. digitalpoint

    New Update gave 500 server error

    Okay... one last test (hopefully). If you uncomment those two lines, and also replace the handleScriptLoaderTag and handleStyleLoaderTag methods farther down that file (approx line #223) with this: public function handleScriptLoaderTag($tag, $handle, $src) { if (is_string($src)...
  15. digitalpoint

    New Update gave 500 server error

    I've been digging and trying to think of various "what if" situations. One possibility I've come up with (and would cause an issue regardless if the new option was enabled or not) would be an invalid script or CSS URL came through WordPress's filter mechanism. It's *supposed* to be a string, but...
  16. digitalpoint

    New Update gave 500 server error

    May be as easy as adding this to your config.php file once it's ready: define('WP_DEBUG', true); https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ Did I mention how much I hate that I can't replicate it? 😂
  17. digitalpoint

    New Update gave 500 server error

    Augh... sorry for all the testing (feel free to not do anything). I really wish I was able to replicate it somehow. In the wp-content/plugins/app-for-cf/src/DigitalPoint/Cloudflare/Base/Pub.php file, if you just remove these lines (around line #20): $cloudflareRepo = new...
  18. digitalpoint

    New Update gave 500 server error

    Ok... so not that. Did you enable the new option (preload resources)? With that enabled, it does trigger an ob_start() call so any output is buffered (allows us to add the necessary preload header after WordPress generates it's content). So maybe something going on with ob_start(), but that...
  19. digitalpoint

    New Update gave 500 server error

    Okay, so not that... 🤔 Not sure how willing you are to test things, but unfortunately I'm not able to since I can't come up with a PHP/web server combo that causes any issues. But if you are... If you make a new file on your server with this (can name it test.php or anything really): <?php...
  20. digitalpoint

    New Update gave 500 server error

    One thought that just came to mind (and maybe why I'm unable to replicate it). It could be that some servers have certain PHP functions/classes explicitly disabled (ones that are being used). Any chance you could check to see if your phpinfo shows anything for disable_functions or disable_classes?
Back
Top