Backend module: CSV import for the VITEC domain models
New "VITEC Import" module under Web: one import page per domain model (v1: Market, Solution, Product - registry-driven, adding a model is one config entry). Workflow: upload a CSV (delimiter and encoding are auto-detected, including German-Excel semicolon/Windows-1252), map CSV columns to DB fields, persist the mapping per model together with the identity field used for matching (new table tx_vitec_import_mapping, no TCA - pure tool configuration), review a unified list of CSV rows matched against the DB records (new / update with differing fields / unchanged / db-only), then apply the checked rows through DataHandler. Each importable row carries an editable JSON payload textarea - what is written is the textarea content, not the raw CSV, so editors can fix values right in the review step. The parsed CSV travels through the form as a hidden JSON field: no session state, no temp files. Importable fields are derived from TCA at runtime (scalar types only; files, categories and other relations are excluded - a flat CSV cannot carry them). Payloads are whitelisted against that field list on apply; new records require a storage pid (prefilled from existing records). BE user permissions apply via DataHandler. The module ships its own CSS (backend-import.css, loaded only by this module) using the frontend button palette from _vitec.scss: orange #f47937 for primary actions, navy #26358c for secondary actions and structure. The stray <h2>Hi</h2> debug leftover in the shared backend layout is removed (also affects the OG Image module). A fourth tab "SEO Research" handles the recurring keyword-research CSV. It is deliberately not an import mask - the file carries research only (no meta title/description yet). Each upload is persisted as a delivery (tx_vitec_seo_research, never deleted) and evaluated: diff against the previous delivery keyed by URL, a structure check of the CSV tree against TYPO3 (pages by slug path; market/solution/product rows against the domain tables, matched by slug then normalized title), and the three work lists from the SEO flags (quick wins by GSC impressions, shared terms grouped by keyword, already ranking). CsvReader now deduplicates repeated header names, which that CSV has. New CLI command vitec:create-markets: creates the market records the structure check reports as missing, sourced from the stored delivery and matched through the same SeoResearchService - what the module lists is what the command creates. Each market gets a sys_category of the same title, found anywhere under the auto-detected market category root or created; sub-market categories are created under the parent market's category, so the category tree carries the hierarchy the flat market model cannot. Idempotent, dry-run first. New CLI commands vitec:create-markets and vitec:market-dummy-image. create-markets creates the market records the structure check reports as missing (root detection three-staged: option, auto-detect, find or create a "Markets" category). market-dummy-image assigns a shared placeholder (white logo on brand navy, fileadmin/placeholders/) to every market without an image - one sys_file for all, replacing the file restyles every placeholder at once. Both idempotent. Deliberately out of v1: import log with three-way compare (protection against overwriting manual edits), images/relations, multiple saved mappings per model.
This commit is contained in:
@@ -37,6 +37,7 @@ this extension turns every content element into clean **JSON** for a React front
|
||||
- [Forms](#forms)
|
||||
- [Page‑level fields](#pagelevel-fields)
|
||||
- [Structured data (JSON‑LD)](#structured-data-json-ld)
|
||||
- [Editorial tooling](#editorial-tooling)
|
||||
- [Requirements](#requirements)
|
||||
- [Installation](#installation)
|
||||
- [Adding a new headless plugin](#adding-a-new-headless-plugin)
|
||||
@@ -188,6 +189,25 @@ endpoint) and `vitec/success-story-path-rewrite`, which lets the public SEO URL
|
||||
`Organization`, `WebSite` (root only), `BreadcrumbList`, `Product`, `VideoObject`,
|
||||
`FAQPage`, `ExhibitionEvent` and `NewsArticle`.
|
||||
|
||||
## Editorial tooling
|
||||
|
||||
**Backend module "VITEC Import"** (Web menu): CSV import per domain model
|
||||
(Market, Solution, Product) with a persistable column mapper and a unified
|
||||
review list (new / update / unchanged / db-only) — what gets written is the
|
||||
editable per-row payload, applied through DataHandler. A fourth tab
|
||||
**SEO Research** stores each delivery of the recurring keyword-research CSV,
|
||||
diffs it against the previous one and checks the CSV structure against the
|
||||
page tree and the domain records.
|
||||
|
||||
| CLI command | Purpose |
|
||||
|---|---|
|
||||
| `vitec:import-success-stories` | One-time migration of the old-site success stories |
|
||||
| `vitec:import-downloads` | Import old-site downloads (Collateral only, idempotent, filename normalization) |
|
||||
| `vitec:create-markets` | Create market records the SEO structure check reports missing, incl. sys_category assignment |
|
||||
| `vitec:market-dummy-image` | Assign the shared placeholder image to markets without an image |
|
||||
|
||||
All commands support `--dry-run` and are safe to re-run.
|
||||
|
||||
## Requirements
|
||||
|
||||
| Component | Version |
|
||||
|
||||
Reference in New Issue
Block a user