CSV import/export and REST API drop newer columns (og_video, event_data, recipe_data, custom_schema) #101

New Issue

2026-06-29T14:19:31Z

jmiller commented

2026-06-29 14:19:31 +00:00

Problem

The v1.3–v2.0 columns og_video, event_data, recipe_data, and custom_schema exist in the schema but are absent from the CSV import/export column set (com_mokoog/src/Controller/ImportExportController.php) and from the REST API field whitelist (com_mokoog/api/src/View/Tags/JsonapiView.php:26-65). Confirmed: those four column names appear 0 times in either file.

Impact

CSV export → edit → import silently drops these fields (data loss on round-trip).
API consumers can't read or write video/event/recipe/custom-schema data.

Fix

Add the four columns to the CSV header + row mapping in both export and import (with validation — e.g. JSON fields must be objects/arrays, see the scalar-JSON-LD blocker).
Add them to fieldsToRenderItem/fieldsToRenderList in JsonapiView and to the API create/update whitelist.
Bump the OpenAPI spec accordingly.

## Problem The v1.3–v2.0 columns `og_video`, `event_data`, `recipe_data`, and `custom_schema` exist in the schema but are **absent** from the CSV import/export column set (`com_mokoog/src/Controller/ImportExportController.php`) and from the REST API field whitelist (`com_mokoog/api/src/View/Tags/JsonapiView.php:26-65`). Confirmed: those four column names appear **0 times** in either file. ## Impact - CSV export → edit → import **silently drops** these fields (data loss on round-trip). - API consumers can't read or write video/event/recipe/custom-schema data. ## Fix - Add the four columns to the CSV header + row mapping in both export and import (with validation — e.g. JSON fields must be objects/arrays, see the scalar-JSON-LD blocker). - Add them to `fieldsToRenderItem`/`fieldsToRenderList` in `JsonapiView` and to the API create/update whitelist. - Bump the OpenAPI spec accordingly.

jmiller added the bug label 2026-06-29 14:19:31 +00:00

jmiller commented

2026-06-29 14:19:33 +00:00

Branch created: feature/101-csv-import-export-and-rest-api-drop-newe

git fetch origin
git checkout feature/101-csv-import-export-and-rest-api-drop-newe

Branch created: [`feature/101-csv-import-export-and-rest-api-drop-newe`](https://git.mokoconsulting.tech/MokoConsulting/MokoSuiteOpenGraph/src/branch/feature/101-csv-import-export-and-rest-api-drop-newe) ```bash git fetch origin git checkout feature/101-csv-import-export-and-rest-api-drop-newe ```

jmiller referenced this issue from a commit

2026-06-29 14:52:58 +00:00

fix: security & correctness batch (#99, #100, #101, #102, #106)

jmiller referenced this issue

2026-06-29 14:53:22 +00:00

fix: security & correctness batch — AI ACL, sitemap disclosure, API/CSV columns, forward-compat (#99 #100 #101 #102 #106) #109

jmiller referenced this issue from a commit

2026-06-29 14:53:44 +00:00

Merge pull request 'fix: security & correctness batch — AI ACL, sitemap disclosure, API/CSV columns, forward-compat (#99 #100 #101 #102 #106)' (#109) from fix/security-correctness-batch into dev

jmiller commented

2026-06-29 14:54:21 +00:00

Fixed in PR #109 (merged to dev). og_video, event_data, recipe_data, custom_schema are now in the CSV export/import (appended, so old CSVs still import) and the REST API field whitelist. Import validates the JSON fields as arrays/objects and og_video as http(s), so a CSV round-trip can't re-introduce the #97 scalar crash. Closing.

Fixed in PR #109 (merged to `dev`). `og_video`, `event_data`, `recipe_data`, `custom_schema` are now in the CSV export/import (appended, so old CSVs still import) and the REST API field whitelist. Import validates the JSON fields as arrays/objects and `og_video` as http(s), so a CSV round-trip can't re-introduce the #97 scalar crash. Closing.

jmiller closed this issue

2026-06-29 14:54:27 +00:00

jmiller referenced this issue

2026-06-29 16:00:44 +00:00

docs: CHANGELOG + README for the current development cycle #114

jmiller referenced this issue

2026-06-29 16:26:51 +00:00

Release: promote dev → main (dashboard, edit UI, ACL, security & forward-compat) #115

Sign in to join this conversation.