-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
The generated site is static and can be opened directly from disk. Some browsers restrict localStorage on file:// URLs, which can affect theme state and media volume/mute persistence.
If behavior seems inconsistent, serve the output folder locally:
cd path/to/site
python -m http.server 8000Then visit:
http://localhost:8000
During media staging, cr4te tries to create symbolic links first and hard links second. If neither works, the build aborts instead of copying media files.
Common fixes:
- Enable symlink creation privileges.
- On Windows, enable Developer Mode or run from a shell with the needed rights.
- Put input and output on the same filesystem so hard links can be used.
If the output folder exists, cr4te asks before clearing it.
Use --force to skip confirmation:
cr4te build -i path/to/Creators -o path/to/site --forceBy default, existing thumbnails are preserved. Use --clean to delete thumbnails too:
cr4te build -i path/to/Creators -o path/to/site --clean --forcecr4te rejects invalid JSON, non-object metadata files, unknown fields, invalid dates, and missing path references.
Default best-effort mode reports issues and skips invalid entries where possible:
- Invalid creator metadata skips that creator.
- Invalid project metadata skips that project only.
Use strict mode when you want the build to fail immediately:
cr4te build -i path/to/Creators -o path/to/site --strictIf a configured portrait or cover path is set but missing, it is a metadata issue.
If no path is configured, cr4te tries to find a suitable image by configured basename. If none is found, it uses generated default thumbnails where needed.
Project facet values only participate in search if the resolved field config marks them as searchable, clickable, or tags.
Check:
cr4te print-config --domain musicThen inspect site_rendering.project_metadata.fields.
Check:
- The extension is supported.
- The file is within
media_rules.max_search_depth. - No folder or file path part starts with the configured exclude prefix.
- The file is not hidden.
- Image sampling has not excluded it.
clean-json deletes creator and project metadata files.
Preview first:
cr4te clean-json -i path/to/Creators --dry-runActually delete:
cr4te clean-json -i path/to/Creators --force