Green chilli or chili,Free slots no download.REGISTER NOW GET FREE 888 PESOS REWARDS!

All my locally activated plugins are randomly deactivating on multisite sites

thewoosh — Tue, 21 May 2024 09:54:34 +0000

Since I migrated my WordPress multisite and upgraded everything, I have been having a helluva problem.

At seemingly random intervals (sometimes minutes, sometimes a day or 2), all the plugins that are locally (not network-wide) activated, deactivate themselves. This happens on all sites in the multisite! Network activated plugins are not affected.

This has been going on for a couple of weeks and is driving me nuts!

Can anyone suggest any debugging methods I can use and stuff to look out for or suggest any ideas as to what might be causing the problem? I would be realy grateful for more sophisticated debugging suggestions than ‘switch off all the plugins and revert to default theme and then reintroduce one by one’ – which is not an option!

I am now running WordPress Multisite 6.5.3 on PHP 8.0 (or 8.2 – I have tried both) on Ubuntu 22.04LTS. I am server admin.

Many thanks for giving this your attention

Events Calendar still deaciviating…

thewoosh — Sun, 19 May 2024 13:30:20 +0000

I am still having the problem that after a random period (sometimes several days), the events calendar plugin just deactivates itself on my Multisite site.

This seems to be since upgrading to WordPress (Multisite) 6.5.2. I have upgraded Events calender to version 6.5 and it’s only activated on that one one site. I reactivate it and it works for a while then, I see it has deactivated again. I have already gone down from running PHP 8.2 to PHP 8.0 on your suggestion but to no avail. I am on Ubuntu 24.04 LTS.

I know that your advice is to remove all other plugins and got to a default WordPress theme but this is not practical. Is there any events I can look out for to debug this? I have ‘Debug This’ plugin installed and have access to server logs…

Any suggestions would be very welcome.

Thanks

Problems with 6.3.7 and WordPress multisite 6.5.2

thewoosh — Wed, 01 May 2024 14:00:38 +0000

Hi – I’m having all sorts of problems with the events calendar plugin since upgrading to WordPress (Multisite) 6.5.2. I have Events calender version 6.3.7 installed (running PHP 8.2 on Ubuntu). What happens is that the plugin keeps getting deactivated. When I reactivate, I am told I need to upgrade my events. Whwnever I do this, it takes ages and always stops short of the total – although one time it did get through the lot and told me that some of th eevents where no longer gonna work because I set them up as recurring events with the pro version which I no longer have installed. I trashed these events, but since then it has never completed the scan.
I tried to upgrade to 6.4 in the hope that this might fix the problem, but it just gets stuck on installing and never finishes…

Any suggeestions for a way out of htis mess?

Constantly Deactiving Itself

rayeason — Thu, 01 Feb 2024 09:47:33 +0000

Hello and good day.

The plugin is constantly deactivating itself.

I am not sure why.

I have performed plugin conflict test and increased server max execution with no luck.

Any pointers would be welcome.

https://drive.google.com/file/d/1dwlH4L_Une_osCyJtfThylh5rvhrtf7z/view?usp=drivesdk

I have performed the Jetpack connect/reconnect several times and it still persists.

Here are my Fatal error logs as requested:

