Event model as wordpress plugin for ecovillage Sieben Linden homepage (siebenlinden.org).
Its functionality comes to life with the Sieben Linden Hueman Child Theme (http://github.com/ecovillage/ev7l-hueman-child-theme).
Events can be pushed and updated with ruby scripts included in wp_event.
By Freundeskreis Sieben Linden e.V. (Germany). Released under the GPLv3+ (or any later version) as included in the LICENSE file.
Use create-wp-plugin-archive.sh to create an uploadable plugin archive for Wordpress.
Until a propagation via wordpress' plugin repository is done, try using the github updater plugin.
The plugin ships with a Widget to show events in a list, some query functions to access events in a loop and registers two query vars that can come handy when creating calendar like views (in a theme).
To use the calendar you need a page called calendar.
An examplary theme can be found at the 7L hueman child theme .
Events (ev7l-event), Event Categories (ev7l-event-category) and Referees (ev7l-referee) are modeled as Custom Post Types (CPT) with special Custom Fields (metadata).
Following relationships exist:
- Event <-> EventCategory (many-to-many)
- Event <-> Referee (many-to-many)
Spelled out:
- an Event can have multiple EventCategorys
- an EventCategory can have multiple Events
- an Event can have multiple Referees (with a
qualificationfor that event) - a Referee can have multiple Events
Relationships are modeled with Custom Fields (post metadata), storing the Post ID in a one-way fashion (it sits at the Event). The custom fields are named event_category_id and referee_id.
Common to all three CPTs is an UUID field to uniquely identify an entity (but, as mentioned above, the Post ID is used for cross-references!).
Custom fields:
| Field | Multiple? | Semantic |
|---|---|---|
| UUID | false | Unique identifier |
| event_category_id | true | post id of an evl7-event-category |
| referee_id | true | post id of an evl7-referee |
| referee_<id>_qualification | false | post id of an evl7-referee |
| fromdate | false | starting date/time (as unix timestamp) |
| todate | false | ending date/time (as unix timestamp) |
| registration_needed | false | whether a registration is needed (and form shall be shown) |
| arrival | false | arrival time/info |
| departure | false | departure time/info |
| current_infos | false | current important information |
| other_infos | false | further information |
| costs_participation | false | price of participation |
| costs_catering | false | information / price of catering |
| info_housing | false | information / price of housing |
| participants_please_bring | false | what participants should bring |
| participants_prerequisites | false | what participants should fulfil |
| cancel_conditions | false | conditions to accept for registration |
The referee_<id>_qualification field deserves separate explanation. Here, <id> is to be replaced with the Post-ID of a given referee.
That means, if your event has 'referee_id' => 412 and 'referee_id' => 821 there should be respective referee_412_qualification and referee_821_qualification fields describing the referees qualification specific for the given event.
Custom fields:
| Field | Multiple? | Semantic |
|---|---|---|
| UUID | false | Unique identifier |
Custom fields:
| Field | Multiple? | Semantic |
|---|---|---|
| UUID | false | Unique identifier |
| firstname | false | referees first name |
| lastname | false | referees last name |
| homepage | false | url of homepage of referee |
In query, some functions are defined to ease theme development (for an example check the 7L hueman child theme).
To release a new zip file to be used as uploadable wordpress plugin call create-wp-plugin-archive.sh. The script will create a zip file which contains the last (git) tag name in its name.
To release a new version follow these steps:
- modify ev7l-events/ev7l-events.php to to use the correct version number.
- git commit -m "0.2.0"
- e.g.
git tag -a "0.2.0" -m "0.2.0" git push && git push --tags./create-wp-plugin-archive.sh
PHP Class-Names cannot start with numerics (0..9).
post__in means 'everything' if passed the result from a multiple meta_query that does not return anything.
Awesome many-to-many example
http://wordpress.stackexchange.com/questions/51386/many-to-many-relationship-between-two-custom-post-types
Either use magic or remember var_dump and print_r.
Mixing PHP and HTML can get you into trouble - nobody seems to have a solution regarding indentation and mental health. I hope I will get proven wrong.
PHP folk loves tabs although not consistently.
Derived from https://github.com/devinsays/team-post-type .