[Bug]: Can't add field for Custom Data Table

[boborua]

Summary

browser will report this error:

installHook.js:1 [react-root:caught] TypeError: crypto.randomUUID is not a function TypeError: crypto.randomUUID is not a function

Steps to reproduce

1. goto route: admin/data
2. add custom table
3. add filed

Expected behavior

custom data fields should can be created

Actual behavior

page crash

Version or commit

0.0.14

Deployment mode

Docker Compose with Postgres

Logs or screenshots

[lovepixel-git]

Root cause is the secure-context restriction on crypto.randomUUID(). It is only defined when window.isSecureContext is true, so an admin reached over plain HTTP on a LAN address or bare hostname has no such function. That matches the Docker Compose setup in the report, and it is why this does not reproduce on localhost, which is treated as a secure context regardless of scheme.

Probed the same dev server across three origins:

origin	isSecureContext	typeof crypto.randomUUID
http://localhost:3001	true	function
http://127.0.0.1:3001	true	function
http://192.168.7.112:3001	false	undefined

The crash comes from makeOption() in src/admin/pages/data/components/NewFieldDialog/newFieldDialogModel.ts, which calls crypto.randomUUID() directly. There is a second, so far unreported instance of the same bug in handleAdd() in src/admin/pages/site/panels/FrameworkScalePanel/ClassGeneratorList.tsx.

Both look like anomalies rather than intent: nanoid is already the id primitive everywhere else in the codebase, including src/admin/pages/data/utils/fieldDefaults.ts and src/core/framework/scaleGroups.ts in these same two feature areas. SelectOptionSchema.id is Type.String() with no format constraint, so switching generators keeps existing UUID-shaped ids valid and needs no migration.

Opening a PR shortly that moves both call sites onto nanoid, with a regression test that exercises makeOption() with crypto.randomUUID removed.