| 开发者 | ralf_st |
|---|---|
| 更新时间 | 2026年7月13日 03:28 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[annovisio].
The fixed standard configuration uses exactly one source:
[annovisio] to a page or post.The standard configuration uses either one public iCalendar/ICS feed or one connected Calendly account.
Yes. AnnoVisio can read public iCalendar/ICS feed URLs from Google Calendar, Microsoft Outlook, Apple Calendar, and other compatible calendar systems.
No. The plugin renders the shortcode page itself as the archive and does not create a custom post type or standalone event pages.
Parsed and normalized calendar data is stored in a WordPress transient. The default cache duration is 8 hours. Administrators can change the duration in hours or refresh the feed manually. The configured calendar name and color are applied when the overview is rendered, so changing these display settings does not require a new feed fetch.
The shortcode renders a visible frontend error. The plugin does not silently fall back to stale, empty, guessed, or partial data.
Yes. The plugin expands recurring events in the WordPress-local recurrence window from January 1 of the current year through 12 months after the current WordPress-local date. RDATE and EXDATE are supported. Unsupported complex RRULE parts are rejected with a visible parser error rather than guessed.
No. iCalendar/ICS feeds are fetched server-side and no external frontend assets are loaded for iCalendar output.
No. Updating the shortcode refreshes its iCalendar data, reads the existing Calendly tables, and rebuilds the display cache. Calendly synchronization is controlled separately on the Calendly page.
Yes. AnnoVisio continues to use the existing Calendly tables and synchronization logic, including its handling of past events and occurrences.
Yes. Existing Calendly multi-day handling and iCalendar date ranges are displayed in the yearly calendar.
[annovisio].