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
It was just pointed out in Zulip that in most cases, this probably doesn't make much sense at Content Type level. As each event might have it's own date, presumably the open and close dates should either be relative to the event date or specific to each node.
But, the help text show how to set a fixed (default) open and close date.
While there may be use cases for this, it seems to me that they would be uncommon and at a minimum, the help text should reflect the more common use cases and say something like - "This is usually set at the node level for specific events."
Ideally, one could make these dates relative to the event date. But, as the event date is not even part of the registration entity, I can see how that might be difficult.
The text was updated successfully, but these errors were encountered:
It was just pointed out in Zulip that in most cases, this probably doesn't make much sense at Content Type level. As each event might have it's own date, presumably the open and close dates should either be relative to the event date or specific to each node.
But, the help text show how to set a fixed (default) open and close date.
While there may be use cases for this, it seems to me that they would be uncommon and at a minimum, the help text should reflect the more common use cases and say something like - "This is usually set at the node level for specific events."
Ideally, one could make these dates relative to the event date. But, as the event date is not even part of the registration entity, I can see how that might be difficult.
The text was updated successfully, but these errors were encountered: