Release of 1.10.2 lite – Write here if you think it's not compatible with 3.6

WP 3.6
1.10.1 – broke my blog total.
1.10.2 – homepage is ok, but on posts i get fatal error:
Fatal error: Uncaught exception 'Ai1ec_File_Not_Found' with message 'The specified file 'event.min.js' doesn't exist.' in /home/xsrv/public_html/wp-content/plugins/all-in-one-event-calendar/app/helper/class-ai1ec-view-helper.php:124 Stack trace: #0 /home/xsrv/public_html/wp-content/plugins/all-in-one-event-calendar/app/controller/class-ai1ec-events-controller.php(200): Ai1ec_View_Helper->theme_enqueue_script('ai1ec-event', 'event.min.js', Array) #1 [internal function]: Ai1ec_Events_Controller->init('') #2 /home/xsrv/public_html/wp-includes/plugin.php(406): call_user_func_array(Array, Array) #3 /home/xsrv/public_html/wp-settings.php(308): do_action('init') #4 /home/xsrv/public_html/wp-config.php(96): require_once('/home/xsrv/...') #5 /home/xsrv/public_html/wp-load.php(29): require_once('/home/xsrv/...') #6 /home/xsrv/public_html/wp-blog-header.php(12): require_once('/home/xsrv/...') #7 /home/xsrv/public_html/index.php(17): require('/home/xsrv/...') #8 {main} thrown in /home/xsrv/public_html/wp-content/plugins/all-in-one-event-calendar/app/helper/class-ai1ec-view-helper.php on line 124

How about people posting here if 1.10.2 lite IS compatible with 3.6.

Given Timely’s weak track record in releasing updates, it would be reassuring to know if people have used 1.10.2 and it has worked OK.

And it solves the problems.

Hi @marek probably you need to update the theme files https://support.time.ly/what-are-core-calendar-files-and-why-do-they-need-updating/

Let me know if this works

Hi @rogal for me “working” means that you can install version 1.10 standards without issues.

I’m going to consider it not working, because I’m caught in an upgrade loop.

According to the WordPress updater, 1.10-standard is a lower version than 1.10.2. My site continually has an upgrade message on it, either from WordPress or from your plugin.

I’m only seeing this issue on a Multisite install. My single-site WP installs are correctly detecting that there is no upgrade available.

Otherwise, I’m not seeing any issues.

Hi, I tried to install the latest version (1.10.2) on my test website running WP 3.6 with the default theme (twenty thirteen) but I got into an install loop when it tries to install the themes (unable to create the directory themes-ai1ec).
I tried to create the directory manually (even though it should be able to create it by itself) and tried again, but the error was still there. Even tried various combinations of owner and permissions, but nothing worked.
I had to rename the plugin directory as suggested and then remove the plugin.
The test server is an ubuntu 12.04 virtual machine up-to-date.

@cpilko i will look into issues with multisite. Thanks for pointing that out

@dalsenoa wordpress does some strick checks on filesystem. Did you copy over the folder themes-ai1ec from the plugin root to the wp-content folder?

Actually no. I simply tried to manually create the folder in wp-content (directly on the server with a terminal, same user and permission as usual) as suggested by the plugin and restart (try again) the themes install (the plugin uses the default ftp service, that usually works fine for themes, plugins and uploads, so it should be ok; file permission is set accordingly to codex suggestions).
I’ll try to manually copy the directory to see if it works.

Ok, I did copy manually the directory form the plugin folder to wp-content via Filezilla and now it works. It said that the plugin was no longer supported and updated to standard calendar. The plugin is now working and I can see my google calendar events in the the calendar page.
Thank you (I guess you should give this advice instead of aksing to manually create the folder).
PS The calendar page is actually a protected page (only registered users can see it; will it be a problem with your plugin?).

@cpilko i tried to replicate that but couldn’t. How do you set up your network?

1.10 standard appears to have problems with Yoast (again) on the latest WP version.