Thank you, Jashan! Thank you GR8FL for asking for the step-by-step!
I also was getting sdk’s Warning and Fatal error messages. I had tried commenting out Line 160 per another thread’s solution to these messages, but that made matters worse. I was doubtful that deleting Line 160 would accomplish anything.
What does worse mean? After commenting out Line 160, the page loading time increased from 1 minute 25 seconds to 4 minutes 10 seconds. No matter what I clicked on in the dashboard, I got Apache server crash messages instead of Warning and Fatal Error messages.
Before commenting out Line 160, my site’s pages, including the Calendar page, hadn’t been affected by the Warning and Fatal Error messages. After commenting out, all site pages gave a version of 404 Page Not Found.
I was ready to throw my laptop out the window and and have nothing to do with time.ly ever again.
Problem was, I really liked the calendar features.
I was leery of deleting Line 160, but figured if I could speed up the page loading time, I’d be less frustrated. I’d try the “using FTP, rename the all-in-one-calendar folder (or maybe the php file, I forget which) and then go to the dashboard and click on this plugin to reset it” suggestion mentioned in another thread on fixing these Warnings and Fatal Error messages.
So I followed Jashan’s steps. The ‘AI1EC_DEBUG’ line is almost at the bottom of the constants.php file. I set it to false.
The Apache crashing and Warnings and Fatal Error messages stopped instantly! My site pages returned! My page loadings dropped to 5 seconds!
All is good with the world!
