The three SSR widgets render dark VITEC tiles like the cockpit module: status with pulse, cache ring and last purge, statistics with the 24 h availability strip and number tiles, errors with hit rate ring and split bar. Shared markup in CockpitHtml, styles in dashboard-ssr.css loaded per widget.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Live band with 24 h availability strip, gauges for hit rate, response time, cache fill and client errors, traffic chart 24 h / 7 days from the health log counter deltas drawn with the core Chart.js of EXT:dashboard, warm progress ring with live polling, purge activity timeline, client error cards, link to the site settings. ssr-cockpit.js replaces ssr-warm-progress.js, whose deletion went into a9923e1.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mit dem selbstreferenzierenden Canonical (07f74e3) zaehlten
/insights/news?page=2 und ?category=... als eigene Seiten mit dem
Titel von Seite 1 (Seobility: 3 doppelte Titel, 2x Duplicate Content).
VitecMetaHandler haengt jetzt ' - Page N' bzw. die Kategorie an Titel
und Description.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Ticket 0096-FE (aehm): the module now uses the core Module layout (DocHeader with reload and shortcut, module-body spacing), a Status card as description list with one badge style, an Actions card with core buttons and icons, help texts below the buttons and TYPO3 modal confirmations (ssr-module.js) instead of window.confirm, and three protocol cards. Purge protocol rows show a one-line time, the trigger as badge plus user, paths as count + first two + disclosure, result and duration right-aligned, with 30/100/500 row switches. Status shows the last health sample with relative age and the cache limit (new optional SSR_CACHE_LIMIT_MB in var/vitec-ssr-purge.env, SsrPurgeService::getCacheLimitMb). ssr-warm-progress.js now also disables the Warm button with a spinner while a run is active. backend-ssr.css holds only layout glue with core CSS variables (dark mode safe). Verified in the backend: layout, modal, running progress bar, protocol tables.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
VitecMetaHandler: /insights/news?page=2 (und ?category=) bekommt einen
selbstreferenzierenden Canonical statt Seite 1 (0100-FE 5.1).
PageJsonLdRenderer: auf Produkt-, News- und Story-Detailseiten ersetzt
der Datensatz (Titel + URL) die Shell-Seite als letztes Breadcrumb-
Element (0108-FE F11). UsecaseListJsonRenderer: cardImage.crops aus den
Listen-Karten entfernt, ~20 kB pro Seite mit Testimonial-Band
(0102-FE 5). Migration fe_answers_fixes_20261111 (angewendet):
Platzhalter 'H1 Header' (/solutions) und 'Featured Product' (Startseite,
Lorem ipsum, CTA auf /product) versteckt; Karte 'Government' auf
/markets/government; Button in #699 'Explore our solutions'; Story CDC
h4 'Product Highlight' -> h3 (0104-FE 4.1).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Der erste Lauf (5bm) legte die neuen Why-VITEC-Baender auf 9 Uebersichts-
seiten als text_only an - das Frontend baut das Icon-Band nur aus icon_card.
Importer legt neue Band-Karten jetzt als icon_card (ohne Icon) an und stellt
vorhandene Band-Karten beim Re-Run um; 36 Karten repariert, Seiten gepurgt.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The Cache warming row of the VITEC SSR module now shows a Bootstrap progress bar with a running counter instead of asking for a reload. New ajax route vitec_ssr_health (SsrController::healthJson) returns the node /__health JSON; ssr-warm-progress.js polls it every 2 s while a warm run is active and every 15 s otherwise (pauses in background tabs) and also refreshes the Cache: N pages / M MB line. The health fetch moved into SsrController::fetchHealth, shared by indexAction and the ajax route; its error text is English now. Verified live in the backend: bar, counter and cache line advance during a run.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Migration crawl2_fixes_20261110 (angewendet): sechs Karten-Buttons
zeigten auf versteckte/geloeschte Produkt-URLs (ArtioSign/ArtioView ->
/products/aetria, Redirects folgen; X-View-Selbstlink entfernt;
Chassis-Karte auf das verbliebene Produkt). Drei weitere News trugen
noch den InfoComm-Importplatzhalter und doppelten echte Artikel
(JODDB, Bluefin, NAB 2026) -> geloescht + 301; EKOM-Artikel bekommt
seinen Text von der alten /en/news-Seite; byte-identische Datapath-
Kopie (#551) -> 301. Drei Tippfehler. Tote vitec.com-Links in 14
Datensaetzen auf interne Ziele (/markets, /insights/sustainability,
Story Northwestern, /product/fx4, 'vitec.com./' und ' '-Links).
SEO-Titel fuer sieben Hauptseiten, Descriptions fuer neun
Kategorieseiten mit < 60 Zeichen.
VitecMetaHandler: Titel-Kontext ueberspringt Ordner-/Shortcut-Ebenen
('End-Points | Products | VITEC' statt 'End-Points | VITEC'); kurze
Story-Titel bekommen '| Success Story'; Meta-Description auf 155
Zeichen gekappt, auch redaktionelle (Seobility: 527 'zu lang').
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
13 Pressemeldungen tragen denselben Text wie eine Success Story
(Seobility: doppelter Inhalt). Neues Feld am News-Datensatz (Tab
'VITEC SEO', Auswahl der Story); VitecMetaHandler ersetzt damit den
Canonical-Link durch /success-stories/<slug>. Die Meldung bleibt in der
Liste, Suchmaschinen werten die Story als Original. Migration
news_story_canonical_20261110 setzt die 13 Zuordnungen (angewendet).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Bisher gab es den Aufklapper nur bei Meldungen mit Stack. Jetzt hat jede
Zeile "details" mit Zeit, Release, voller URL, kompletter Meldung,
Stack (oder Hinweis "no stack transmitted"), vollem User-Agent und
anonymisierter IP, damit sich jeder Fehler bewerten laesst (Wunsch Harry).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Die Kategorieseiten tragen seo_title = '<Titel> | VITEC' (Import), was
die Kontext-Vorlage als gepflegten SEO-Titel las. Der Brand-Suffix wird
vor dem Vergleich abgestreift; die Vorlage baut den Titel aus Seitentitel
+ Elternseite neu auf, der Brand-Suffix folgt wie bisher.
Die Rootline ist root-first; der Helfer las bisher Index 1 (oberste
Ebene, 'Products') statt der direkten Elternseite ('AVoIP & KVM').
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Der Import hatte bei fast allen Seiten den Seitentitel 1:1 als seo_title
gespeichert, dadurch griff die Kontext-Vorlage fuer kurze Titel nie. Ein
seo_title, der dem Seitentitel entspricht, gilt jetzt als nicht gepflegt
('Aligo | AV over IP & KVM | VITEC'). Dazu die Meta-Description der
Solutions-Uebersicht (war bis heute der TCA-Platzhaltertext).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Crawl nach dem Footer-Fix: 1.094 Seiten (vorher 9). Backend-Anteil:
- Migration seo_report_fixes_20261110: Platzhalter-SEO-Titel auf /solutions
geleert; News mit verdoppeltem Titel/Slug und Slugs mit Slash bereinigt
(+Redirects); 8 Tippfehler; zweite Welle toter Alt-Links (datapath.co.uk-
Absolutlinks, utm-Varianten, /resource-center, /services, /contact-sales,
/aetria-use-cases, /video-wall-solutions ...) in 48 News ersetzt + 101
Redirects; Record-Shells /product, /news/article, /success-stories/story
leiten auf ihre Uebersichten; Meta-Description /datasheets; WordPress-
Reste in den 17 SEO-Artikeln entfernt; 53 News-Zeiger-Records (type=1
auf alte /en/news-Seiten, ohne eigenen Text) bekommen den Seiteninhalt
(Text + Bilder) in den Record und werden normale Artikel - die alten
Seiten leiten per 301 auf die Artikel.
- VitecMetaHandler: kurze Seitentitel ohne SEO-Titel erhalten ihren
Bereich als Kontext ('Aligo | AV over IP & KVM | VITEC').
- ProcessedFileReferenceToArray: Alt-Text-Fallback (Referenz-Titel, dann
Dateititel) fuer Content-Block-Bilder.
- UsecaseListJsonRenderer: Testimonial-Baender liefern nur noch Stories
mit Zitat, aktueller Markt zuerst, max. 12 (vorher alle 70 = 226 kB auf
jeder Markt-/Solution-Unterseite, identische Bloecke auf ~90 Seiten).
- NewsJsonRenderer: paginierte Listen-Payloads 15 Min. im hash-Cache
(USER_INT rendert sonst jede Variante neu; 50 langsame URLs im Report).
- robots.txt host-abhaengig: dev bekommt robots-dev.txt mit der dev-Sitemap
(Seobility fand '0 Sitemaps', weil die Sitemap-Zeile auf www zeigte).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Neue PSR-15-Middleware ClientErrorMiddleware: nimmt Browser-Fehler des
React-Frontends als JSON {url, message, stack, release, userAgent}
entgegen und antwortet 204 ohne Body. Schutz: 30 Meldungen pro Minute
und IP (Sliding Window ueber TYPO3-RateLimiter, 429 + Retry-After),
8-KB-Body-Limit (413, Content-Length und tatsaechliche Bytes), kein
JSON-Objekt oder leere message = 400, GET = 405. Keine Session, keine
Cookies; der /_json-Praefix funktioniert ebenfalls.
Speicherung in der neuen Tabelle tx_vitec_clienterrorlog mit
anonymisierter IP (IPv4 letztes Oktett 0, IPv6 /48). Sichtbar als
Tabelle "Client errors (last 24 h)" im Modul VITEC SSR (mit Stack als
Aufklapper) und als Zeile "Client errors reported (24 h / 7 d)" in der
Dashboard-Kachel VITEC: SSR statistics.
CLI vitec:client-error-cleanup [--days=30] loescht Eintraege aelter als
30 Tage (taeglich per Cron).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Die SEO-Artikel trugen (a) eine FAQ-Sektion als nackte <p>-Paare im
Bodytext und (b) ~150 Links auf die alte datapath.com-Struktur
(/datapath-products/..., alte /markets/...-Namen, /video-wall-solutions)
- alles 404 auf der neuen Seite.
- NewsJsonRenderer (Detail-Modus): extractFaqBand() schneidet die
'Frequently asked questions'-Sektion aus dem Bodytext und liefert sie
strukturiert als faq {heading, items[{question, answer(HTML)}]} fuers
Frontend-Accordion (fail-safe: unter 2 sauberen Paaren bleibt alles
unveraendert); collectMentionedProducts() liefert bis zu 6 Karten
(title, text, image, link) fuer im Text verlinkte Produkt- und
Kategorieseiten. Beide Felder additiv; Listen unveraendert.
- Migration fix_datapath_links_20261110: 148 News-Records auf die neuen
Ziele umgeschrieben (Mapping alte Datapath-IA -> /product/<slug> bzw.
/products/<slug>/Markets/Solutions, Ziele gegen DB verifiziert) und
113 sys_redirects 301 angelegt (alte Pfade mit und ohne Slash - greift
fuer externe Backlinks, sobald datapath.com hierher zeigt).
Live verifiziert: Beispielartikel liefert faq (8 Fragen, Antworten mit
funktionierenden Links), 4 Karten, Bodytext ohne FAQ-Absaetze und ohne
Datapath-Links; normale News unveraendert (faq null); Redirects 301 ok.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
17 SEO-Artikel tragen ein rohes FAQPage-JSON-Objekt in einem
abschliessenden Absatz ihres Bodytexts - das Frontend renderte es als
sichtbaren Text, Google sah es nie als strukturierte Daten.
Neue Klasse Seo\EmbeddedJsonLd trennt solche schema.org-Bloecke aus dem
RTE-HTML (fail-safe: was nicht sauber dekodiert, bleibt stehen):
- NewsJsonRenderer: Detail-bodytext und Listen-Exzerpt ohne die Bloecke
- PageJsonLdRenderer: die dekodierten Nodes wandern in den @graph der
Seite (FAQPage landet damit als <script type=application/ld+json> im
Head, den das Frontend bereits injiziert)
- VitecMetaHandler: Description-Fallback aus dem Bodytext ohne JSON-Muell
Verifiziert an 3 Artikeln: @graph mit NewsArticle + FAQPage (8-9 Fragen),
kein FAQPage-Rest im Textkoerper, kein sichtbarer JSON-Absatz im HTML.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Die Uebersichtsliste (news_newsliststicky/news_pi1 ohne limit und ohne
Auswahl, d.h. genau /insights/news) liefert jetzt pro Request nur die
Karten der angefragten Seite: ?page=<n>&category=<slug>, Antwort additiv
mit pagination {page,pages,itemsPerPage,total}, categories[] mit
Gesamt-Zaehlern und activeCategory. page klemmt auf die letzte Seite,
unbekannte category faellt auf alle zurueck, Sortierung serverseitig
datetime DESC, itemsPerPage aus settings.list.paginate (Default 12).
Caching: page/category stehen in cacheHash.excludedParameters, der
TYPO3-Seitencache unterscheidet die Varianten also nicht - das Element
konvertiert sich deshalb im paginierten Fall per
convertToUserIntObject() zu USER_INT (EXT:headless wrappt den
INT-Marker selbst); ETag/304 je Query-Variante verifiziert, der
SSR-Cache haelt eine Variante pro Pfad+Query.
Karten im paginierten Modus in schlanker Form (Felderliste aus
0070-FE); media[] traegt jetzt ueberall alternative (Alt-Text-Fallback
B5). Teaser-Listen mit limit und Selected-/Search-Listen unveraendert;
ohne pagination-Feld bleibt das Frontend beim bisherigen Verhalten.
JSON der Liste: 700 kB -> ~100 kB pro Seite.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Ticket 0068-FE: ProductFeatureJsonRenderer returned json_encode(null), which headless passes on as the STRING null (it only decodes object/array-looking strings) and crashed the front end. It now returns an empty string and the TypoScript field sets ifEmptyReturnNull = 1, giving a real JSON null. No other renderer used the pattern. Ticket 0066-FE: SsrPurgeService::warm() posts to the node /__warm endpoint (derived from SSR_PURGE_ENDPOINT, same secret), exposed as a Warm cache button with confirmation in the VITEC SSR module, a Cache warming progress row fed by /__health, and the CLI vitec:ssr-warm [paths]. Warm runs are deliberately not written to the purge log. Verified: two-path run 2/2 done, affected page delivers productfeature null.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The backend context menu appends .js itself when importing the callback module; with the extension already in the attribute the browser requested ssr-context-menu.js.js and the click died silently. Confirmed working in the backend after the fix.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
SsrPurgeItemProvider adds the item behind Clear cache for real pages (doktype < 199) whenever the purge endpoint is configured. The callback module posts the page uid to the new vitec_ssr_purge_page ajax route, which resolves the page path through the site router, purges it via SsrPurgeService (trigger contextmenu:username, logged as usual) and reports back as a toast notification.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Widgets, backend module template and flash messages now match the rest of the backend, which is English.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The group identifier comes from EXT:dashboard DashboardWidgetGroups.php; with an unknown group the widgets never appeared in the add-widget dialog.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Package 1: SsrPurgeService posts to the node /__purge (endpoint+secret in var/vitec-ssr-purge.env, outside git) and logs every attempt to tx_vitec_ssrpurgelog. DataHandler hooks queue per request and flush once: pages with nav-relevant field changes and all tx_news_/tx_vitec_ records purge everything, other page/content edits purge the hosting page path. Gated by the routing flag and the new Site Set switch vitec.ssr.autoPurge. Flipping the SSR switch ON purges everything once. CLI: vitec:ssr-purge, vitec:ssr-health (samples /__health into tx_vitec_ssrhealthlog, 14 days kept, scheduler-ready). Package 2: dashboard widgets vitecSsrStatus (live health, release, switch, last purge) and vitecSsrStats (purge counts, failures, uptime, response time). Package 3: backend module web_vitecssr with manual purge (paths or everything) and both protocols. Tested end to end against the running node (purge single/all 200, health sample logged).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Ticket 0054-FE section 5: (1) with the SSR flag on, /_frontend/assets/* is now proxied to the VPS release as well, deliberately without a file-exists guard so stale local SPA hashes cannot shadow the release; the proxy rules tag requests with env SSRPROXY and mod_headers adds X-Forwarded-Proto: https. (3) If-None-Match comparison in JsonCacheHeaders accepts the -gzip suffix that mod_deflate appends, so browser 304s work through compression. (4) X-TYPO3-Cache-Tags*/-Debug-Cache/-Cache-Lifetime/-Parsetime are stripped from responses (onsuccess and always tables - they leak record ids and overflowed the SSR node 16 KB header limit on news pages).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New JsonCacheHeaders middleware (outer, frontend stack): GET/HEAD 200 responses under /_json get a single Cache-Control: no-cache, Expires: 0 and a content md5 ETag; If-None-Match answers as empty 304. Logged-in visitors (fe_typo_user) keep TYPO3 headers. Expires: 0 is deliberate so mod_expires leaves the response alone. .htaccess: the global Header unset ETag now skips /_json (KEEP_ETAG env, carried across the mod_rewrite internal redirect as REDIRECT_KEEP_ETAG). Fulfils tickets 0011-FE point 3 and 0055-BE question 6; asset immutable headers were already live.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
All seo.* settings now carry real values (sources: vitec.com footer + privacy policy, KBIS for the legal name VITEC SA): canonical base, org name/legalName, address Chatillon, phone, sameAs LinkedIn/YouTube, logo at fileadmin/vitec-brand/vitec-logo.png (served 200, verified in the home jsonLd as absolute www.vitec.com URL). Email left empty - no public address exists. Removed the my.vitec.setting / my.seoRelevantSetting scaffold examples from the set definition and the my.example.setting value.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Site set Vitecset: new bool setting vitec.ssr.enabled (default off,
backend switch under Site Management > Settings > VITEC Settings)
- SsrFlagService derives var/vitec-ssr-on.flag from the setting;
SyncSsrFlag middleware (frontend + backend) re-syncs per request
because TYPO3 v14 fires no event on site settings save;
vitec:ssr-flag CLI command for status/--sync
- public/.htaccess: flag-gated block proxies page requests [P] to
https://vitec-ssr.evomedien.de (mod_proxy incl. https target verified
on this host 2026-11-09), same exclusions as the SPA fallback block;
completely inert while the flag file is absent
- Emergency off without TYPO3: delete var/vitec-ssr-on.flag
- Tested end to end: flag on -> pages proxied to VPS Caddy (502 while
the SSR node is not deployed yet), /_json untouched; flag off ->
SPA shell exactly as before
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The 2026-11-02 menu build created the 3 categories and 9 sub-categories
as sysfolders (labels); every level must be a clickable page.
- build-product-overviews: six sub-categories adopt the 2026-10 category
pages (Joe's workbooks; content, slug and SEO kept, sitemap name as
nav_title), the remaining folders become pages with generated content,
Capture & Graphics gets the main column of Graphics & Multi-Display and
Video Capture copied in. Pages move/convert by direct UPDATE (the
redirects slug hook would rewrite the flat child slugs); three 2026-10
pages leave the menus but stay reachable. Warns about a sys_redirect
on a target slug.
- ProvideProductCatalog: categories[].link and groups[].link (additive),
menu title = nav_title when set, only filled groups/categories count.
The menu search reads both levels as pages too.
- build-why-vitec-bands: band at the top of the main column; on pages
with an existing "Why VITEC?" section the context's icons go onto the
cards whose title matches the icon theme (16 icons on 4 pages).
- No browser cache headers on the page JSON: headless enables
sendCacheHeaders and TYPO3 14 caches pages for a year by default, so
every /_json/ response carried max-age=~31536000.
- Spec v1.32.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Megamenu entries with the catalog or spotlight layout get two editor
fields, "Data source folders" (source_pages) and "Data source
categories" (source_categories); the extension stores them, the site
package's listener reads them from the entry row.
- ProvideInsightsSpotlight reads its news from those folders (empty =
11 + 442; the newer posts live in 442, the query only read 11) and,
when set, only from those categories (Insights: Blog Post + Press
Release). Newest datetime first, three cards.
- Pages carrying the menu are tagged with the news and event tables, so
saving such a record refreshes the menu without a cache flush.
- VITEC field descriptions via a TCA override; spec v1.31, README.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- token-containment pass: theme words inside the card title
(ManagementFoundation -> "Aetria management foundation")
- last-pair rule: a complete set (#icons == #cards) with exactly one
icon and one card left over pairs them (FlexibleConnection,
EndToEndEncryption, HighPerformance, 4KSourcetoDisplays, AVoverIP)
- genuine mismatches (aligo-workstation, EZ-TV Platform, AvediaPlatform
Artio icons) still stay unmatched for the editors
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- new inline table tx_vitec_product_feature (title, cardtext, FAL icon)
+ `features` field on the product record; ProductShowJsonRenderer
emits product.features {heading, items[{title, text, icon}]} and null
while a product has no cards, so the front end keeps its
applications-HTML fallback
- new vitec:seed-product-features: seeds the cards from the
applications <p><strong> pairs and matches the staged agency icons by
normalised title (camelCase split, stop words, Levenshtein <= 3 typo
tolerance); products with existing cards are never touched
- new vitec:build-why-vitec-bands: "Why VITEC?" intro + icon_card band
on the 7 overview pages with a staged icon set (the contract's
"centered" variant does not exist - documented in ticket 0039-BE);
vision/visionav sub-group sets stay unassigned
- product-check page: sortable title column and an Open Product button
- new migration fix_colombia_quote.php: stray quote element #12037
removed, quote_role set (ticket 0038-FE)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The vitec/herosection content block has prefixFields - the real column
and sys_file_reference fieldname is vitec_hero_bgimage; the JSON merely
strips the prefix. The first apply wrote the 20 references with the bare
name, so they existed but never rendered (no herosection anywhere had an
image, so there was no working example to catch it against).
- BuildProductOverviews: attach/backfill/skip-check now use
vitec_hero_bgimage
- new migration fix_overview_hero_refs.php: renames the existing 20
references in place (no re-attach) and sets the counter column
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Page-tree entries get a "Page tree display" field (columns | rail |
rail-compact), emitted as display + cardSize: Markets and Solutions
show their main pages as a list and the sub-pages as image cards on
hover. Page-tree items carry image (page media) and teaser (abstract)
from stage 2. Additive; front ends ignoring display render columns.
- vitec:attach-page-media gains --depth=2 and falls back to the page's
hero background before the grey placeholder; the 39 sub-solution
pages got their hero image as page media.
- MegamenuJsonRenderer tags every page carrying the menu with the menu
tables and tt_content_<uid>, so saving menu records refreshes all
pages instead of waiting for a full flush.
- Products catalog: drop catalog.news; both promo boxes ("Product
highlight", "Product news") are the entry's editorial teaser cards.
ProvideInsightsSpotlight back to its previous state.
- Spec v1.29 and v1.30 (header version corrected), README.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rebuild the product section after the agency sitemap and menu prototype
of 2026-11-02:
- vitec:build-product-overviews builds sysfolder labels (3 categories,
9 groups) below /products with 20 overview pages /products/<slug>
(layout 9: hero, intro per group, product cards, contact CTA) and two
menu shortcuts. Dry-run by default, idempotent, explicit sorting.
- ProvideProductCatalog reads that page tree and emits catalog version 2:
categories[].groups[].items[] of type page (productCount, products,
image) or shortcut (target indices), plus viewAll, news and search.
- Transitional v1 fields (groups[].products/link/uid, categories[].uid/
link, product teaser) keep the deployed front end alive; it read the
v1 shape and rendered a white page without them. Remove once the
front end reads items.
- ProvideInsightsSpotlight::latestNews() is public with a count.
- Product type-ahead (type 7385) adds matching overview pages and a
per-product overview with its menu path.
- Spec v1.28.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The Resources Section Layout select gained a third value, hardware
("Layout 3 - Hardware option"): Technical Highlights spread over two
columns, no resource cards
- ProductShowJsonRenderer::resourcesBand() emits the same envelope with
items: [] for hardware even when cards are maintained, so the cards
stay on the product and reappear when switching back to layout 1 or 2
- Spec v1.27 (resources.sectionLayout values)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- comparison report migrations/check_product_downloads.php (kept,
read-only): download records vs. the delivered product workbooks -
34 of 74 workbook products have a datasheet, the entire Datapath
line has none in the pool (import came from vitec.com; queued for
Joe), ~35 orphan datasheets belong to products without records;
a vitec:link-product-downloads re-run added seven clean links
(Artio x2, Diamond-H, the three TOUGH records, X-View)
- RTE resolution fixed at the root: ContentElementResolver and
ContainerChildrenProcessor passed bodytext RAW into the payload, so
t3:// links leaked unresolved; both now run RTE columns (bodytext,
vitec_quote) through RteResolver::html()
- the imported "Download Success Story" RTE buttons carried the wrong
link identifier (tx_vitec_download -> download, one-time migration
fix_download_record_links.php) AND old-site uids - missing here or,
worse, accidentally pointing at foreign PDFs. New
vitec:convert-story-download-buttons replaces them with real
vitec_downloadcard plugins: the download is resolved by STORY title
(manual map for ISR / "Okada Manilla", exact-title fallback for
suffixless PDFs like "Lord's Cricket Ground"); 29 converted, 4
stories without a delivered PDF have their button hidden. New
FlexForm layout "Success Story Download" (story_download) applied
everywhere; the FE renders it as the previous centered button
- the ADIB "Featured Products" text section (the only one site-wide,
verified by scan_story_headers.php) is now ONE vitec_productlist
with hand-picked products via old-name aliases and the new FlexForm
layout "Success Story Products" (story_products); the four text
elements are deleted. vitec:convert-story-product-sections stays
re-runnable for future imports
- the productlist envelope additionally carries "columns" (= number
of products, capped at 4) so the story grid renders as many columns
as it has products - additive key, available to every product list;
and hand-picked lists now ship successStories as an empty array (the
empty category selection used to aggregate stories over the WHOLE
tree, leaking story cards into the section)
- the story downloadcards carry header "Downloads" (set on convert
and backfilled): the front end builds the story anchor nav from
element headers, so the section now appears there
- diagnosis scripts kept: check_download_record, check_story_elements,
scan_story_headers; verified live on the ADIB payload (structured
download object, productlist [5,18,6], texts 10 -> 5)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- the freshly attached card images did not show: text_only is the
explicit no-image variant, so vitec:attach-card-images now flips a
card to "vertical" whenever it carries (or receives) an image; and
the new placeholder PNGs sat in the sshfs 770 trap - fix-asset-perms
covers them, with public/product-audit added to its targets
- new generic vitec:wrap-cards-grid --page=<slug>: wraps a page's cards
into vitec_cols_33_33_33 containers (b13 columns 221/222/223), three
per container, section-aware - every top-level intro paragraph starts
a section, other element types close it, so the category headings on
/products keep their grids beneath them. Existing grid containers are
pooled and reused, surplus ones hidden
- the first apply aborted mid-move and left a half state (15 empty
shells, three cards moved; diagnosis migrations/check_grid_447.php,
kept) - v2 repairs such states by design: global container pool,
hard asserts after the create pass, try/catch around the move pass,
and a final "no card left top-level" verification
- applied on /products and verified live: 38 cards in 15 grids
(sections 5/7/3/6/2/4/2/6/3 -> 2/3/1/2/1/2/1/2/1 containers), order
intro -> grids -> banner -> faq intact, children delivered in the
known items/contentElements shape
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- new vitec:attach-card-images (dry-run by default) for the ~145
vitec_card elements the 2026-10-27 workbook imports created across
/products, /insights, /support and /contact: a card linking
/product/<slug> gets the record's first product photo (hero banner
as fallback), every other card gets the numbered placeholder
placeholders/pages/<pid>-NN.png counted from slot 10 in card order
per page (slots 01-04 and 08 are taken by the page conventions; the
number doubles as the image wish list towards the agency). 110
placeholder PNGs (640x480) were generated from the live payloads so
the numbering is deterministic; cards that already carry an image are
never touched but keep advancing the counter, so re-runs stay stable
- container children are included: the editor had arranged the /support
cards into a grid container (colPos 221-223/251), which the first
top-level-only query skipped
- applied and verified live: 42 product photos, 110 numbered
placeholders, 18 generic grey cards - the grey ones map the records
without any image at all (ArtioSign, ArtioView, Arqa, the Aetria
family, Wall Control 10, X-Series; all Datapath software without an
image delivery, queued for Joe)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- new vitec:build-product-portfolio (dry-run by default): hero, nine
category sections (intro paragraphs with the exact sitemap H2s and
Learn-more buttons onto the new category pages), 38 product cards
with record-first link resolution (30 resolved; the 8 open record
gaps stay reported), a Case Studies & Events banner (midnight,
success stories / events), ONE vitec_faq accordion whose four
questions are created as vitec_faq_items collection children
(field names probed against the schema at runtime), and the orange
prefooter banner (contact / solutions); full page properties and
page layout 0 -> 1 "Index Page"
- diagnosis first (new read-only migrations/check_products_page.php
and check_products_page2.php): the dry run reported zero legacy
elements although the payload rendered ~40 - every own element of
page 447 was already soft-deleted, the visible rendering came from
the "Collection Product Infos" compose page. Building in place was
therefore safe; unconsumed visible legacy would have been hidden,
not deleted
- side finding, left open on purpose: six old-taxonomy category stubs
(#451-454, #456, #458) still sit visible under /products with the
family pages beneath them - hide/move/redirect is an editorial
decision queued for Olli
- applied and verified live (hero, 9 category buttons, 30 card links,
4 FAQ items, both banner CTA pairs, meta)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- new vitec:create-missing-products: MGW Diamond TOUGH, MGW Pico TOUGH,
MGW Pico+ TOUGH and X-View Integrated Displays as visible records
(teaser drafts, pid and sys_category assignments copied from the
sibling product; titles equal the Dropbox folder names so the image
importer matches immediately). IQS4 stays out - its delivery folder
is empty, question to Joe
- asset re-run via vitec:import-product-images after re-staging the
Dropbox delivery (the misfiled Diamond-OG banner corrected into the
OG inbox folder again): new photos for 95-Series, Avedia chassis,
SFF PRISM and the new TOUGH/X-View records
- new migrations/build_product_audit.php: generates the internal
product-asset audit at /product-audit/ (same basic auth, same-origin
thumbnails) - one row per record with thumbnail, detail link, badges
for hero/photos/texts/resources/datasheets/solutions, flags, stats
and client-side filters; re-run any time
- new vitec:import-product-category-pages: builds the nine
/products/<category> pages (frontend layout 9, hero/main/preFooter)
from the agency "Product Category Pages" workbooks - intro
paragraphs, Why-VITEC / product / solution cards, the comparison
rows as ONE text element with a plain table (no comparison CType
exists; FE styles it), prefooter banner to /contact, full page
properties, page sorting per sitemap 3.1-3.9; the empty shells #455
and #457 are reused. Product card links resolve record-first (exact
title, stripped parenthesis, family alias, unique slug prefix);
ProductFamilyAliases gains ten category-level family labels. Solution
cards tolerate US/UK spelling (center/centre, visualization/
visualisation). Applied and verified live (nine routes, links,
tables, meta)
- known gaps reported, queued for Joe: IQS4, Media Players (93/94),
Chassis Systems, Express Backplanes, Accessories & Cables, PCIe
Encoders, VMS Plugins & Integrations; the Vision family card awaits
a flagship decision
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- 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>
- vitec:align-market-records gains --delete-dropped: soft-deletes the
records the agency dropped from the taxonomy, including their MM rows
(DataHandler does not clean the foreign side on delete). Decision:
all nine legacy records go, including Healthcare #42 - the Overlake
story loses its badge on purpose and reports as unresolved on future
importer runs
- the run exposed a regression: the RENAME_MAP entries Government ->
Government & Agencies and Education -> Education Communications are
not idempotent because both old names double as NEW main-market
names. The re-run hijacked the main records (stories and teaser
travelled along), created empty replacements and deleted the real
sub-market records as unclaimed
- repair: migrations/fix_market_rename_regression.php (dry-run default,
guarded) swaps the pairs back - main records keep their stories and
workbook teasers, the fresh empties take over the sub-market roles;
applied and verified live (marketlist 11/11 with main detail pages,
badge distribution back to 20/9/9/8/6/4/1, no legacy names left)
- the two non-idempotent entries are removed from RENAME_MAP with a
comment: a rename mapping whose old name is reused by the new
taxonomy must not survive its one-time run
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
orascheandClaude Opus 5.5