cossd

Hi Marventus,

Sorry I thought I already had – have done now – my bad!

Cheers!

Hi Dan,

First I used the automatic update in the WordPress Dashboard to upgrade from 1.5 to 1.6.3.

Once it was installed (which took about 30 seconds), I went into the AI1EC settings in the WordPress Dashboard, and in the top-right area of the screen was an advertisement for 1.6.3 Premium.

I clicked the ad. Unfortunately at this moment I can’t remember exactly how I installed it (I know, poor memory!). Either it auto-installed after I followed instructions, once I’d clicked the ad; or maybe I had to download the 1.6.3 Premium zip file, then manually install it.

(The zip file can be downloaded from https://www.thenl.ly).

To manually install a plugin, in your Dashboard to go Plugins > Add New > Upload. Choose the 1.6.3 Premium zip file, and click Install.

After it installs, you may need to click Activate.

Sorry I can’t be more specific – good luck, and please let me know if I can be of any more (vague) assistance!

Thanks! Yes, it solved it immediately. Thanks again for your help.

I’ll be sure to visit help.then.ly in future.

Hi yani.iliev,

Thanks for your suggestion, but no luck yet. Here’s the procedure I followed:

1. In the WordPress Dashboard, I went to Settings – Permalinks, and copied my existing custom permalink structure
2. I selected one of the other (preset) permalink structures and clicked ‘Save Changes’
3. I re-selected ‘Custom Structure’, pasted in my custom structure (which I’d copied in step 1), and clicked ‘Save Changes’ again

But it hasn’t worked. My custom structure is:

/%category%/%year%/%monthnum%/%day%/%postname%/

Sorry forgot to add, I’m using the following plugins:

– Akismet
– Contact Form 7
– Google Analytics for WordPress
– Google XML Sitemaps
– Really Simple CAPTCHA
– The OpenHook Customizations Manager
– WPtouch (currently disabled)

…and the Thesis theme.

My web host is running php 5 (I don’t have any other version details).

Cheers!

Thank you so much – version 1.6.3 has solved all problems. The upgrade from 1.5 to 1.6.3 went smoothly. I then upgraded to 1.6.3 Premium, which works perfectly as well.

A great update – cheers!

Thanks everyone for your input. Installing 1.6 via FTP or the WordPress dashboard resulted in the same error.

I used the same method as perfumewagon and KillerWhale to revert to 1.5, which is stable.

This morning I tried installing 1.6.1, and received the same errors as with 1.6:

Warning: Wrong parameter count for array_unique() in /var/www/vhosts/councilofsocialservices.org.nz/httpdocs/wp-content/plugins/all-in-one-event-calendar/all-in-one-event-calendar.php on line 271

Warning: Invalid argument supplied for foreach() in /var/www/vhosts/councilofsocialservices.org.nz/httpdocs/wp-content/plugins/all-in-one-event-calendar/all-in-one-event-calendar.php on line 274

Fatal error: Class ‘Ai1ec_Settings’ not found in /var/www/vhosts/councilofsocialservices.org.nz/httpdocs/wp-content/plugins/all-in-one-event-calendar/all-in-one-event-calendar.php on line 286

SO once again I used FTP to delete all files, then successfully reverted back to 1.5.

Shortly afterwards, I noticed that version 1.6.2 had been released. After installing 1.6.2, I received the following (similar) errors:

Warning: Wrong parameter count for array_unique() in /var/www/vhosts/councilofsocialservices.org.nz/httpdocs/wp-content/plugins/all-in-one-event-calendar/all-in-one-event-calendar.php on line 272

Warning: Invalid argument supplied for foreach() in /var/www/vhosts/councilofsocialservices.org.nz/httpdocs/wp-content/plugins/all-in-one-event-calendar/all-in-one-event-calendar.php on line 275

Fatal error: Class ‘Ai1ec_Settings’ not found in /var/www/vhosts/councilofsocialservices.org.nz/httpdocs/wp-content/plugins/all-in-one-event-calendar/all-in-one-event-calendar.php on line 287

So once again, I’ve used FTP to delete the files, and have reverted back to version 1.5 in the meantime.

We just logged into our host’s file manager, and could see that the element-selector.js file was showing a size of 0.00 KB (and its permissions etc did not match the other files in the js folder).

So, we deleted that file, re-downloaded the plugin, extracted the element-selector.js file, and uploaded it to the js folder on our server.

Fixed the problem.

shrmn – thanks so so much for steering us in the right direction. Much appreciated!

Many thanks for your help! We’re not familiar with javascript – can you please advise how to proceed from here?