walkinverse
Forum Replies Created
-
Forum: Plugins
In reply to: [The Events Calendar] Multiple Sites Using Plugin CrashedDo I need to pay for a license to get support? Not sure what to do at this point. I am just trying to test out the plugin and can’t afford to have it take my site down again. I hate to be strong-armed into a subscription until I can try something first. @bordoni any idea on what we can do?
Forum: Plugins
In reply to: [The Events Calendar] Multiple Sites Using Plugin CrashedI just updated all plugins on both test and prod. Now running Version 6.2.0.1 with WordPress 6.3.1. Also an running again in production.
Forum: Plugins
In reply to: [The Events Calendar] Multiple Sites Using Plugin Crashed@jhuffman @dviss @bordoni I just updated my test server to use wordpress 6.3.1. as I saw they cut a new release and it seems to have resolved the issue. It might have had something to do with 6.3. I have not tried this in production. I turned off all plugins and used the default theme. Upgraded to 6.3.1 and activated the calendar plugin. Didn’t crash. I then turned back on the theme and walked each plugin one by one. Didn’t crash.
Forum: Plugins
In reply to: [The Events Calendar] Multiple Sites Using Plugin CrashedTherein lies the issue. As soon as we turn the plugin on the website crashes and we have to manually delete it on the back end. We cant even test to see where the error is. It literally blows up wordpress.
Forum: Plugins
In reply to: [The Events Calendar] Multiple Sites Using Plugin CrashedYou would think. I even told them I was going to run a trail and if I liked it I have multiple site where I would have (past tense) bought a license. Do you know of any other reputable calendar plugin?
Forum: Plugins
In reply to: [The Events Calendar] Multiple Sites Using Plugin CrashedUnfortunately, they are not willing to help. I just got this response from their support team. Even though I told them others are having issues. @tristan083
Hi there,
Thank you for sharing that, we’ll definitely investigate this issue if we find similar cases, but as for now I couldn’t find any reported bug regarding this, and the issue seems to be related to your site configuration.
If you don’t have an active license, please post this issue on wordpress.org community forum where we provide support for our free users.
Please let me know if you have further questions.
Best regards,
Atousa- This reply was modified 2 years, 8 months ago by walkinverse.
Forum: Plugins
In reply to: [The Events Calendar] Plugin has broken siteThere is no conflict. This has also happened to others. I opened a ticket here before this one. https://wordpress.org/support/topic/multiple-sites-using-plugin-crashed/
On my test server I removed all plugins, and went to the default theme. The only plugin was the calendar. it crashed the site.
Forum: Plugins
In reply to: [The Events Calendar] Multiple Sites Using Plugin CrashedI have two. One is Digitalocean with spanel. And the other is https://www.scalahosting.com/.
I host many sites and when wordpress upgraded it broke them all. Funny thing is, I didnt even think about it as I always update on test first. Luckily only 2 sites were using the event calendar plugin. Lesson learned never trust any updates. I do not think it’s the hosting platform.
Forum: Plugins
In reply to: [The Events Calendar] Multiple Sites Using Plugin CrashedI opened a ticket on their main support, but they won’t address it as I do not have a license key. I mentioned they need to check the forum as multiple people are having this issue.
Forum: Plugins
In reply to: [The Events Calendar] Multiple Sites Using Plugin Crashed@tristan083 no worries, it happens. I understand.
It’s with two different sites with different themes. Same version of the Events Calendar, the most current. It occurs with the Events Calendar Version: 6.2.0.1. I deleted Event Tickets and it still occurred.
One site uses generatepress Version 3.3.1 and the other Astra pro Version 4.2.2.
WordPress on both: Version 6.3
PHP on both: PHP version 7.4.33
I tested 8 on a test server and same error.
Also, I removed all plugins from the test server and used a default theme with and same error.Forum: Fixing WordPress
In reply to: CRON no longer works after updateThank you. Unfortunately, this is an actual bug in PHP 7.4 The developers have discussed it in their forums. IT was suppose to be fixed, but never was. It has to do with fpm getting caught in a loop. If you only host one site, you will never hit it. I host multiple sites and that is how I found the issue.
https://github.com/php/php-src/issues/8072
It causes your websites to timeout and lock. It has to be fixed at the PHP community level.
https://bugs.php.net/bug.php?id=74709
It’s an old issue that has not been fixed. That is why I had to move to 8.
Thank you again for your suggestions.
Forum: Fixing WordPress
In reply to: CRON no longer works after updateI cant use 7.4 as it causes issue with the FPM-PHP. It’s a known bug. So in order to remove that bug you have to move to version 8. The cpanel tech guy raised it way up the chain. TI causes high CPU and other issues. I am using PHP 8. I guess it’s a version 8 issue with PHP then?
Forum: Fixing WordPress
In reply to: CRON no longer works after updateIt is definitely a wordpress bug. I even removed my theme as well. Now it’s just bare bones. Not a single plugin is running. WordPress crons wont fire.
This keeps showing it wont run:
wp_privacy_delete_old_export_files()
wp_scheduled_delete()
delete_expired_transients()
wp_update_plugins()All arguments show as none. Which kind of aligns with the error. Which makes it look like an actual bug in the wordpress core.
When I try to run cron via url, cli or the plugin I get this:
[12-Apr-2022 16:33:07 UTC] PHP Warning: Undefined array key "args" in /home/public_html/wp-cron.php on line 124 [12-Apr-2022 16:33:07 UTC] PHP Warning: Undefined array key "args" in /home/public_html/wp-cron.php on line 127 [12-Apr-2022 16:33:07 UTC] PHP Warning: Undefined array key "args" in /home/public_html/wp-cron.php on line 138 [12-Apr-2022 16:33:07 UTC] <strong>PHP Fatal error: Uncaught TypeError</strong>: count(): <strong>Argument #1 ($value) must be of type Countable|array, null given</strong> in /home/public_html/wp-includes/class-wp-hook.php:292 Stack trace: #0 /home/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', NULL) #1 /home/public_html/wp-includes/plugin.php(522): WP_Hook->do_action(NULL) #2 /home/public_html/wp-cron.php(138): do_action_ref_array('wp_privacy_dele...', NULL) #3 {main} thrown in /home/public_html/wp-includes/class-wp-hook.php on line 292Forum: Fixing WordPress
In reply to: CRON no longer works after updateFATAL ERROR
I have done further testing and removed every single plugin and still the same issue. This is a bug in wordpress. The site is jsut back to it original state and still this issue. It occurred with the new update. And the worse part it takes the site down.
[12-Apr-2022 16:15:52 UTC] PHP Warning: Undefined array key "args" in /home/public_html/wp-cron.php on line 124 [12-Apr-2022 16:15:52 UTC] PHP Warning: Undefined array key "args" in /home/public_html/wp-cron.php on line 127 [12-Apr-2022 16:15:52 UTC] PHP Warning: Undefined array key "args" in /home/public_html/wp-cron.php on line 138 [12-Apr-2022 16:15:52 UTC] PHP Fatal error: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /home/public_html/wp-includes/class-wp-hook.php:292 Stack trace: #0 /home/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', NULL) #1 /home/public_html/wp-includes/plugin.php(522): WP_Hook->do_action(NULL) #2 /home/public_html/wp-cron.php(138): do_action_ref_array('wp_privacy_dele...', NULL) #3 {main} thrown in /home/public_html/wp-includes/class-wp-hook.php on line 292`
- This reply was modified 4 years ago by walkinverse.
Forum: Fixing WordPress
In reply to: Ufter update Fatal Memory errorsI did all that The only thing that worked was to increase to 512MB which seems odd. I also disabled all plugins. It is the core wordpress it seems. It only happened after the update, not before.