HTML Content Before/After Event Still Not Working w/ 6.7.1

  • Resolved First Timothy Lutheran Church

    (@firsttimothylcms)


    1 month ago

    Hello, I tested the updated plugin version 6.7.1 and the issue is still occurring where HTML content to be displayed before and/or after the calendar grid is not being saved. I read through the change log, but I’m not familiar with all of the coding terminology. I understand this bug was reported during 6.7.0 – was a fix for this issue bypassed in the newly released version?

    What can we do to keep our HTML content intact before and after the calendar grid until it’s fixed, aside from not updating the plugin on our live site? Our webpage actively uses both content areas as do other users given the comments posted on a previous thread. Any advice you have would be most helpful. Thank you.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • wort

    (@wort)

    I tried adding the filters in the functions.php file of our theme as described for a work around, but they had no effect on the page at all. At least they didn’t throw errors. So I took the filters out again.

    So, yeah, this needs resolution. Perhaps I should open a ticket on the site since I am a pro account.

    Thread Starter First Timothy Lutheran Church

    (@firsttimothylcms)

    Hello, that would be great if you can open a ticket for support and help direct more attention to the issue. I really appreciate your help and I’m sure other users will too. Thanks!

    wort

    (@wort)

    heh. I did and got the same canned response. Even though I specifically mentioned that the functions.php hack wasn’t working as advertised.

    Plugin Support sammysamp

    (@sammysamp)

    Hi there!

    We are certainly aware of this issue and rest assured that we are working on it.
    Although we do not have a fix date right now, I can say that the fix is ??in the testing phase to be released very soon. We appreciate your patience and understanding in advance.

    Thread Starter First Timothy Lutheran Church

    (@firsttimothylcms)

    Thank you for the update Sammy! Looking forward to its release.

    Plugin Support Darian

    (@d0153)

    Hi @firsttimothylcms

    In the meantime, I’ve included your specific use case in our internal ticket [TEC-5283] to communicate it to our team.

    We prioritize bugs by taking into consideration the number of users impacted as well as how the bug impacts one’s ability to run an event/sell tickets. I don’t have a specific timeline as to when this issue will be resolved, but trust that our team is aware. Our team communicates updates and bug fixes in our newsletter and via our changelog.

    I’m happy to help if any other questions are coming up around this topic, otherwise I’ll go ahead and close this ticket.

    Thanks again for reporting this issue and for using The Events Calendar! Have a great day.

    —

    Internal Bug Ticket Reference: TEC-5283

    Thread Starter First Timothy Lutheran Church

    (@firsttimothylcms)

    Thank you Darian!

    Plugin Support sammysamp

    (@sammysamp)

    Hey there,

    We’re back with some good news!

    In our latest release, we have resolved the issue where Add HTML before event content and Add HTML after event content fields under Events > Settings > Display > Additional Content tab strip out HTML tags

    Please update the plugins to their latest versions to apply that fix to your site.
    As always, we suggest testing updates on a staging site first and having a recent backup, but it should all be smooth sailing.

    See: https://theeventscalendar.com/knowledgebase/creating-and-using-a-wordpress-staging-site/

    If you have further questions/concerns, please feel free to reach out.

    Thread Starter First Timothy Lutheran Church

    (@firsttimothylcms)

    Thank you for the update Sammy! We’ll create a staging site and test it out. Thanks again for your help and have a great day!

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.