Hi, need ideas to solve following task.
I have an event (training course) with multiple dates (e.g.: 5 Jan 08, 7 Feb 08, 3 Mar 08, an so on).
Want to have only a single document for this event because of a non-varying description for the training day. But I need a solution to handle the dates for this event.
That means:
- an input solution at the event document (in manager mode) for all dates a year
- automatic output of the current date (the next in the near future) at the start page
Any ideas? Thanks.
Thanks, but I think a database-table editor solution would be too confusing for my client (the author). The solution can be an event doc for every training event with detailed description. For each doc I set multiple date TVs for the max amount of dates. The author can fill these TVs with all dates needed to publish. A snippet will collect all TVs and puts a lists with dates at the event page.
The start page should have a snippet that also counts this TVs and sets the next training date following the current date as a single output (Next training on ...). I’ll try this next.
-
MODX Staff
- 10,725 Posts
I’ve done basically what ganeshXL is proposing several times using a custom calendar application I built with xPDO, and I just add links to a hidden add/edit form directly to the front-end pages. When the manager users login to the back-end and then browse the front-end, they have direct access to managing the events from the event views themselves. It works quite well for me and my clients.
I personally find editing things as documents that are ultimately more than just a web view (i.e. represent some kind of reusable source data) is problematic to maintain when combined with any significant quantities, and makes it unnecessarily difficult to present alternate views of, or maintain that data, in some cases.