sunkast

I agree as well. Sick and tired of updating this plugin, only to have to re-configure it every time because of new “features” and what not. In my case, switching to the classic version DOES NOT disable the skyscraper. Sure you could hide it using CSS. But the code is still there, making a web site take longer to load. That’s unacceptable.

Anyone looking for the last version that does not have the skyscraper, it’s version 4.1.5

I had this same issue. EM is a really one of the best events plugins out there. And no offense to Marcus, and those that have contributed to the development. But the update process between major versions hasn’t been very good. I’ve been using EM since version 2. And with each major release, I’ve had issues with events going missing.

From my experience, it doesn’t appear that you can upgrade to a major release without being on the very latest previous version first. Meaning that the only upgrade path from v4 to 5 is if you are already on 4.305. I found this to be the same going from v3 to 4.

So in this case, I had to manually update first to v4.305 since I was not running the the newest version of 4. Then manually install the first 5.0 beta. This worked for me, and I was able to automatically update to 5.04 after that without losing my events.

Thanks to jolaedana for pointing out using 4.305 first.

It was rather frustrating figuring out this process, and having it happen yet again during an update from an old version, to the newest. I really wish the developers would work to improve the upgrade process between major releases.

Figured out my issue. The theme was using a custom function called is_child to add certain HTML. But since the new pages were grandchildren, the necessary HTML wasn’t be added because is_child only looks at direct children, not grandchildren.

I found this post: https://www.ads-software.com/support/topic/check-if-current-page-is-child-or-grandchild-of-a-page?replies=7#post-1787093

It solved my issue.

Wouldn’t ya know it. Finally found out how to do this. The documentation for the plugin is poor. Doesn’t explain anything about showing the event end date. I finally did see at the very bottom of the change log for the plugin documentation on a short code that does just what I want. I couldn’t find this information any where.

Added an end date option always on for multi-day events. Added a new placeholder format to deal with the end date. You can now wrap dates in #{} or #@{} . The values inside will have a format of date(). For example #{Y-m-d} #@_{ \u\n\t\i\l Y-m-d} will show as “2009-03-23 until 2009-03-28” (only for end dates with no recurrence) or just “2009-03-23” for normal events.