2024-01-02T01:00:23+00:00 CRITICAL Uncaught GuzzleHttp\Exception\ClientException: Client error: POST https://api.medium.com/v1/users/144d6a1d80d20f268b3645959ee8f23f4d41fa115af0135030c861ac438f33c28/posts resulted in a 403 Forbidden response: run() #5 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/promises/src/Promise.php(224): GuzzleHttp\Promise\Promise->invokeWaitFn() #6 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/promises/src/Promise.php(269): GuzzleHttp\Promise\Promise->waitIfPending() #7 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/promises/src/Promise.php(226): GuzzleHttp\Promise\Promise->invokeWaitList() #8 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/promises/src/Promise.php(62): GuzzleHttp\Promise\Promise->waitIfPending() #9 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/guzzle/src/Client.php(187): GuzzleHttp\Promise\Promise->wait() #10 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/medium/vendor/jonathantorres/medium-sdk/src/Client.php(135): GuzzleHttp\Client->request() #11 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/medium/vendor/jonathantorres/medium-sdk/src/Medium.php(215): JonathanTorres\MediumSdk\Client->makeRequest() #12 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/class-wpw-auto-poster-md-posting.php(400): JonathanTorres\MediumSdk\Medium->createPost() #13 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/class-wpw-auto-poster-md-posting.php(63): Wpw_Auto_Poster_Medium_Posting->wpw_auto_poster_post_to_medium() #14 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/admin/class-wpw-auto-poster-admin.php(1621): Wpw_Auto_Poster_Medium_Posting->wpw_auto_poster_medium_posting() #15 /var/www/reasonelectronics.com/wp-includes/class-wp-hook.php(324): Wpw_Auto_Posting_AdminPages->wpw_auto_poster_scheduled_cron() #16 /var/www/reasonelectronics.com/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #17 /var/www/reasonelectronics.com/wp-includes/plugin.php(565): WP_Hook->do_action() #18 /var/www/reasonelectronics.com/wp-cron.php(191): do_action_ref_array() #19 {main} thrown in /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113 2024-01-02T02:00:25+00:00 CRITICAL Uncaught GuzzleHttp\Exception\ClientException: Client error: POST https://api.medium.com/v1/users/144d6a1d80d20f268b3645959ee8f23f4d41fa115af0135030c861ac438f33c28/posts resulted in a 403 Forbidden response: run() #5 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/promises/src/Promise.php(224): GuzzleHttp\Promise\Promise->invokeWaitFn() #6 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/promises/src/Promise.php(269): GuzzleHttp\Promise\Promise->waitIfPending() #7 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/promises/src/Promise.php(226): GuzzleHttp\Promise\Promise->invokeWaitList() #8 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/promises/src/Promise.php(62): GuzzleHttp\Promise\Promise->waitIfPending() #9 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/guzzle/src/Client.php(187): GuzzleHttp\Promise\Promise->wait() #10 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/medium/vendor/jonathantorres/medium-sdk/src/Client.php(135): GuzzleHttp\Client->request() #11 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/medium/vendor/jonathantorres/medium-sdk/src/Medium.php(215): JonathanTorres\MediumSdk\Client->makeRequest() #12 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/class-wpw-auto-poster-md-posting.php(400): JonathanTorres\MediumSdk\Medium->createPost() #13 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/class-wpw-auto-poster-md-posting.php(63): Wpw_Auto_Poster_Medium_Posting->wpw_auto_poster_post_to_medium() #14 /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/admin/class-wpw-auto-poster-admin.php(1621): Wpw_Auto_Poster_Medium_Posting->wpw_auto_poster_medium_posting() #15 /var/www/reasonelectronics.com/wp-includes/class-wp-hook.php(324): Wpw_Auto_Posting_AdminPages->wpw_auto_poster_scheduled_cron() #16 /var/www/reasonelectronics.com/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #17 /var/www/reasonelectronics.com/wp-includes/plugin.php(565): WP_Hook->do_action() #18 /var/www/reasonelectronics.com/wp-cron.php(191): do_action_ref_array() #19 {main} thrown in /var/www/reasonelectronics.com/wp-content/plugins/social-auto-poster/includes/social/libraries/tumblr/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113 2024-01-02T07:47:18+00:00 CRITICAL Uncaught Error: Call to a member function get_attributes() on bool in /var/www/reasonelectronics.com/wp-content/plugins/woocommerce/includes/class-wc-cart.php:1052 Stack trace: #0 /var/www/reasonelectronics.com/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php(877): WC_Cart->add_to_cart() #1 /var/www/reasonelectronics.com/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php(3678): WooSEA_Get_Products->woosea_get_shipping_cost() #2 /var/www/reasonelectronics.com/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(4770): WooSEA_Get_Products->woosea_get_products() #3 /var/www/reasonelectronics.com/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(4676): woosea_continue_batch() #4 /var/www/reasonelectronics.com/wp-includes/class-wp-hook.php(324): woosea_create_all_feeds() #5 /var/www/reasonelectronics.com/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #6 /var/www/reasonelectronics.com/wp-includes/plugin.php(565): WP_Hook->do_action() #7 /var/www/reasonelectronics.com/wp-cron.php(191): do_action_ref_array() #8 {main} thrown in /var/www/reasonelectronics.com/wp-content/plugins/woocommerce/includes/class-wc-cart.php on line 1052 2024-01-02T07:51:43+00:00 CRITICAL Uncaught Error: Call to a member function get_attributes() on bool in /var/www/reasonelectronics.com/wp-content/plugins/woocommerce/includes/class-wc-cart.php:1052 Stack trace: #0 /var/www/reasonelectronics.com/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php(877): WC_Cart->add_to_cart() #1 /var/www/reasonelectronics.com/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php(3678): WooSEA_Get_Products->woosea_get_shipping_cost() #2 /var/www/reasonelectronics.com/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(4770): WooSEA_Get_Products->woosea_get_products() #3 /var/www/reasonelectronics.com/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(4676): woosea_continue_batch() #4 /var/www/reasonelectronics.com/wp-includes/class-wp-hook.php(324): woosea_create_all_feeds() #5 /var/www/reasonelectronics.com/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #6 /var/www/reasonelectronics.com/wp-includes/plugin.php(565): WP_Hook->do_action() #7 /var/www/reasonelectronics.com/wp-cron.php(191): do_action_ref_array() #8 {main} thrown in /var/www/reasonelectronics.com/wp-content/plugins/woocommerce/includes/class-wc-cart.php on line 1052

