설명
This plugin is an extension of Modern Tribe’s – The Events Calendar, as such it will not function without that plugin on your WordPress installation.
This plugin and myself have no affiliation with Modern Tribe and do not represent the company or its products.
The plugin was designed to create dynamic iCal feeds from your Calendar’s events.
Those feeds can then be used to plug into other copies of The Events Calendar, on other websites. Specifically, by using Modern Tribe’s FREE event importing feature for “iCalendar”. Simply paste the URL into the appropriate box and wala!
Thus, the creation of distributed event calendaring.
If you have any problems, please email me directly: amanda at dalziel dot net dot au
“I don’t always test my code, but when I do… I do it in production.”
스크린샷
The admin panel – exporting the feeds.
The admin panel – setting the options.
설치
This section describes how to install the plugin and get it working.
e.g.
Installing the plugin is easy. Just follow these steps:
- From the dashboard of your site, navigate to Plugins –> Add New.
- Select the Upload option and hit “Choose File.”
- When the popup appears select the gimme-calendar-feeds.zip file from wherever you downloaded it to.
- Follow the on-screen instructions and wait as the upload completes.
- When it’s finished, activate the plugin via the prompt. A message will show confirming activation was successful.
- Make sure you have Modern Tribe’s – The Event Calendar also installed.
- Go to “Events” -> “iCal Feeds” in the dashboard
- Enter a unique name for your new iCal feed (no spaces, only alphanumeric characters, the underscore and dash are allowed).
- Make sure you have some categories set up for your events in Modern Tribe’s – The Event Calendar.
- Choose which categories you want your iCal feed to display.
- Click “Add new feed”
- The new feed will appear on the right (or below, if you have a tiny screen). Either copy the link displayed to wherever you wish to share it or change the options to apply it automagically to you calendar.
Requirements
- PHP 5.2.4 or greater (recommended: PHP 5.4 or greater)
- WordPress 3.9 or above
- jQuery 1.11.x
- Modern Tribe’s – The Event Calendar
FAQ
- Do I need Modern Tribe’s – The Event Calendar?
-
Yes.
- Do you work for Modern Tribe?
-
No.
- When are you releasing version 2.0?
-
Now.
- When are you releasing version 3.0?
-
Um…
- What new features will version 3.0 have?
-
I have no idea. Why don’t you tell me?
후기
이 플러그인에 대한 평가가 없습니다.
기여자 & 개발자
변경이력
1.0
Plugin released.
1.0.1
- Plugin name changed
- Fixed bug when adding a feed, straight after deleting a feed
1.0.2
- Temporarily fixed a bug involving the plugin checking for The Events Calendar but because WordPress doesn’t always load plugins in the same order, this was a tricky bug to squash. Threaded bugs usually are.
1.0.3
- Removed references to deprecated TribeEvents class
2.0.1
- Split plugin into tabs (export, options)
- Restructured the code to allow for future calendar systems
- Added feature to add a custom permalink to any feed
- Added geo-coordinates for non-Pro versions of The Events Calendar – requires your own Google API key
- Added feature to export featured images of events as an ical attachment
- Added a link to the calendar feed to the bottom of Events pages
- Restricted permissions
- Only loaded js and css on actual page that needs them
- Restricted ajax access
- Added cleanup functions on deactivation
- Added update functions on activation, I hope they work.
2.0.2
- The update now adds necessary roles
2.0.3
- Changed the donate link to my account, rather than Modern Tribe
- Updated info in readme about Modern Tribe’s FREE Event Aggregator
- Added images for the banner and icon in WordPress.org plugin search
2.0.4
- Changed the banner image
2.0.5
- Added monumental timezone support because although it passed one validator, it failed another.
2.0.6
- Stoopid mother frickin’ colon was missing from the organizer CN which borked EVERYTHING up. Stoopid colon. Grr.
2.0.7
- I was issuing a security decree against every ajax call that was not mine. I think all it did was clog up the error_log. But that’s enough to annoy me.