Commenting out that line resolves the plugins issue.
For those that don’t upgrade to 1.10.11 then you might miss out on a key for the version 2 release which adds views and Facebook integration. So, you might get stuck with less features than you have now.
My advice is to install from timely and upgrade to 1.10.11.
@billrodgers2013
How will installing from Time.ly and upgrading to 1.10.11 fix this bug?
Please elaborate.
I upgraded 4 sites, both WP3.71 and WP3.81 to Time.ly 1.10.11
I upgraded Manually because in the past I experienced tremendous troubles updating.
All of them gave this error on activation:
The plugin generated 3483 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.
After deactivation and again activation of the plugin all 4 sites gave no errors and appear to work well.
Yes, to be sure after reading Time.ly site about problems people were experiencing I commented out line 160 in this new all-in-one-event-calendar.php , this line which reads
unset( $plugins->active[ array_search( $basename, $plugins->active ) ] );
Hello,
To fix this, please FTP your site, and go to Wp-content -> plugins -> All in one calendar -> all-in-one-calendar.php and delete the following code at line 128
unset( $plugins->active[ array_search( $basename, $plugins->active ) ] );
This should fix the issue.
Thanks
This crashed my pages as well. Yet another issue with this plugin. Ugh…
@jashan – this did fix the issue. I’m just glad I know how to FTP and modify the code.
Hello Everyone
Would anyone like to put together step by step instructions on how to fix this and post the solution on this thread.
Thanks in advance
+1 for step-by-step instructions.
If you are experiencing the issue with “Fatal error: Cannot use object of type stdClass as array” … “on line 160”
Here’s how I fixed it:
1. FTP to your site or use cPanel/hosting file manager to access your site’s files.
2. Edit file “all-in-one-event-calendar.php” in the plugin root directory
3. Look at link 160 and remove or comment out:
unset( $plugins->plugins->{$basename} );
4. Reupload file to replace existing one
5. Refresh admin panel; you should not see anymore error.
I hope this helps.
I just update to 1.10.11 and now my logged in users are just fine, but people not logged in are throwing errors
“Fatal error: Uncaught exception ‘Ai1ec_Cache_Not_Set_Exception’ with message ‘Failed to write ‘ai1ec-response/month/standard/2014-03/’ to void cache’ …blah blah blah” seems to be the core of the error.
But it’s totally useless (for me) if people not logged in cannot see the calendar.
Any ideas on how to resolve this?
i see this plugin i hogging resources on my server. it’s sitting on “Top” with 28.2% to 70% of CPU constantly. turn off the plugin, no more CPU hog. really disappointing since i love this plugin. this issue was both before and after upgrading to recent version.
Hello @scarletcarnival,
PLease FTP your site, and go to wp-content -> plugins -> All in one calendar ->contants.php file
Set the AI1EC_CACHE to false in file constant.php at line 503.
This will help.
Thanks
Hello @helloari,
Performance and load times are a huge focus as we work to build v2.0
We’re hoping this will be released soon (if testing goes well).
In most of the cases, the reason of this high memory usage is GOOGLE CRAWLING. Please read our article here on how to limit Google crawling: support.time.ly/limiting-excessive-google-crawls/
Please clear your cache periodically from Wp-content -> plugins-> All in one calendar -> Cache
Try installing a cache plugin such as WP Total Cache. It will help reduce calls to the server. If possible, install APC or some form of Opcode Caching.
Your patience is greatly appreciated.
Take care
Thank you.
That definitely helped allow the calendar to be seen by those who are not logged in users.
However, the events are still shown as 31 December 1969.
@jashan – one of the issues I saw with Google creating so many requests was the fact that the calendar auto-generated links into the past on every event view, which means bots were spidering pages going back into the 80s. This gives bots an incredibly exaggerated sense of a website’s size. While your suggestion of blocking those pages works with Googlebot, it does nothing to prevent bots that do not obey robots.txt from creating a huge load on the site. A much more sensible approach would be to give or allow the setting of a point in which links to the past are no longer created. There is no reason to allow a web based events calendar to auto-generate content going back 40 years like that. I am even able to click back to dates in the 60s, since it uses a negative time stamp after you hit 1970.
-Michael
