scamrp1ckleballclub

Brad,

Yes, originally I was able to get to the Backup tab. But, it was a few months ago, so there has been lots of updates to the various plug-ins we use. I wanted to review the backups that have been occurring on a regular basis and delete the older ones.

The email that is sent does not identify the error. Here is the whole email that I received:

“Howdy!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Total Upkeep Premium.

First, visit your website (https://www.scamrpickleball.org/) and check for any visible issues. Next, visit the page where the error was caught (https://www.scamrpickleball.org/wp-admin/admin.php?page=boldgrid-backup) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

https://www.scamrpickleball.org/wp-login.php?action=enter_recovery_mode&rm_token=GfxyawVf0Uk4N7hGIeNDLU&rm_key=rjgk1i6pZTtF84Pu16NtNf

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.9.3
Current theme: Zita (version 1.5.4)
Current plugin: Total Upkeep Premium (version 1.5.9)
PHP version 7.4.15″

Unfortunately, when I logged into WordPress today, the error is back. Not sure what has changed in order for this to occur, but thought I would let you know to see if the host can fix it again.

Thanks, Gino

I logged into WordPress and the error no longer appears. The news is shown correctly in the Bold Grid box.

Thanks so much for getting this solved.

Gino

Jesse,

I’ve been working with DreamHost over the past hour to try and correct this error. They can’t seem to identify where it is being caused. Andrew C. was the support person I deal with. This is his last comment:

Andrew.C: see, so the thing with that error is that it can be caused for a number of scenarios actually, we checked cURL module is active, DNS settings are also correct, I mean it would’ve caused a major error if if was something on DNS but that’s not the case.

We don’t see unusual files or errors, apart from the one we found earlier from ModSecurity, but that one should be disabled so no rules should be blocked either

I’m hoping based on the information provided above by Andrew that this isn’t a problem that is affecting the website in general – just the news not being displayed when I log in. However, it would be nice if this error could be corrected.

Let me know if there is something that can be done.

Thanks, Gino

After receiving an email from the Webnus Help Desk, the issue seems to be that I am creating too many recurring event items. I was using the Calendar to build a pickleball schedule for a week and then making it recurring every week for the remainder of the year. This is what is causing the slowdown of loading the calendar.

After further consideration, I’ve decided not to use the calendar plugin to build the pickleball schedule, so I am closing this ticket now.

Please note that I sent the screen shots in a response email, since I am unsure of how to include them in this ticket. If you need the screen shots sent on the forum, please me know how to do this.

Please note that my Calendar page on the website only uses the monthly calendar shortcode: [MEC id=”212″].

Thanks

Jesse,

I inserted the CSS and it worked perfectly.

Thanks for providing the solution and the quick response to my question.

I’m marking this as resolved.

I didn’t realize that WP did not allow duplicate email addresses. I thought it was just usernames. So, I thought by setting the username to the email address, I was making sure that no duplicate emails were entered.

I guess there is no reason for me to hide the username field on registration, if no duplicate email addresses can be entered. Thanks for the information again.

Thanks for your response. It gives me a number of options to look at. I’m starting to rethink my original request. I currently have the username automatically being set to the email address that the member enters on the registration form. At first, I didn’t like this approach, in case the user changes their email address. However, I need to ensure that each email address is unique (since we are interfacing with MailChimp for emails) and this approach does work initially, since usernames can’t be duplicated. I can then install a plug-in that allows me to change the username manually for anyone that changes their email address later. This will hardly happen and is only a maintenance issue every few months. Plus, there are only 200 members, so not an onerous task.

Again, thanks for your input.