Version 5.0.3.1 breaks v2

Okay, update:
Everything should work if you are using the updated designs.
This happens when using the legacy design.
Checking…

Hi @aguseo,

I can’t speak for everyone of course, but in my case I’m using:

• the “Activate Block Editor for Events” option
• a non-default Events template
• not “Use updated calendar designs” (though I haven’t tested this bug with this option enabled either)

I have tried this with a custom theme built on Understrap and also Twentytwenty in my staging environment. For your other two questions, I’m not using any plugins to affect TEC or the editor.

Thanks

• This reply was modified 4 years, 6 months ago by adbowp.

As for @paulagaces’s post, I believe he was saying that this is the only code that is rendered on the front end in this case – which I can also confirm. The Event datetime, featuredimage, and venue aren’t populated and are just comments. In 5.0.2.1 (or 5.1.0 with @docdunning’s fix) those comments aren’t there and are replaced by actual content.

Thanks for all the info here and in the other thread. I have collected all, filed a bugticket and flagged it. I’ll keep y’all posted here of the progress.

Again, apologies for this and thanks for your patience!

Andras

Hi @adbowp @paulagaces @docdunning

Quick update: a fix has been developed and is being tested. If all goes well this should be resolved in the next TEC release.

Andras
Ref: TEC-3456

Hi @aguseo – that’s great to hear. Thanks for keeping us updated.

Hi,

We just wanted to let you know that a fix has been released for this issue!

Please try updating and let us know if you are experiencing any further issues. As always, we recommend running updates on your?staging site?before doing so on your live site, just to be on the safe side.

Thanks again for your patience while we worked on getting this fixed!

Hi, I use WordPress 5.4.1 with theme Primer version 1.8.9 and The Events Calendar version 5.1.2

I also use Molongui Authorship version 4.0.8., a plugin to display an author box in posts.

I always use Classic Editor to create events, they look far better than Gutemberg Blocks Editor. And default Page template.

I don’t know when (probably after an update) the author box started to display in events.

I deactivate all plugins and switch to an unaltered WordPress theme (Twenty Sixteen). Then I enable Gutenberg Blocks Editor to create and publish an event, and later made some testing. Results:

• With Gutenberg Blocks Editor disabled and default Event template selected, the author box is displayed.
• With Gutenberg Blocks Editor enabled and default Event template selected, the author box has gone, but also the featured image and the boxes with event details at the end of the page.
• With Gutenberg Blocks Editor disabled and default Page template selected, the author box is displayed again.
• With Gutenberg Blocks Editor enabled and default Page template selected, two author boxes are displayed.

Also found that old events (created with Classic Editor) have issues:

• With Gutenberg Blocks Editor enabled or disabled and default Event or Page template selected, the author box is displayed.

Hope this helps.

I’ll try to downgrade and see if that fix the issue.

I’m still having issues enabling Events > Settings > Display tab > Use updated calendar designs. When I do this my calendar disappears and the events are just showing a list of comments from users. I’m using “Default Page Template”. It only works with “Default Events Template”. Unfortunately “Default Events Template” eliminates my sidebars, which I need, and it makes my background transparent, which makes everything look chaotic.

I posted about this in this thread: https://www.ads-software.com/support/topic/use-updated-calendar-designs-not-working/ but was told to continue the conversation here to keep things focused.

Hi @jaimemarchwinski – I can confirm the latest update is working as expected for me, thank you ??

Should I mark as resolved or leave open for the others with issues?

Hi @adbowp

Thanks for letting me know, glad to hear that the latest update resolved your issue!

I’ll go ahead and mark this thread as resolved, but if others are still experiencing this issue, please open up a new ticket.

Cheers,
Jaime