cefiar

Only other things I can suggest:

If you’re using one of the “Manual Adjust” timezones, try using a similar named timezone that is close to your location and see if that helps.

Otherwise, if you have mysql experience, look at the ai1ec_events table, specifically the timezone_name field.

The following query can be quite useful for seeing the number of events that are matched to which timezones:

select timezone_name,count(*) from ai1ec_events group by timezone_name;

Very weird. Appears as though you may need someone from Time.ly to invesigate.

Basically it appears as though the twig template engine is not actually working, so it’s not producing any output files.

PS: I don’t work for Time.ly

…../all-in-one-event-calendar/cache/ needs to be writable by the webserver user. The directory will end up containing .php files (the twig template engine writes out .php, which is the eventual code that the calendar runs).

You can disable the cache, but it really slows down the plugin, and I don’t know if it will solve all the write access issues you’ve had.

I don’t see why it would want write access to wp-admin/post.php though.

PS: I don’t work for Time.ly.

Clearing the cache should be all you need to do to get it to pick up the template.

If you upgraded from 1.x, you may find that old themes are somehow confusing the issue. If you have …../wp-content/themes-ai1ec/ dirs present from an old 1.x setup, you may want to rename that themes-ai1ec out of the way. While they might not be processed unless you have the Legacy Themes add-on installed, probably best to avoid the issue. Ai1ec V2 only uses …../wp-content/themes-ai1ec/ for child themes now.

Note: cache/twig needs to be writable by the webserver user. You can check if the dir is writable by going to Dashboard -> Events -> Settings, and go into the Advanced -> Cache Report tab.

No you’re right I missed a piece of the path.

You need to clear the ai1ec cache to get it to work.

Easiest way is to rename the twig directory in …../all-in-one-event-calendar/cache/ and then refresh the page. Rename it to something like oldtwig.

If your permissions are ok, it will re-create that dir (and all the subdirs under it) then you can delete the renamed dir (eg: delete oldtwig).

If your permissions aren’t correct, ai1ec will not be able to create the dir (probably producing an error and disabling the plugin, so you will want to rename oldtwig back to twig and then re-enable the plugin so that people can at least use your site.

Note: If your cache permissions are wrong, you need fix them so the webserver user can write to them. It should be fine though as otherwise you’d have other errors. That said, I always recommend the rename/test/delete method, as it gives you a fallback in case there is an issue.

Definitely, but as mentioned by Lukasp, it’s a quick work-around, not an end-to-end fix.

I’m assuming the fix will be in the next update, but that depends just how complex the underlying issue is.

Facc: If you get a fatal error, try turning on debug in Ai1ec.

Note: Debug will slow things down, and display a lot of messages that would be useless for a working install, so remember to turn it off afterwards.

To enable Ai1ec’s debug:

Edit …../all-in-one-event-calendar/app/config/constants.php

Near the end of the file, you will see this line:

define( 'AI1EC_DEBUG', false );

Change it to:

define( 'AI1EC_DEBUG', true );

Try again and report any errors if you don’t understand what they are and/or can’t fix the issues you get.

If you want the event time to show after the title you ned to fix a bug (that should be fixed in 2.0.7).

Edit …../all-in-one-event-calendar/public/vortex/twig/month.twig – starting at line 56:

Change:

{% if event.is_allday %}
         <span class="ai1ec-event-time">
                    {{ event.get_runtime( 'short_start_time' ) }}
         </span>
{% endif %}

To:

{% if not event.is_allday %}
         <span class="ai1ec-event-time">
                    {{ event.get_runtime( 'short_start_time' ) }}
         </span>
{% endif %}

If you want it BEFORE the title I recommend creating a child theme. Do the change above (to fix the bug in the default theme), create your child them, then in the child theme edit month.twig and move the new section of code above the title code (which is immediately above it) – starting line 53:

<span class="ai1ec-event-title">
    {{ event.get_runtime( 'filtered_title' ) | raw }}
</span>