What's new in 2.2
-
2.2 was released this morning.
Summary
- It fixes a bug where single event maps didn’t respect any especially tailored coordinates (if set for the venue in question)
- It adds new capabilities to the [event_embed] shortcode – you can now apply “AND” conditions
- Shortcode-level caching has also been added to [event_embed]
What does “AND” condition support mean?
My wording could definitely be clumsy, but in essence if you do this:
[event_embed categories="one, two"]Then it will retrieve upcoming events that have been categorized in “one”, or “two” or both “one” and “two”.
Now, if you only want events that have been categorized with “one” and “two” (and you wish to ignore events that only have one of those categories applied), you can do:
[event_embed categories="one + two"]How to enable caching
It’s as easy as this:
[event_embed cache="auto"]Once the shortcode has produced its HTML it will store it for 2hrs, saving on unnecessary database queries. If you want the cache to persist for a longer or shorter period just supply the time in seconds:
[event_embed cache="86400"](In the above example we’re telling it to cache things for 24hrs before refreshing.)
You can, if you like, apply different time limits to different uses of the shortcode.
Bugs?
Hopefully this release quashes more bugs than it causes, but if not please just create a new thread and I’ll be happy to help as soon as I can.
- The topic ‘What's new in 2.2’ is closed to new replies.
