I have perhaps a stupid question: “Why are you making this so complicated?”
For this I would like to outline another way to create and maintain an event calendar in Kirby.
Some time ago I have developed a Kirby’s website (http://www.sav-barchfeld.de/) with a calendar of events (http://www.sav-barchfeld.de/kalender). There I have chosen in my view an easier way with the need to use the panel by the editors, which is here the default for all pages. But this could certainly be replaced by appropriate input page.
In my understanding, the main difference is something else:
I have created a content type “event” together with the associated blueprint, that contains all the fields, that are required for the representation of an event. In the blueprint of the calendar I have enabled the page type event as a possible child of the calendar.
I had to add the representation of all events, that “visible” children of the events are, in the template of the calendar.
The editor now has the ability in the panel to create a new event, then to fill in the fields and to upload photos or other files as needed or, as usual, to turn any event “visible” or “invisible” or update or change specific individual fields from existing events, like:
(screenshot of an event in the panel / here in English language / !click two times in this picture to grow it here!)
The uploaded files will have to be taken either into rendering in the template, being assigned in the panel possibly by some fields provided or be inserted in a textarea as an image or similar. But that is normal building a Kirby website.
In the above-mentioned website, we have been decided, if at all, to integrate pictures on the field Text of the event (using kirbytext).
Note: My way to store this data is commonly known as the relational model of data (https://en.wikipedia.org/wiki/Relational_database).
Hint: If you want you can protect the events from being viewed at an own webpage.
[last edited: 2015-05-22 16:05 / German time]