Menu
close
Often problems that occur with Timely's Calendar come from conflicts with other Themes or Plugins. Use these steps to determine if this is the case.
First please check to make sure you have the latest versions of:
If you have identified a plugin conflict, please let us know in the forums which plugin is causing the conflict and what the error is. Unfortunately there is usually no quick fix for plugin conflicts, however we try to iron out these conflicts in future releases if possible.
If you are seeing 2 calendars on your booking page, it's probably because you are using more than one method to display the calendar. Go through the following methods and pick one of the methods:
There are multiple ways to display your calendar.
To clear your calendar cache, navigate to your WordPress dashboard > Events > Settings > Advanced > Advanced Settings.
Uncheck this item:
Use advanced JS cache.
Then click on the Save Settings button.
If you receive a "500 server" error when you attempt to download your calendar's ICS file, there are the possible reaons and solutions:
Solution 1:
I found that the Slider WD Plug-In conflicted with the option to download an ics file from your timely calendar. Disabling this plugin solved the problem.
Solution 2:
It seems we were having this issue with PHP version 7.1 (7.0 seems to work).
Our developer commented out the following lines and that seems to have eliminated the error message and all events synced successfully:
plugins/all-in-one-event-calendar/lib/iCal/iCalcreator-2.20/iCalcreator.class.php” and the lines are 8003-8006
if( $startdatets <= $wdatets ) { // only output within period
$result[$wdatets] = TRUE;
// echo "recur ".date('Y-m-d H:i:s',$wdatets)."<br>\n";//test
}
In your calendar dashboard under Events > Import Feeds > Import Feeds tab >
You click on the Refresh button, but the feed never gives you a confirmation message that the sync/refresh operation completed.
Most likely, the reason could be that your host is reaching it's PHP memory limit -- and then the feed hangs.
I suggest increasing the memory limit, and try the feed refresh again -- it should finish, then produce either a confirmation or an error message -- this is how you know it finishes.
There are 4 ways to increase your PHP memory limit:
Add this to your wp-config file:
define('WP_MEMORY_LIMIT', '256M');or
Edit your PHP.ini file (requires access to your server files). If you have access to your PHP.ini file, change the line in PHP.ini
If your line shows 64M, try 256M:
memory_limit = 256MEdit your . htaccess file. If you don’t have access to PHP.ini try adding this to an . htaccess file:
php_value memory_limit 256MContact your Web Hosting Support
Ask your web host to increase the upload_max_filesize value for you to 256M
On some server configurations, Google's search robot will attempt to crawl every possible variant of the calendar. This can lead to overloaded servers and slow sites.
To limit the number of crawling queries made by Google or another search engine you need to modify the robots.txt file of your site.
You will need FTP access to your site, as there is no other way to edit that file. Also - you need to know the address of the page where your calendar is - usually it is https://your-domain.com/calendar but may vary depending on your settings.
Next - open FTP and navigate to the root folder of your site (that’s the same folder where wp-config.php file is placed). There you will see robots.txt file (if it is not there - create one with the content below). Open it and make sure it contains this content:
User-agent: * Disallow: /wp-admin/ Disallow: /wp-includes/
There may be more content but you can safely ignore it. If these lines are not present - add them manually. Under these three lines add the following content:
Disallow: /calendar/action~posterboard/ Disallow: /calendar/action~agenda/ Disallow: /calendar/action~oneday/ Disallow: /calendar/action~month/ Disallow: /calendar/action~week/ Disallow: /calendar/action~stream/
Save the file. This should prevent Google from indexing virtual pages. These pages make it easier for your users to navigate, but does not make sense to be crawled by search engines. And it will not prevent Google from visiting your calendar in general and gathering information about your events.
If you have issues implementing this fix, please contact your host for assistance.
If you are using a version of the plugin older than 1.11 Pro or 1.10 Standard, please note that you must use a colon instead of a tilde:
Disallow: /calendar/action:posterboard/ Disallow: /calendar/action:agenda/ Disallow: /calendar/action:oneday/ Disallow: /calendar/action:month/ Disallow: /calendar/action:week/ Disallow: /calendar/action:stream/
You must also modify the "calendar/" part. It must also reflect the actual installation path of our calendar.
I.e. if you have configured your calendar to appear under a page, where the slug is "my-events-list", then you must change "calendar/" to "my-events-list/". Even more, if you use a hierarchical page location, for example "community/events" then "calendar/" in the robots.txt must be changed to "community/events/".
you also need to patch your plugin file. In file class-ai1ec-href-helper.php found in wp-content/plugins/all-in-one-event-calendar/lib/routing, replace lines 11 to 22 with:
private $used_paramaters = array( 'action', 'page_offset', 'month_offset', 'oneday_offset', 'week_offset', 'time_limit', 'exact_date', 'cat_ids', 'auth_ids', 'post_ids', 'tag_ids', );
For most desktop PC browsers, you can clear your browser cache by pressing [CTRL] + [Shift] + [Delete], then follow the on-screen instructions to clear your cache.
For Mac, you can clear your browser cache by pressing [Command] + [Shift] + [Delete], then follow the on-screen instructions to clear your cache.
Browser-specific Instructions to Clear Cache:
Chrome
chrome://settings/clearBrowserData
From the "Obliterate the following items from:" drop-down menu, you can choose the period of time for which you want to clear cached information. To clear your entire cache, select the beginning of time.
Firefox
Alt to make it visible.Microsoft Edge
Internet Explorer 9 and Higher
Alt to make it visible.Opera
Safari 8
Command-Q to exit the browser completely.Safari 7 and Below
Command-Q to exit the browser completely.In a recent update we added some performance improvements to our addons -- which involves running some components of the addon features on our servers, for which your calendar will need to be logged in to access.
If you find that an addon has been deactivated, please be sure your calendar is logged into the Timely Network under:
Events > Settings > Viewing Events tab
This action will register your website URL with our API, allowing any addons to recognize your calendar.
Note: Both, your add-on, and your core calendar, should be in the same account for your addons to work.
In your Month View of the Calendar, when you attempt to navigate to the Next or Previous month, you receive a 404 or 200 Error message.
Here are some steps that may solve this problem for you, please go through each one until the issue is resolved:
- Make sure that your Calendar page is set to the right page in the Settings > Viewing Events tab (no need to use shortcode on a page set as the default in the plugin settings)
- Try turning on/off “Strict compatibility content filtering” in Events -> Settings –> Viewing Events.
- Try turning on/off “Use frontend rendering” in Events -> Settings –> Advanced
- Try resetting permalink settings to Plain and then back to your custom style
- This error is most likely a result of a plugin or theme conflict (usually caused by a caching or security plugin).. Please try a different theme temporarily such as Twenty Seventeen, or, disable all plugins and then check if the problem recurrs -- then re-enable each one until you find which one caused the problem.
If you get this error when you try to view your calendar in your browser:
It may be that there is some corruption in the installation. Here are the instructions to re-install the plugin while saving your events:
- Perform a complete back up of your database before proceeding further
- Delete the file uninstall.php from the plugin directory that is currently on the server (found under /wp-content/plugins/all-in-one-event-calendar). Deleting this file ensures that when you uninstall the current version of the plugin, your event data and calendar settings will be preserved when you delete the plugin (don’t skip this step – it’s important!)
- Deactivate the All-in-One Event Calendar using your WordPress Dashboard.
- Delete the All-in-One Event Calendar using your WordPress Dashboard.
- Database -> wp_options, click option_name to sort and delete everything with ai1ec_, this will delete plugin settings but events will remain in the database.
- Now install the latest version.
If the 500 Server Error appears when you try to download your calendar's ICS file:
Solution 1:
If you have the 3rd party plugin called "Slider WD" installed, it is known to cause this error. Simply disable or delete it.
Solution 2:
Some customers reported the error while using PHP version 7.1 (but 7.0 seems to work).
Edit the file:
plugins/all-in-one-event-calendar/lib/iCal/iCalcreator-2.20/iCalcreator.class.php
and comment out the followig lines (8003-8006):
if( $startdatets <= $wdatets ) { // only output within period
$result[$wdatets] = TRUE;
// echo "recur ".date('Y-m-d H:i:s',$wdatets)."<br>\n";//test
}
If you have duplicate events from a feed, this could be a sign that you have imported the same ICS feed twice. Please review the full list of Calendar Feeds to see if there are any duplicates.
1. Click "Delete" next to the feed to remove it from your system.
2. Select "Delete the events" when you are prompted. This will remove those events from your Calendar. If you do not delete the existing events, they will remain in the Calendar, even though the feed has been deleted.
- a feed that has events which duplicate those in your Calendar
- a feed that has duplicate events within it
In either case, review the feeds. Search for duplicate event titles within feeds or check if the calendar you are importing contains events you have already posted ,or are the same as events imported from another feed.
When creating or editing an event, you receive this error message:
"The link you followed has expired"
The solution:
Please be sure your calendar is logged into the Timely Network under Events > Settings. If you are already logged in on that page, please log out, then log back in -- then try creating or editing an event again.