You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a similar thought some weeks in the past, wanted to disable the rendering of that block for past events and than realised … that there might be reasons to have this in place also for past events. So I stopped there.
Now it would be interesting to know, what you suggest. Should the block just be removed (or better: not rendered on the front end) for all past events? Should this be selectable? Is this kind of differentiation maybe interesting for other blocks, too?
Hi @carstingaxion ,
I looked at the use case scenario for keeping the Add to Calendar on past events.
This is one of the things I found on ChatGPT:
_Users may want to associate notes, documents, or reminders with past events, like a meeting or conference. By adding the event to the calendar, they can append relevant information or materials to help recall specific details when needed.
Adding past events can help ensure that there are no gaps in their calendar, especially when reviewing activities over the year or for tax and legal purposes._
Describe the bug
Here's a feedback I got from a QA friend who tested a past event.
https://jam.dev/c/742551f4-f73c-4ce8-8dd0-d10cb5c7fd6e
Steps to Reproduce
Screenshots, screen recording, code snippet
Environment information
MacBoook, Chrome, Firefox
WordPress information
Latest version.
Code of Conduct
The text was updated successfully, but these errors were encountered: