Plugin and templates rework - #21
Open
minapok wants to merge 9 commits into
Open
Conversation
added 7 commits
September 1, 2026 11:31
The existing plugins only render events by date, so editors could not build a curated selection – e.g. a teaser of three conferences on a landing page while all other events stay in the automatic listing. The new "selectedList" plugin lets editors pick events through a FlexForm record selector. EventRepository::findByUids() ignores the storage page, because an explicit selection has to work across sysfolder boundaries, and it restores the order the editor chose – the query itself returns the records sorted by eventstart.
All three plugins output a list of events, so their titles were hard to tell apart in the "New Page Content" wizard – and two of them had no description at all. Each one now names its output and says in one sentence how it differs from its siblings. The plugins also move from the generic "plugins" group into their own "Events" group, and the label keys follow the CType signature. plugin.list and plugin.upcoming are gone – projects overriding them via locallangXMLOverride have to follow up.
The url field existed in columns and in the model but was missing from showitem, so editors could never fill it and the frontend link stayed empty. Add it to a new "link" palette together with an optional link_title, which gives the link a readable label instead of the bare URL. The partial falls back to the URL when no title is set.
The event form was a flat list of fields in an arbitrary order, with categories sitting between title and the dates palette. Fields are now grouped in the order an event is described: dates, title, description, then location and audience in a new "details" palette, then the link. Language and categories move into their own tabs so the general tab stays focused on editorial content.
Normalize the TCA array formatting: drop the aligned "=>" padding, which had drifted apart between the ctrl and columns sections, and add the missing trailing comma after 'required'. Widen the url input to 50 characters. Restructure both language files: group trans-units by the table or plugin they belong to, sort the event units alphabetically, and drop the redundant <target> elements from the English source file, which only duplicated <source>. This also removes a stray character behind the description target that had slipped in. No labels are added, removed or reworded.
`pages` and `recursive` sat under the appearance tab, where nobody looks for the record storage, and a stray leading comma produced an empty form item. Move both fields into the plugin tab and drop the comma. Switch the tab labels to the core.form.tabs shorthand, which is what the core itself and the event TCA in this extension already use.
The event list was a stack of divs wrapped in Bootstrap-style grid markup (section/container/row/col) that only ever fitted one specific project. List, SelectedList and Upcoming had drifted apart while rendering the same thing. All three now share the same minimal structure: a container div carrying the content element uid, and a ul whose items are the event partial. The plugin header is no longer rendered here, since fluid_styled_content already emits it through its default layout. In the partial, each row becomes an li and the dates are wrapped in time elements with a machine-readable datetime attribute. The visible date uses the SHORTDATE pattern, so it follows the request locale instead of a hardcoded format.
bmack
reviewed
Sep 1, 2026
bmack
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.