• Resolved duber777

    (@duber777)


    Hello.

    Plugin version 1.10.0.

    On PHP 8.2.9, I get this error in the IIS server logs:

    Uncaught TypeError: fclose(): Argument #1 ($stream) must be of type resource, bool given in C:\inetpub\websites\mysite.com\wp-content\plugins\wp-super-cache\wp-cache-phase2.php:2357

    Stack trace: 0 C:\inetpub\websites\mysite.com\\wp-content\plugins\wp-super-cache\wp-cache-phase2.php(2357): fclose() 1 C:\inetpub\websites\mysite.com\wp-content\plugins\wp-super-cache\wp-cache-phase2.php(2117): wp_cache_get_ob() 2 [internal function]: wp_cache_ob_callback() 3 C:\inetpub\websites\mysite.com\wp-includes\functions.php(5349): ob_end_flush() 4 C:\inetpub\websites\mysite.com\wp-includes\class-wp-hook.php(310): wp_ob_end_flush_all() 5 C:\inetpub\websites\mysite.com\wp-includes\class-wp-hook.php(334): WP_Hook->apply_filters() 6 C:\inetpub\websites\mysite.com\wp-includes\plugin.php(517): WP_Hook->do_action() 7 C:\inetpub\websites\mysite.com\wp-includes\load.php(1252): do_action() 8 [internal function]: shutdown_action_hook() 9 {main}

    thrown in C:\inetpub\websites\mysite.com\wp-content\plugins\wp-super-cache\wp-cache-phase2.php on line 2357

Viewing 5 replies - 1 through 5 (of 5 total)
  • I presume you’re using version 1.10.0? I’m surprised you’re seeing this warning as it’s supposed to be suppressed.

    It does show there’s a problem on your site as the plugin couldn’t write to the cache files. If you enable debugging in the plugin you’ll see warnings about that.

    Thread Starter duber777

    (@duber777)

    That’s right, I use this version in conjunction with the IIS web server.

    File system-level access to the cache folder is not restricted. These entries appeared in the PHP_errors text file of Windows Server OS. I have now manually deleted the entire cache. Restarted the web server. Watching. I haven’t turned on debugging yet, but the check built into the plugin completes successfully.

    For information: the following plugins are also installed on the site: All In One WP Security, WP SMTP and CMP – Coming Soon & Maintenance Plugin and maintenance mode is enabled – the stub page.

    For the correct operation of your plugin, after all, no more settings (except for permalink) need to be made in WP (version 6.3)?

    Thread Starter duber777

    (@duber777)

    UPD: After a few minutes, it was re-reproduced out of the blue. After a few minutes, it was re-reproduced out of the blue. Diagnostic data: https://dropmefiles.com/RFhpn

    It is not very clear which directory the plugin needs access to. By means of IIS, I have configured access restriction by IP addresses to the wp-admin directory and files wp-login.php, xmlrpc.php outside. The rest of the directories are open for writing.

    Unfortunately, I’ve never used IIS, so I can’t help you configure it correctly.

    I know you won’t want to hear this, but it would be simpler to use a Linux box to run your website. That’s what the vast majority of sites use, so it’s very well-supported and understood.

    Thread Starter duber777

    (@duber777)

    I understand. I will try to find solutions on my own. Thanks for the feedback.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘PHP Fatal error’ is closed to new replies.