- getMenu() treats hidden/time/fe_group as enable fields but NOT
nav_hide - the treeColumns doc comment claimed otherwise, and the
news detail page ("article") stayed in the new spotlight rail after
the editor hid it in menus. All three getMenu() calls (spotlight nav,
pagetree columns and their items) now pass 'AND nav_hide = 0';
verified live (6 rail items)
- all four tx_evomegamenujson_* tables get
security.ignorePageTypeRestriction: they are inline children of the
menu plugin and live on whatever page the plugin sits on - creating
a new entry on the standard page failed with "table is not allowed"
- new vitec:attach-page-media --root=<slug> (dry-run by default):
attaches the numbered placeholder pages/<pid>-08.png (slot 08 = page
media / menu tile, the number doubles as the image wish list) as page
media to every child page without one; existing media is never
touched. Run for /support (8 pages) so the planned Support menu entry
renders as two 4-tile rows via the pagetree layout's column images
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- customer wish (via Olli, 2026-10-27): a more visual main menu in the
style of rossvideo.com - image cards instead of plain link lists; for
Insights a left-rail submenu whose hover swaps a visual area showing
the latest news and the next events
- new entry layout "spotlight" in evo_megamenu_json, built strictly on
the catalog pattern so the extension stays project-neutral: `nav` is
a flat rail from the linked page's live children (abstract as teaser,
first page media as 640px-webp image from stage 2 - the hover swap
material), `spotlight` is emitted verbatim from the new
BuildSpotlightEvent (null without a listener); curated columns are
ignored like on pagetree
- new vitec listener ProvideInsightsSpotlight supplies the cards: the
three latest news (storage pid 11, type 0 - the Solr convention;
link /news/article/<path_segment> per the NewsDetail route enhancer;
fal_media as processed 640px webp) and the next two events
(hideonwebsite = 0, upcoming by eventstart/eventend; link = eventurl
or the events page)
- pagetree columns can now carry an image (stage 2+, first page media
of the column's page): attach images in the page properties and the
markets/solutions panels turn into image cards without further code
- TCA select and label extended; README brought up to date (the
pagetree layout had never been documented) with the spotlight JSON
contract, reference mirror synced; frontend briefing updated
- activation is editorial: switch the Insights menu entry to the
spotlight layout and link it to the Insights page
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
MenuBuilder::image() returned getPublicUrl() of the ORIGINAL upload, so
the Success Stories teaser cards (and item/featured images) carried
multi-MB files into every page payload. All menu images now go through
the ImageService (maxWidth 640, webp - the search-tile convention);
width/height report the processed size, and the original URL remains
the fallback when processing fails so the menu never loses an image.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- evo_megamenu_json: new entry layout "pagetree" - the panel columns
mirror the live subtree of the page the entry links to (one child per
column, grandchildren as items, getMenu() restrictions apply), so the
menu can never age against the page structure again. The stale
9-market panel after the markets realign was the trigger. Curated
columns are ignored on this layout; teasers and the featured slot
stay editorial. Same columns shape in the payload - front ends need
no change beyond knowing the new layout string
- new vitec:normalize-slugs --root=<slug> [--style=plain|and]:
recursively realigns every slug below a root to
<parent-slug>/<slugified-title>, cascading, with a sibling-collision
warning; EXT:redirects covers the old URLs. TYPO3's slug generator
keeps slashes from page titles (third hit: rtcc-/-rtic), this sweeps
a whole tree. Run on /solutions: four fixes, including the
long-standing passenger page and solution page 467. The misspelled
"engagament" slug stays deliberately - it follows the page title and
is fixed in the coordinated typo task
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- evo_megamenu_json stays project-neutral: new panel layout "catalog";
for such entries the MenuBuilder dispatches the new PSR-14 event
BuildCatalogEvent and emits whatever a listener sets as `catalog`
(null without a listener). The entry's teaser cards serve as the
featured tiles; the teaser inline field now also shows for "catalog",
and the entry form reloads when the layout changes. README section
"Layout catalog"
- VITEC listener ProvideProductCatalog fills it, modelled on the Ross
Video products menu: main categories below the "Product" root, their
subcategories as groups, products with a plain-text one-line teaser;
same visibility rules as the product list, Product Finder links
(/products?cat=&subcat=), empty categories and groups left out, three
queries for the whole catalog
- Product type-ahead GET /_json/?type=7385&q= (USER_INT page type,
ProductMenuSearchJsonRenderer): Solr restricted to products, last term
completed as a prefix, up to six product cards plus their titles as
autocomplete suggestions; endpoint announced in catalog.search
- Spec v1.23 (clause 7.16: product type-ahead)
- new project-neutral extension evo_megamenu_json (Evomedien): a Megamenu
plugin holding entries, columns, items, teaser cards and a featured slot
as nested records; presentation settings travel with the payload so the
front end reads behaviour instead of hard-coding it; published as
page.10.fields.megaMenu, driven by the site settings megamenu.contentUid
and megamenu.storagePid
- vitec:seed-megamenu fills one element from the live structure: 5 entries,
26 columns, 95 items, 4 story cards; items without a page yet are flagged
pending so the front end falls back to the column link
- vitec:debug-sets prints the resolved site set order
- read-only diagnostics: check_megamenu_schema.php, check_typoscript_templates.php
- docs: schema updates run via extension:setup (database:updateschema no
longer exists in v14), and a JSON Accept header activates headless-mixed,
which strips every set-added page field
orascheandClaude Fable 5