14. Oktober 2026 · Changelog
CDPCMS 2.1.0
- Add modules (1096): Modules page has „Add module“: upload a module package (ZIP with one folder and module.json) or install from the module catalog (`storage/app/module-catalog.json`, every package checked against its sha256). Checks before anything is written: size, folder name, no unsafe paths or links, allowed file types only, minimum CDPCMS version (`requires_cdpcms`). A new module stays inactive until it is activated; an update only accepts a newer version and keeps the previous folder in `storage/app/module-backups/`. Loading indicator while installing.
- Theme template folder (1089): a theme reads its page templates from `cms/themes/<theme>/templates`. File names stay as they are (`standard` is a page, `post` is a post). A website without a theme keeps `cms/templates`. A theme that has no `templates` folder yet is still read from its previous folder. A new theme receives the starter templates once; existing files are not overwritten. Published pages stay in the website `content/` folder.
- CDPWiki templates (1089): `wiki-index`, `wiki-article` and `wiki-texts` are part of the default page templates for every website. A site shows the overview (20 articles, 4 by 5, with page numbers), the article with a sidebar, and the CMS entry that holds the wiki texts. The filler is `connect/cdp-wiki.php`.
- Responsive content images (824): on upload, edit and publish, raster images under `/core/assets/gfx/` get width steps 160, 320, 480, 640, 800, 960, 1280 and 1600, never larger than the original. The publisher adds `srcset` and `sizes` to those images. An image that already has `srcset` is left unchanged. Deleting the file removes its steps. Release through the approval button.