Home › Forums › Calendar Products › Events Calendar PRO › Fatal Error
- This topic has 9 replies, 4 voices, and was last updated 9 years, 8 months ago by
Shannon.
-
AuthorPosts
-
August 17, 2016 at 9:22 am #1152613
Shannon
ParticipantI am using 3 Clicks and I just renewed and updated my Calendar Pro and I’m getting the Fatal Error also:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 64 bytes) in /home/content/p3pnexwpnas09_data02/38/2714938/html/wp-includes/wp-db.php on line 1780
I can’t even see my calendar and it was working fine 2 days ago. I thought it was because I didn’t renew but it’s apparently for another reason. I contacted my Hosting first and have sent you his suggestion and questions for you as I don’t have knowledge of php memory.
August 17, 2016 at 10:48 pm #1152966Geoff B.
MemberGood evening Shannon and welcome to the Events Calendar forum!
Thank you for reaching out to us.
We are sorry to hear about the fatal error message you are receiving. This is completely unintended!
I would love to help you with this topic.As a first troubleshooting step, could you please provide us with your complete system information in a private reply using the instructions found in the following link?
https://theeventscalendar.com/knowledgebase/sharing-sys-info/
If indeed the issue is caused by the updated, the good news is that it’s totally possible to downgrade: https://theeventscalendar.com/knowledgebase/downgrading-plugin-past-version/
With that in mind, could you tell me what your curent memory limit is for WordPress ?
Usually found in your wp-config.php file.Furthermore, does the issue persist if you temporarily deactivate the Events Calendar Pro ?
Best regards,
Geoff B.
August 17, 2016 at 11:19 pm #1152981Shannon
ParticipantThis reply is private.
August 17, 2016 at 11:21 pm #1152982Shannon
ParticipantMy hosting company upped my max to 128MB
August 17, 2016 at 11:28 pm #1152988Shannon
ParticipantThis reply is private.
August 18, 2016 at 3:03 pm #1153393Geoff B.
MemberGood evening Shannon,
Thank you for writing back and for sharing your system information.
First of all, I’m mostly glad that you managed to get your site working again.
To your point, it seems like there is something with the latest update that is creating some kind of conflict with your install.
The good news is that the updates themselves have been thoroughly tested, which means we should be able to get them to work for you to.I would like to offer to investigate this with you.
Could you please send me a copy of your WordPress theme / child theme in a .zip file link (via Dropbox or Google Drive) so that I can run some tests on my end ?
Furthermore, do you by any chance have a staging / test website as well ?
You are also right about the matching versions. It is better to use them whenever possible.
The correct match is currently the Events Calendar 4.2.5 and the Events Calendar 4.2.4The reason why there is a difference in subversion numbers is because the Events Calendar received one more maintenance release than Pro at this point.
Hang in there as we figure this one out!
Best regards,
Geoff B.
August 18, 2016 at 4:50 pm #1153450Shannon
ParticipantThis reply is private.
August 19, 2016 at 10:26 pm #1153958Geoff B.
MemberGood evening Shannon,
Thank your for the files.
Provided that you have a staging site and assuming it is a fairly similar copy of the live site, the fastest solution would be to go through our complete testing for conflicts procedure and let us know what you find out: https://theeventscalendar.com/knowledgebase/testing-for-conflicts/
Have a good weekend,
Geoff B.
September 10, 2016 at 9:35 am #1162438Support Droid
KeymasterHey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.
Thanks so much!
The Events Calendar Support Team -
AuthorPosts
- The topic ‘Fatal Error’ is closed to new replies.
