Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter bsam21

    (@bsam21)

    Correct. When I disabled w3, I hadn’t removed the object and advanced cache. Hence WP crashing. Turns out my issue was a slight corruption of the option_name “recently_activated” in the database in the options table. Deleted that and all is good. I’ve re-installed W3 now.

    Thanks for your help in this.

    Thread Starter bsam21

    (@bsam21)

    That fixed it!! Thank you very much!

    Thread Starter bsam21

    (@bsam21)

    RE: “The error you have now mentioned indicates an incorrectly implemented plugin. Deactivate all plugins and then test when the error occurs again by activating them individually.”

    I can deactivate, and even physically remove all plugins and this error continues to occur if I try to display the plugins screen:

    [19-Nov-2023 19:19:30 UTC] PHP Fatal error: Uncaught TypeError: Unsupported operand types: string + int in …/wordpress/wp-admin/includes/class-wp-plugins-list-table.php:188
    Stack trace: 0 …/wordpress/wp-admin/plugins.php(550): WP_Plugins_List_Table->prepare_items() 1 {main} thrown in …/wordpress/wp-admin/includes/class-wp-plugins-list-table.php on line 188

    Perhaps some setting is corrupt in the database?

    Thread Starter bsam21

    (@bsam21)

    I tried enabling the error log via wp-config. As soon as I do, my site fails (or won’t load) with a blank screen. Disabling it re-enables the site. Nothing is written to the log file.

    So then I installed the “Admin debug” plugin, which also modified wp-config but seems to work. No idea why my edit didn’t as the changes are the same as far as I can tell. Here are the errors when I try to access the Installed Plugins function:

    [17-Nov-2023 19:52:47 UTC] PHP Deprecated: Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead. in <snip>/wordpress/wp-includes/functions.php on line 6031
    [17-Nov-2023 19:52:47 UTC] PHP Fatal error: Uncaught TypeError: Unsupported operand types: string + int in
    <snip>/wordpress/wp-admin/includes/class-wp-plugins-list-table.php:188
    Stack trace:
    #0 <snip>/wordpress/wp-admin/plugins.php(550): WP_Plugins_List_Table->prepare_items()
    #1 {main} thrown in <snip>/wordpress/wp-admin/includes/class-wp-plugins-list-table.php on line 188

    Thread Starter bsam21

    (@bsam21)

    Thanks for the info. I removed everything and the website still works (yay!). However, the Installed Plugins page still give the above error. I re-installed the w3 plugin, but no change. I’ve manually re-enabled all my other plugins via the database active_plugins record, so my site is working as designed, but this error is concerning.

    Any other suggestions? Thanks again.

    Thread Starter bsam21

    (@bsam21)

    First of all, I installed the app via the wordpress loader. My eset found it when I went to use the app. I just reported it here. If it was a false positive, fine, but I’d rather report it than not.

    Perhaps you too should think before you say stupid things

    Thread Starter bsam21

    (@bsam21)

    Cloud,
    Either delete the plugin and install a different file manager, or go to your

    /wordpress/wp-content/plugins/wp-file-manager/lib/js/worker

    directory and delete the “quicklook.tiff.js” file.

    Thread Starter bsam21

    (@bsam21)

    Oops. As usual, I found the solution on the XNAU website, but only after I posted this issue, and it wasn’t obvious at first. Under the “Date Shifting and Other Timezone-related Issues” Tips and Tutorial, there is a “Preventing the Plugin Timezone Sync” section. It says the WP Health Check will show a warning if PDB advanced setting- “Sync php Timezone” is checked, although it doesn’t explicitly says the name of the WP error.

    If your site is showing this issue, I suggest you go to https://xnau.com/date-shifting-and-other-timezone-related-issues-in-participants-database/ and read the pros and cons of this setting.

    Regards
    M.

    Thread Starter bsam21

    (@bsam21)

    Oops. I noticed that I missed removing the number 407 in one spot in the email (I was removing them all manually from the email – my bad). That is not the issue. The bad call is.

Viewing 9 replies - 1 through 9 (of 9 total)