Jetpack Disconnecting/Deactivating

rayeason — Thu, 01 Feb 2024 00:50:46 +0000

Hello and good day.

The plugin is constantly deactivating itself.

I am not sure why.

I have performed plugin conflict test and increased server max execution with no luck.

Any pointers would be welcome.

https://drive.google.com/file/d/1rqQjO3uDofp2LskquWGj8wxmzdMnOh2m/view?usp=drivesdk

Constantly Deactiving Itself

rayeason — Mon, 15 Jan 2024 00:43:40 +0000

Hello and good day.

The plugin is constantly deactivating itself.

I am not sure why.

I have performed plugin conflict test and increased server max execution with no luck.

Any pointers would be welcome.

https://drive.google.com/file/d/1dwlH4L_Une_osCyJtfThylh5rvhrtf7z/view?usp=drivesdk

Wordfence is deactivating on its own A

mrg14071972 — Sat, 30 Sep 2023 17:08:33 +0000

This is the third time the last 5 months I’ve found Wordfence deactivated on my site. I logged in to check my members status and Wordfence was not active.
The previous 2 times after the reactivation and the full scan it found some problematic files that I deleted and then it didn’t find anything wrong.
A little while ago today I discovered again that it is not active and I activated it and I am doing a scan again and there is no problem.
After searching I found someone else with the same problem but I didn’t read anywhere that you give him a solution, I also talked to the hosting company and they don’t block anything from their side, I actually oppose it for your plugin.

is there a log file that tells you when and why it was deactivated?
Is there a safeguard that prevents the plugin from being deactivated?

Thanks.

What happens if i deactivate the plugin? Will I lose all tags and categories?

jobergstromtds — Thu, 17 Aug 2023 09:23:05 +0000

We need to do some tests on our website, and our Theme Support has asked us to deactivate all our plugins temporarily. But I’m worried that deactivating the Post Tags and Categories for Pages plugin will remove all the tags and categories we have allocated to pages since installing and activating the plugin?

Fatal Error when deactivating plugin

nickcapretta1 — Tue, 11 Oct 2022 23:44:23 +0000

Hi, I decided to go another route seeing I need support for recurring donations on my webpage, but when I try to deactivate this plugin I receive a fatal WordPress error. I can deactivate/reactivate other plugins without issue, just not this one.

where does aiowps store is settings

branhampaul — Wed, 05 Jan 2022 20:46:09 +0000

This question is coming because when the plugin “all in one WordPress security” is deactivated and deleted, and even when its’ database is deleted from the database tables; upon reinstalling the plugin, the settings are preserved.

Why is this happening? Where are the settings data stored, and not removed upon deactivating?

This is risky to some WordPress environment – this character when it locks admins out makes it difficult to recuperate.