Juan Gray

Thanks, this is what we assumed. Although we came close to getting it to work with some hooks, but in the end, we put the secondary theme in a different installation and linked it to the main site.

Some diagnostic messages in place of missing divs and blank pages might be good, but as a WP dev, server admin and sometimes plugin-developer, I know of course the origins of the errors are not so easy.

The issue resolved with the next WordPress update.

Yes I discovered the problem was the Eventify plugin’s abject failure to properly register events. The calendar could not possibly find them. I destroyed the Eventify plugin and shredded the disk space it used to occupy.

To get events to show up on EC3 you must add them as posts through the EC3 custom fields way down at the bottom of the post. This isn’t mentioned in the documentation or anywhere else on the internet.

I managed to force WP into making the post date the same as the event date, but then WordPress then refused to list it as published. I installed a plugin to force WordPress to publish future posts, which it still refused to do. I forced it past this point, and then unfathomably the calendar STILL listed the post as when it was posted.

As far as I can tell, even DIRECTLY manipulating the dates, deleting database tables, the calendar still pulls the stupid date from somewhere else. The pointless, useless, POST date of an event.

Rather than smash my laptop, I decided to uninstall and discard Event Calendar 3 after 5 days of wasted development.