All-in-One Event Calendar Update 1.10.11

Thank you. I did on 11 March 2014. No response so far.

Hello,
Can you please send another email. It might have been missed by mistake due to high number of emails that we are getting.

Take Care

@jashan is that because of all the bugs in your code?

Commenting out line

unset( $plugins->plugins->{$basename} );

did not work for me… and, it doesn’t make any sense because that was part of a conditional statement:

if ( $is_json ) { // object-access
		unset( $plugins->plugins->{$basename} );
	} else { // array-access
		unset( $plugins->plugins[$basename] );
	}

did NOT work for me. Granted, I’m using Dreamweaver CS6- but for me, line 160 was :

unset( $plugins->active[ array_search( $basename, $plugins->active ) ] );

I don’t get it, but, my business model tells me i can’t use this. I can’t do anything to my plugins.

OK- update- I found if I disabled the plugin (through FTP, just by adding an underscore to the all-in-one-event-calendar folder name), refreshed the plugin dashboard (this will automatically deactivate the calendar plugin), added whatever plugin I needed- or adjustments I needed, then took the underscore back out of the all-in-one-event-calendar folder name… reactivated it within the dashboard… and everything works!

Yayyyy! No panic!

correction on my last post,

everything appeared OK after manual update and disabling line 160

but not!!

just a whole bunch of errors on the page where it should have been.
Fatal error: Uncaught exception ‘Ai1ec_Cache_Not_Set_Exception’
Will make this a new support question

Ok so my 2nd comment has also been deleted.

Does anyone know if there is a way to complain about the forum moderators?

LordLiverpool I’ve undeleted your comments. They were deleted as

@jashan is that because of all the bugs in your code?

Isn’t really conducive to a reasonable conversation.

If you want to work with Jashan and the other time.ly developers then please do.

i had the 1969 problem – what I did is downgrade to version 1.10.9 and restore the database. The plugin changed the table – preparing the update to version 2.

the plugin didn’t do the table migration smoothly.

my bigger issue is massive CPU load and i have not found a solution for that. i had to move sites between servers and it’s really a problem.

I still cannot get this plugin working. 1.10.11 crashed my site, and ever since I got my site up again, whenever I try to activate this plugin I get a fatal error (it gives me nothing more specific than that). Here is what I have tried so far:

1. Commented out line 160. Still got fatal error when activating.

2. Deleted plugin and reinstalled latest version from Timely site, and commented out line 160. Still got fatal error when activating.

3. I tried ChadAustin’s suggestion a few posts up, but that didn’t work either.

4. Deleted plugin and installed 1.10.5 from Add New Plugin in Dashboard. Calendar did not function. Tried updating this to 1.10.11. Still got fatal error when activating.

Any ideas what else I can do?

Hello @luke314pl,

What are the exact FATAL error you are getting? Please paste them here.

Thanks

It just says: Plugin could not be activated because it triggered a fatal error.

I’ve had a similar experience with this upgrade, with a site going offline, Google crawl errors, plugin.php problems, and a very stressed and naturally upset client.

I am a fan of All-In-One but would like to ask Timely how we can remove the upgrade notification from the WP dashboard and if there would be a benefit from revoking the 1.10.11 update altogether.

I appreciate a lot of work has gone in to the development and the version that has been the source of the issues is a free plugin, but it is ‘costing’ a lot of time for web designers fixing various issues and doing harm to our client relations.

This is genuinely not wanting to start a witch hunt, only asking if you can be more proactive in detering what is a known issue for other users of your otherwise very wonderful plugin.

1.10.11 is there mainly so you can get an email for a free key to Views and Facebook. Given 2.0 is close I’d say it is unreasonable to expect an update to 1.10.11 or for it to be pulled.You are basically getting something for nothing given the new common core and paid for add-ons.

The line 160 bug is *very* easily fixed.The 1969 issue is much less prevalent.

If a **free** plugin is costing a lot of time for some web developers I’d suggest they upgrade clients to a paid version and take advantage of support.

bill, I acknowledged (and have considerable appreciation of) how much work has gone in to this free plugin. No issues, but if the line 160 fix is a quick solution, don’t understand why this is not flagged-up outside of forums like this in a place where it is visible to casual WP users. If an individual (or client) undertakes their own plugin updates, they may not be so comfortable in opening a file in a text editor (heaven forbid MS Word!) and commenting out content.

Convincing a client to move to a premium version of a plugin when it has just caused them a minor meltdown would be a hard sell. At a later stage, or for new clients, I agree. It would also be a good way to put money back in the developer’s pockets.

I’m just asking if there is a way to disable the update notification.