Skip to content
JoeCMS Download 3.1.5

Changelog

Every JoeCMS version, described by what it changes for the people using it.

3.1.5

8 Nov 2026 Latest stable release

Security 1 entry

  • /install closed on installed sites. When the site is already configured, the old installer prefills its form with the configuration in use, database and SMTP passwords included, and accepts the form submission (frmAction=install). It was reachable from the public /install route without any login. Now, on an installed site, the installer only opens from the back office (Configuration → Basic, /admin/configuration/install, where the CMS asks for login); any other address, /install in every variant included (/INSTALL, /install/, ?setup), answers 404. The check sits at the top of the installer, so it holds whatever path leads there. (conf/gallery/install/index.php; manual 01)

Fixed 3 entries

  • An unreachable store no longer takes the page down. With DEBUG_MODE on, an isError() on an unconfigured storage — typically the page statistics on MongoDB, which a new installation doesn't have — printed the error sheet and closed the page in place of the requested page: /login answered with the CMS error and looked broken. Now that case writes a line in cache/logs/…_storage_nosql.txt and the page carries on. With debug off the page was already served: the error used to go to …_error_critical.txt, now it goes to the storage log. The SQL branch stays as it was: a missing relational database must make itself heard (vendor/wolfgan/storage/Storage.php, controller_nosql).
  • /install no longer answers 500. A GET /install on an already installed site — for example a crawler's scan — ended in an E_USER_ERROR («Catrina: Percorso Riservato. Verificare perche entra qui»), hence in an error page and a report in Sentry. cmsRouter::regexp() expanded * to (.*) even inside a hand-written group, so the source ^/install(.*) became ^/install(.(.*)) and no longer matched the short URL: the kernel recognised the page but not its route, and the service/updater case of system_init_on_before_routing() fell through — because of a // no break — into the actex case, which raises the fatal error. Same fate for /updater/check, whose page doesn't even have a router. Now * becomes (.*) only outside groups, and if the page route doesn't close the request it carries on: the Content Manager router takes it, and a path that doesn't exist answers 404. (vendor/wolfgan/cms/services/router.php, library/gallery/system/init.php; manual 01 §2)
  • The installer opens on PHP 8. From the back office (Configuration → Basic) the page came out empty because of three cases that were warnings in PHP 7 and are fatal in PHP 8: the ini_get("mysql.max_persistent") check (an ext/mysql directive, removed in PHP 7: ini_get() returns false, the comparison with -1 always fails and the installer declared itself critical, printing only «mysql.max_persistent must be Unlimited»); VG_SITE_ADMININSTALL, a constant nobody defines, read in the comparison; cm_getClassByFrameworkCss("", "link", null, "bootstrap"), which passes the framework name where the already resolved structure is needed. Also, the final branch redirected to /setup, a URL that doesn't exist on a JoeCMS site: now it redirects to the same URL with ?setup. The FTP_* constants, which only the old config.updater.php defined, are read with defined(): without credentials you see «FTP Path unavailable» instead of a fatal. (conf/gallery/install/index.php, conf/gallery/install/common.php, library/FF/common/framework-css.php)

3.1.3

31 Oct 2026

Fixed 2 entries

  • Ajax POSTs reach the module, not the page they start from. For every XHR request on a public page, library/gallery/system/init.php first tries to render the sections of the Referer page, and if anything comes out it answers with them and stops. It is there to reload blocks, but it also caught submissions: a POST to /registrazione sent from the home page received the home page HTML and the account was not created. From the /registrazione page it worked, because there the sections are empty. Now POSTs no longer take that path; GET reloads stay as before. (manual 01 §2, 08)
  • The page cache no longer saves or serves responses to POSTs. The key of a cached file contains the request parameters, form fields included: the wrong response from the point above was saved, and whoever sent the same data again got it from the cache, even from the right page. check_static_cache_page() now drops POSTs before looking for the file and turns writing off (DISABLE_CACHE). (library/gallery/system/cache.php; manual 12 §2)

3.1.2

30 Oct 2026

Fixed 1 entry

  • bin/deploy.sh makes itself executable. A project created by copying the files of cms received the script without the execute bit, and ./bin/deploy.sh answered permission denied on every new project. Launched once with bash bin/deploy.sh, the script now restores the bit on disk and in the git index and asks you to commit it. (bin/deploy.sh, docs/manuale/14-ambienti-e-deploy.md)

3.1.1

26 Oct 2026

Fixed 4 entries

  • A half-written cache file no longer brings the page down. Filemanager::save() wrote the file in place with file_put_contents(..., LOCK_EX): two requests rewriting the same file (the error documents index, which bots grow with made-up URLs) could leave a truncated copy to another one, and including it gave a fatal ParseError (Sentry 155604961). Now a temporary file is written and renamed, which is atomic, and the file's OPcache is invalidated. A corrupted file that gets read anyway is deleted and rebuilt on the next write, instead of stopping the request; before, on PHP 8, that branch also crashed because of the Filemanager::DEBUG constant, which did not exist. Fixed the precedence in SEARCH_IN_KEY || SEARCH_IN_BOTH && isset (fs_php.php, fs_xml.php): a missing key returned array($chiave => null), which counts as true; now it does not (vendor/wolfgan/filemanager/; manual 11 §3). The error documents index stays written and never read, on purpose: cache_get_error_document() calls it with the arguments swapped, and putting them back in order would turn a healthy page into a 404 every time the index is corrupted (library/gallery/system/cache.php).
  • AGENTS.md no longer goes to the server. bin/deploy.sh left out CLAUDE.md and MEMORY.md, but not AGENTS.md, the instructions file read by Antigravity, Cline and the other AI assistants: with the deploy it ended up in the docroot, downloadable by anyone like the rest of the internal documentation. Now it stays out like the other two. On a site already deployed the online copy must be removed by hand.
  • A module can have /api in its paths. The kernel and the core's api rule grabbed any path that contained /api — a module's /jd/api/me, /apicoltura — and sent it to the framework's internal REST, which answered 404 with an empty body before the module or the page was reached. Now /api is reserved only as the first segment, and so is /srv in the services rule (before, it also grabbed /blog/srvizio). A path with a language prefix (/en/api/…) no longer reaches the internal REST: the platform does not use any. Found with JoeDesk, whose APIs in production did not respond (vendor/wolfgan/cms/services/kernel.php, conf/routing_table.xml; manual 01 §3 and 04). bin/deploy.sh no longer warns about service files starting with api-: they work now.
  • HTML no longer stays a week in the browser. The installer's .htaccess set text/html "access plus 1 week": CMS pages declare their own cache, but a module controller, a custom script or a redirect without headers stayed seven days in the browser, and Apache added its own max-age=604800 even next to the PHP one. With JoeDesk the redirect to the login stayed cached and, after signing in, the browser went back to the login by itself. Now "access plus 0 seconds" (install/lib.php, .htaccess, the old installer's conf/gallery/install/.htaccess-*.tpl templates; manual 12). The deploy does not upload the .htaccess: on sites already installed the line must be changed by hand.

Security 2 entries

  • PHPMailer 7.1.1 instead of 5.2.14. 5.2.14 dates from 2015: it has the known flaws of the mail() transport (CVE-2016-10033, CVE-2016-10045) and was never updated for PHP 8. 7.1.1 comes from the official tag, with the commit Packagist points to. The platform loads it with the 5.2 paths and names: class.phpmailer.php, class.smtp.php and class.pop3.php stay as adapters (PHPMailer, phpmailerException, SMTP, POP3 are aliases of the 7 classes), so Mailer, process_mail() and the sites' code do not change. Gone are the 5.2 OAuth, EasyPeasyICS, NTLM, and with them get_oauth_token.php and the examples/ and test/ folders, which on the server were scripts anyone could run. Tested with PHP 8.1 and 8.5 on what Mailer and process_mail() use (language, SMTP, CC, BCC, Reply-To, embedded images, attachments, quoted-printable, catch (phpmailerException)), and with real sends via JoeSMTP (library/phpmailer/, vendor/wolfgan/mailer/Mailer.php; manual 06 §2).
  • Internal files no longer open from the browser. Apache serves by itself every file that exists, and the kernel's 404 on /library, /vendor… only applied to requests reaching index.php. On desk.giorgiopalermo.com one could download the CMS logs (cache/logs/…_request.txt, 363 KB for the day, and the SQL errors), the database.sql dump and CHANGELOG.md, and run the PHP files in library/, vendor/, ff/, conf/, cache/, migrations/ (PHPMailer's get_oauth_token.php answered 500). Now the installer's .htaccess answers 404 to PHP, .sql, .log, .sh, .ini, .lock… in those folders and in applets/, contents/, uploads/, to all of cache/logs/ and to database.sql and the root .md files. Static files (CKEditor in vendor/), cm/, themes/ and modules/ stay open (install/lib.php, .htaccess, conf/gallery/install/.htaccess-*.tpl; manual 14 §3 and 01 §3). The deploy does not upload the .htaccess: on sites already installed the block must be added by hand, right after the HTTPS redirect.

3.1.0

10 Oct 2026 DB schema → 5

Fixed 10 entries

  • Login errors are in the page's language. On /en/login, /fr/login or /es/login the form still answered in Italian: "Utente non ancora attivato clicca qui", "Username o password errata", "Campo username o password non compilato". Now Auth::login() answers in Italian, English, French or Spanish (other languages get English), and the link for an account still to be activated leads to the activation page in the same language (/en/activation, /fr/attivazione) instead of always to /activation. The two messages the script writes by itself (a response without an error, a service that does not respond) follow the page's language too, and 2FA in Spanish no longer comes out in English. The texts live in Auth::text(), like the 2FA ones: they work even without dictionary rows. (vendor/wolfgan/auth/Auth.php, vendor/wolfgan/auth/widgets/login/script.js, manual 08 §1)
  • Password recovery and activation in the page's language. Recovery showed in Italian the field validations, the "REIMPOSTA PASSWORD" button, the strength labels and the wrong-code error; "Email mancante o non valida" and the screen reader labels of the six code boxes were in Italian in activation too. Now the browser texts come from the dictionary through the theme template, and the server ones from Auth::text(). The link back to sign-in and the final buttons towards the personal area follow the language and JC_USER_AREA_PATH (Auth::userArea()), instead of always pointing to /login and /area-utente. (themes/site/contents/recover/index.html, themes/site/contents/activation/index.html, vendor/wolfgan/auth/widgets/recover/index.php, vendor/wolfgan/auth/widgets/activation/index.php, manual 08 §1)
  • Account emails go out in the recipient's language. Activation and recovery had body and subject in Italian for everyone ("Il nostro benvenuto! Codice attivazione: …"). Now the templates use the dictionary and the Mailer translates them into the language of Mailer::setLang(), that is the recipient's profile language: before, the template codes always followed FF_LOCALE, and from a cron job the body came out in the default language. hook.php builds the subject in the same language. A subject that is already written is no longer looked up in the dictionary: with the code inside it, every email added a placeholder row to ff_international. (vendor/wolfgan/mailer/Mailer.php, hook.php, themes/site/contents/email/auth/, manual 06 §2)
  • The 2FA code email can go out. The template was auth::account_code.html, a name the Mailer does not resolve: sending failed (mailer_template_notfound) and sign-in replied that the code could not be sent. Now there is the theme template themes/site/contents/email/auth/account_code.html, translated, falling back to the module's one. 2FA stays off by default. (vendor/wolfgan/auth/Auth.php, manual 08 §5bis)
  • Cookie banner translated, and back in shape. Its texts were hard-coded in Italian: now they are in the dictionary (svc_cookie_*), and the privacy policy link is in the page's language. The inline CSS lost three rules, deleted by the template engine because {word:word} braces look like variables: the "Customize" panel stayed always open and on mobile the buttons did not line up. (themes/gallery/contents/services/cookie.consent.html, conf/gallery/services/cookie.consent/index.php, manual 10 §4)
  • 404, 500 and maintenance pages in the visitor's language. They were Italian only. The texts now live in cm/errori.php in four languages, chosen by the kernel, by the address prefix or by the browser, without needing the database; home and sign-in links point to the same language. (cm/errori.php, cm/extras/404.html, cm/extras/500.html, cm/maintenance.php, manual 13 §1bis)
  • Maintenance mode really stops the CMS. After the 503 page cm/maintenance.php did not exit, and index.php started the CMS anyway: during an update, on half-copied files, with its output appended to the page. (cm/maintenance.php)
  • No more raw codes on the page. A registered user opening /restricted went back to sign-in with mod_auth_profile_not_authorized in a popup; the not-found page of the VGallery engine had not_found_title as its title, and the error box http_response_empty_title. The entries now exist in all four languages, and the access-denied message is in the user's language. (modules/auth/contents/session/index.php, database.sql)
  • An update no longer overwrites the site's PWA manifest. The joecms-update-*.zip package carries its own metadata in a root manifest.json, and the updater extracted it over the manifest the installer writes for the site (name, colours, icons); site.webmanifest and browserconfig.xml went back to the repository defaults. Now the updater protects the three files and the update package does not contain the PWA ones. Whoever updates from 3.0.3 with the updater (which is still the old one) ends up with a manifest.json holding the metadata: just delete it, and the theme uses site.webmanifest, which this package does not touch. (library/updater/JoeCmsUpdater.php, build-zip.sh, library/gallery/common/set_header_page.php)
  • Theme popups in the page's language. themes/site/javascript/root.js wrote in Italian the payment and outcome popups, the close button and the password eye label; the payment-successful message spoke of a "tesseramento" (membership), left over from another project. (themes/site/javascript/root.js)

Changed 1 entry

  • hook.php is entirely platform code; what belongs to the site lives in the config and in hook.local.php. The installer wrote the domain inside hook.php, which the update package replaces: applying an update, a site lost its domain, and with it the distinction between production and staging (no noindex on staging), plus any change made there. Now the domain is JC_SITE_DOMAIN in the config, which updates never touch; the constants at the top of hook.php (AREA_SEO_SHOW_MODIFY, AREA_PUBLISHING_SHOW_PREVIEW, MOD_SEC_PROFILING, MAX_UPLOAD, …) are changed from the config; the site's own code goes into hook.local.php, which hook.php includes at the end, the updater protects and the package does not contain. The updater copies the domain from the old hook.php into the config by itself, and from now on keeps hook.php in the backup. With a manual deploy, before uploading the new hook.php add define('JC_SITE_DOMAIN', 'dominio-del-sito'); to the config. (hook.php, install/lib.php, library/updater/JoeCmsUpdater.php, build-zip.sh, manual 14 §3, 10 §1)

Security 1 entry

  • ?error= and ?success= no longer enter the page as HTML. themes/site/javascript/root.js put the parameter value into the popup as it was: a link such as /?error=<img src=x onerror=…> ran code on the site. Now it is written as text. (themes/site/javascript/root.js)

Docs 1 entry

  • Rule 18: a text the visitor sees is never written in a single language, with the table of where it goes depending on what prints it. (manual 02 §2.3, 00)

Schema 1 entry

  • 5: the dictionary (ff_international) gets the entries for the public texts: cookie banner (svc_cookie_*), account emails (svc_mail_*), password recovery (svc_rec_err_*, svc_rec_reset_btn, svc_pw_strength, svc_otp_digit) and the ones that were missing (mod_auth_*_not_authorized, mod_auth_access_denied, not_found_*, http_response_*). On an existing site they come with migrations/schema_0005_testi_multilingua.php, idempotent, which does not touch translations already written by the administrator. The updater runs it by itself; with a manual deploy it runs before the rest of the code (php bin/update.php --migrations-only --vai or /restricted/updater), otherwise those texts come out as codes.

3.0.3

10 Oct 2026

Added 6 entries

  • Non-destructive automatic update engine and DB migration system. Introduced the built-in update manager (library/updater/JoeCmsUpdater.php) to move safely and painlessly between CMS versions on production sites. The system implements a strict protection blacklist that never overwrites config.remote.php, config.local.php, .htaccess, uploads/ or the cache, runs pre-flight checks of the PHP requirements and write permissions, enables atomic maintenance mode (.maintenance with bypass token) and makes a preventive safety backup before extracting the files.
  • CLI for system updates (bin/update.php). New command-line utility to check the installation status (--status), turn maintenance on and off (--maintenance on|off), safely apply ZIP update packages (--file <path> --vai) or run only the database migrations (--migrations-only --vai).
  • Web interface for updates in the backend (/restricted/updater). New management controller in conf/gallery/manage/updater/index.php with a status dashboard, platform health monitoring, drag & drop upload of ZIP update packages, a real-time log console and guided alignment of the schema migrations.
  • Incremental migration registry (migrations/ and the jc_migrations table). Introduced the database migration system run by JoeCms\Updater\MigrationsRunner, supporting transactional .sql and .php scripts. Created the baseline migration migrations/schema_0004_v302_baseline.php, matching JoeCMS 3.0.2 / schema 4.
  • Centralized maintenance mode handler (cm/maintenance.php). Added a check at the top of index.php that returns a 503 Service Unavailable response and a responsive template in the CMS palette when .maintenance is present, while administrators holding the bypass token keep their access.
  • Dual packaging target in build-zip.sh (installation + update). Extended build-zip.sh to generate both the full archive joecms-<versione>.zip (for new installations, with wizard and DB seed) and the lightweight package joecms-update-<versione>.zip, which carries manifest.json and leaves out the installer, for automatic updates on sites already running.

Fixed 5 entries

  • Multilingual registration routing (conf/modules/auth/routing_table.xml). Removed the rigid leading anchor ^/ from the mod_auth_registration rule, so that localized paths with a language prefix (e.g. /en/registration) correctly reach the auth controller.
  • Resilience and JSON error handling in the registration controller (modules/auth/contents/registration/index.php). Wrapped the POST handler in a try ... catch (\Throwable $e) block that emits JSON directly, turning off FormsFramework's silent interruption ($db->on_error = "ignore") and explicitly checking SQL errors on every query. This way any error returns an explicit JSON response instead of an empty, 0-byte HTTP 200 response. Added defensive language fallbacks to prevent exceptions when dictionary translations are missing, and isolated the post-registration event dispatcher.
  • Preventive validation and localized messages in the registration widget (script.js and index.html). Added a mandatory client-side check of the privacy consent with localized messages (IT/EN) and better handling of generic errors when the server does not respond.
  • .htaccess compatibility hardening on shared hosting. Removed the Options +FollowSymLinks directive from .htaccess and from the installer templates (install/lib.php, conf/gallery/install/.htaccess-*.tpl), which caused 500 errors on restricted shared hosting (such as InfinityFree/iFastNet). Guarded the use of the Apache modules for the CORS and Vary headers (mod_headers.c, mod_setenvif.c) with conditional <IfModule> blocks.
  • Installation wizard cleanup (install/index.php). Removed a duplicated block of code in the setup finalization step.

3.0.2

9 Oct 2026

Fixed 1 entry

  • HTTP double compression prevention and intelligent environment auto-detection. Introduced cm_can_compress() in library/gallery/system/compression.php to detect whether the web server (Apache with mod_brotli/mod_deflate, OpenResty, Cloudflare) or the PHP engine (zlib.output_compression) already handles HTTP compression. When upstream compression is present, PHP always serves plain HTML and disables generation and delivery of pre-compressed .gz files (library/gallery/system/cache.php, library/gallery/system/set_cache_page.php, cm/cm.php, ff/classes/ffTemplate.php, vendor/wolfgan/cache/services/page.php), eliminating the unreadable/hieroglyphic characters bug. If the server lacks compression modules and the client supports gzip, PHP compression remains active. Added SetEnv SERVER_COMPRESSION 1 to .htaccess directives (install/lib.php, conf/gallery/install/.htaccess-*.tpl, .htaccess) to immediately signal Apache compression modules to PHP.

3.0.1

9 Oct 2026

Changed 1 entry

  • PHP 8.4 compatibility for implicit nullable parameter types across libraries and vendors. Normalized all parameter declarations using deprecated Type $param = null syntax by making them explicitly nullable ?Type $param = null across libraries and vendors (PHPExcel, OAuth2, AlgoliaSearch, CssMin, Facebook SDK, IMAP, Minify, MobileDetect, RabbitMQ, MongoDB, Smarty, Symfony Polyfill, Twilio, Twitter, BunnyCDN). Added #[AllowDynamicProperties] attribute to abstract class vgCommon for full PHP 8.2+ compatibility.

Fixed 4 entries

  • Resilience in generating file icons and media previews (ffMedia). Introduced helper method ffMedia::createLinkOrCopy(), which attempts hard link creation between source and destination (link()) with transparent fallback to file copy (copy()) when operations fail due to filesystem constraints (cross-device EXDEV), symlinks, or hosting permission limits, preventing fatal errors. Added existence checks for mode and wizard before accessing array keys.
  • Session management and authentication cookies (authSession). In authentication destroy() method, premature emission of deletion Set-Cookie headers can now be suppressed during session regeneration on login or restore, preventing accidental loss of the newly established session ID. Improved on-disk session verification (checkSession) avoiding false negatives when the session directory cannot be directly listed.
  • Login redirection and customized user area paths. The authentication widget and login controller now dynamically honor the JC_USER_AREA_PATH constant for post-login redirection, route administrators to /restricted, and prevent redirect loops to /area-utente for regular members.
  • Path resolution in CMS kernel (cmsKernel). Corrected path_info normalization in cmsKernel during enginePath stripping prior to language code extraction.

Added 2 entries

  • Installer: multilingual user area paths and localized authentication routes. The setup wizard now supports distinct user area path configuration for each enabled language (with default fallbacks /area-utente, /user-area, /espace-client, /area-usuario, /benutzerbereich, etc.). Automatically populates the localized slug manifest contents/i18n.php for both user areas and standard auth routes (/registrazione, /attivazione, /recupero-password), guaranteeing automatic 301 redirects by the CMS router.
  • Security hardening and web manifest support in .htaccess. Added MIME type mapping for application/manifest+json (.webmanifest, .json) in root .htaccess and installation templates. Updated .htaccess-noscript.tpl protection template using <FilesMatch> and Require all denied blocks to prevent direct script access and execution in uploads and cache directories.

3.0.0

8 Oct 2026

Added 1 entry

  • Native Package Manager module (modules/package-manager/) for ZIP extension upload and installation. Added an area in the administrative backend (/admin/pacchetti and menu item "Gestione Moduli (.zip)") for uploading extension packages in ZIP format (WordPress style). The engine:
    • Validates archive security by blocking path traversal attempts (../) or absolute paths;
    • Inspects the manifest.json descriptor file included in the package;
    • Extracts components into their respective folders (modules/<id>/, contents/, themes/);
    • Automatically triggers database migrations and DDL if manifest.database.schema is defined;
    • Supports interactive post-installation setup wizards for path and settings configuration.

2.0.3

8 Oct 2026

Fixed 2 entries

  • Incorrect preview path for files and images in backend when using CM_SHOWFILES. In ffField_base::process_file() (ff/classes/ffField.php), if a field defined file_saved_preview_url with CM_SHOWFILES (e.g. /cm/showfiles.php/96x96/...), the framework unconditionally prepended "/uploads" to the resulting URL, generating incorrect and non-existent links such as /uploads/cm/showfiles.php/.... Now URLs that already contain CM_SHOWFILES (or /cm/showfiles.php), that already start with /uploads, or that are absolute (http://, https://, //) are used directly; the /uploads prefix is only applied to local relative paths not handled by the image service.
  • Debug error on autocomplete calls with empty query or missing session. In the parsing scripts of activecomboex, autocomplete, autocompletetoken, and autocompletex widgets (themes/responsive/ff/ffField/widgets/*/parsedata.php), if the SQL query stored in the session was empty, an ffErrorHandler::raise("debug", ...) was raised. They now properly return an empty JSON array ([]), preventing unnecessary blocking and debug error messages while typing.

2.0.2

8 Oct 2026

Fixed 2 entries

  • On hosting providers disabling exec(), the site failed to start: "Call to undefined function exec()". During cache reads, the filemanager validated PHP fragments with exec("php -l ...") (vendor/wolfgan/filemanager/services/fs_php.php). On many shared hostings, and on all free ones, exec/shell_exec are in disable_functions and the call resulted in a fatal error — triggered on the very first cached page, including /login. Now syntax is checked with PHP's internal parser (token_get_all(..., TOKEN_PARSE), which throws a recoverable ParseError on PHP 8): identical outcome to php -l on cache files, but always available and without a child process, hence much faster on each read (in benchmarks down from ~70 ms to less than a millisecond). For the same reason, other un-guarded shell command call sites no longer cause fatal errors: the same syntax check in jobs (Jobs::controller_script(), vendor/hcore/jobs/Jobs.php), installer's installer_commandExist() (conf/gallery/install/common.php), and ffMedia::commandExist(), which now consider the command absent if shell_exec is missing, as well as PDF thumbnail generation (ffThumb::load_image()), which falls back to the generic icon instead of interrupting the page without exec.
  • Thumbnails on media. throwing 500 errors on hostings without shell_exec. ffMedia and ffThumb exist in two copies, and sites installed via the wizard (COMPOSER_PATH) load those in vendor/phpformsframework/ (ffMedia.php, ffImage/ffThumb.php), not ff/classes/: the guard is now in both. Without it, every new copy of an image went through ffMedia::optimize(), which looks for external optimizers using shell_exec("which …"), causing its first request to return 500.

Docs 1 entry

  • Manual 14 §1: exec() and shell_exec() are not requirements. The site runs on hosting providers that disable them; without them, only PDF previews and external image, CSS, and JS optimizers are omitted.

2.0.1

6 Oct 2026

Fixed 3 entries

  • With the router's in-memory cache on, the first request failed. cmRouter::loadMem() wrote to $this->router and $this->cache, properties that don't exist on cmRouter (its own are rules, named_rules, ordered): the read triggered "property «router» not found on class cmRouter". On top of that it treated a cache miss (null) as a hit (!== false), and went in anyway. Now it fills the right properties and treats the miss as what it is. The page router cache is also aligned with the key it writes (cache_router; before, __cm_cache__ on the read side and cache_router on the write side): until now it was never reused. The default of CM_ENABLE_MEM_CACHING stays false, and it's the right one: without FF_CACHE_ADAPTER the "memory" is ffGlobals, which lasts one request, and turning it on saves nothing; with the apc and fs adapters on PHP 8 the site doesn't start, because they call apc_store()/apc_fetch(), which APCu no longer has, and apc.php extends a class that doesn't exist (ffCacheAdapterAdapter). It only makes sense with redis or memcached and their server, and even there the gain is small: pages served from the page cache don't reach the router.
  • cmRouter::orderRules() was missing altogether. cm::process() calls it before saving the rules to the cache when CM_ENABLE_MEM_CACHING is on, but the method didn't exist in any class: "function «orderRules» not found on class cmRouter". Now it exists and sorts every priority bucket with ffCommon_IndexOrder, the same criterion already used by cmRouter::process().
  • Error document for a non-existent address: the page no longer gives a 500. A request for a path that doesn't exist — for example a scanner probing /.aws/.env — ends up in system_write_cache_error_document(), which calls Filemanager::update(): there read() can return a non-array value (for example 1, when the included file exposes neither a return nor a declared variable), and on PHP 8 passing an integer to array_replace() is a TypeError. Now update() starts again from an empty array when read() doesn't return an array, as when the file doesn't exist yet: the address comes out 404, not 500. (vendor/wolfgan/filemanager/services/fs_php.php)

Added 1 entry

  • Brotli in the .htaccess generated by the installer. The wizard (jc_htaccess_static_tail() in install/lib.php) and the old installer's templates (conf/gallery/install/.htaccess-cms.tpl and .htaccess-base.tpl) add the mod_brotli filter, guarded by IfModule: on servers that have it, html, css, js, json, xml and svg go out in Brotli to browsers that accept it and in gzip to the others. The block sits before the DEFLATE one: of the two filters, the first in the chain does the compressing, and placed after it a browser accepting both br and gzip always got gzip (tested on Apache 2.4.68). The gain is small: at mod_brotli's default quality (5) about 3% on CSS and JS compared with gzip, and the HTML coming from the page cache stays gzip, because PHP already compresses it. On sites already installed it has to be carried over by hand, because their .htaccess doesn't travel with the deploy.

Changed 2 entries

  • The Cache-Control of public pages seen by guests is a constant. The max-age hard-coded to 7 in cache_parse() (library/gallery/system/cache.php) is now CM_PAGECACHE_GUEST_MAXAGE (cm/conf/config.php, default 7), which can be overridden in the installation's config (config.local.php / config.remote.php). It applies to pages served from the page cache: the response that composes the page the first time still goes out with max-age=3. It only concerns guests: the pages of signed-in users stay no-store. It's there to raise the TTL for sites whose content isn't real-time, without touching the code.
  • CM_ENABLE_MEM_CACHING can be overridden. In conf/gallery/config.php the constant is no longer an unconditional define(): an installation can turn it on from its own environment config. Default unchanged (false), to be left that way unless there's a redis or memcached adapter (see "Fixed"). With the constant on, __CLEARCACHE__ in the URL works too; it has to go with the emptying procedure in the deploy.

Docs 2 entries

  • Manual 12: the router cache and ffCache described for what the code does. Turning on CM_ENABLE_MEM_CACHING isn't "a free optimisation": without an adapter it does nothing, and with apc or fs on PHP 8 it makes the site error out. The adapter table gave fs as "filesystem, default, works everywhere": fs.php is a copy of apc.php (it calls apc_store()), and without FF_CACHE_ADAPTER the cache lasts as long as the request. The max-age of public pages is described in both cases: 3 when the page is composed, and CM_PAGECACHE_GUEST_MAXAGE when it comes from the cache.
  • Manual 14 §4: with a high opcache.revalidate_freq the cache is emptied afterwards, not right away. In the first interval after the upload PHP may still run the old version of an already compiled file, while it reads the templates new from disk: pages regenerated at that moment stay in the page cache with the old code. Empty cache/ once that time has passed, or restart the site's PHP-FPM before emptying it.

2.0.0

1 Oct 2026

Security 1 entry

  • Bcrypt-only passwords, at login and in recovery too. Password recovery saved the new password with MySQL's PASSWORD() (double SHA1, unsalted), and so did every write that goes through the access model. Now every write produces bcrypt (Auth::hashPassword(), the model's password field in inBcrypt), and login accepts only bcrypt (Auth::verifyPassword()): it no longer recognises PASSWORD() and WordPress hashes and doesn't convert them. Anyone who still has a hash in those formats has to reset the password through recovery. A bcrypt hash with a cost other than the current one is rewritten at login. Login no longer uses PASSWORD(), which doesn't exist on MySQL 8.

1.7.0

1 Oct 2026

Added 2 entries

  • Registration: the project's fields reach the event. The widget also sends the form fields named extra[...], as they are, and on_registration_done receives them in $dati["extra"] (to be validated: they come from the browser), together with the date of birth in $dati["dob"]. A project adds its own questions to the form without touching the widget; without extra fields nothing changes. (vendor/wolfgan/auth/widgets/registration/script.js, modules/auth/contents/registration/index.php, manual 08 §5)
  • Translatable password recovery widget. The error messages, the button text after the code is sent and the password strength labels are read from the template — data-err-password, data-err-conferma, data-err-diverse on #errorMsg, data-testo-codice on the button, data-etichette (separated by |) on the label —; without them, the usual Italian texts remain. (vendor/wolfgan/auth/widgets/recover/script.js, manual 08 §1)

Fixed 9 entries

  • The kernel's path rules grabbed every URL that started like a system folder. In vendor/wolfgan/cms/services/kernel.php the entries were '^/conf*', '^/error*', '^/cm*', '^/asset*', '^/cache*', '^/ff*', '^/contents*'… and in cmsRouter::regexp() every * becomes (.*), with a preg_match not anchored at the end: the rule caught everything starting with that word, not just the folder. A site that published a /confronto page saw it answer 404 with an empty body — the page was there and worked, you just never got to it —, /errore ended up on the CMS error page, and /cms, /assetto, /cachet, /ffmpeg, /contents-vecchi in the wrong folder. Now every folder rule is '^/name(/|$)': the folder and what lies under it, nothing else. The same goes for /themes, /uploads and /asset, which still go through cm/static.php, and for the reserved area, /restricted(/|$); /static/*, /media/*, /showfiles/* and the API rules stay as they were. If you run a site in production: after the update it's worth checking whether it uses addresses that started like a system folder (manual 01 §2-3).
  • Language: the language list no longer brings down the pages of signed-in users. The preferred-language engine (library/gallery/common/language_preference.php) runs in the kernel, right after Auth::check(): before ff/main.php and before the Content Manager loads the modules. There get_locale() can't work: without FF_PHP_EXT it's "Undefined constant", and with a cold language cache it goes through mod_auth_get_locale(), which lives in modules/auth/common.php and doesn't exist yet ("Call to undefined function"). 1.5.1 had closed the first case by avoiding get_locale() there until the framework is loaded; GDay, still on 1.3.0, ran into both, with every page of the area returning 500. Now the engine reads the list from the schema the kernel already has in memory (cache/locale.php, the same ff_languages with status > 0) and reuses it for the whole request; and get_locale() itself no longer falls over: it falls back to "php" if FF_PHP_EXT is missing, and to the kernel's schema if mod_auth_get_locale() isn't there yet. (library/gallery/common/language_preference.php, library/gallery/common/get_locale.php)
  • Sign-in: the "Sign in" button never showed why a login was rejected. In the widget's onclick the return path ended up where the script expects the clicked element — hCore.auth.login(url, selector, elem, redirect) — and there elem goes to jQuery: jQuery("/restricted") → "Syntax error, unrecognized expression: /restricted". The response died before writing the API's message (console aside, the page stayed silent); with the right credentials that branch isn't touched, so the defect only showed on failed logins, on the second factor and on dropped connections. The theme's login page had the same onclick, and there the ?ret_url= return was lost as well. Now the templates pass this and the path in fourth place, and the script accepts as elem only an element (or an id), falling back to the form's container. A theme that copied the page with the old onclick now shows the message, but it has to be fixed too to get the return. (vendor/wolfgan/auth/widgets/login/index.html, index-corretto.html, script.js, themes/site/contents/login/index.html, manual 08 §1)
  • Password recovery: for many real emails the code wasn't sent. The validator wanted a top-level domain of 2-4 letters and no + before the at sign: nome@studio.online, nome+studio@gmail.com or a test .invalid weren't emails, Auth::request searched by username, found nobody to write to and answered "ok" anyway. Now isEmail uses filter_var(…, FILTER_VALIDATE_EMAIL). (vendor/wolfgan/cms/services/validator.php)
  • Password recovery on multilingual sites: the welcome email with the activation code arrived. hook.php chose the email template from PATH_INFO, and the switch only knew /recover: on /recupero-password or /en/recover it ended up in the activation branch (wrong subject and template). Now it reads the template Auth::request has already chosen (recover_code or activation_code). (hook.php)
  • /logout was a 404 even for signed-in users. modules/auth/contents/logout asks for the mod_auth_logout rule, which wasn't in the routing table. (conf/modules/auth/routing_table.xml)
  • Payments: from the site the Payment class didn't load. Only the root autoload.php knew it, and index.php doesn't include it (it loads Composer's): checkout, Stripe webhooks and payment cron jobs died with "Class Payment not found". The API found it, and the command-line tests loaded it by hand. (vendor/wolfgan/autoload.php, manual 10 §2)
  • The deploy carried the modules' tests to the server (modules/*/tests/), destructive on the database they're given. Now they're excluded. (bin/deploy.sh, manual 14 §4)
  • PHP 8.5: curl_close() deprecated. In the Notifier and in downloadRemoteFile() it's only called on PHP 7, where it's still needed. (vendor/hcore/notifier/Notifier.php, hook.php)

Security 3 entries

  • ?__debug__ and ?__query__ switched diagnostics on for anyone. Any visitor, by adding ?__debug__ to the address, turned display_errors and the CMS dumps back on: server paths, warnings, variables. Now cm/livello-errori.php removes the two parameters from the request for anyone who may not ask for them: they open from the command line, with SetEnv JC_DEBUG_ALLOWED 1 (or the environment variable), or on a .local copy seen from the machine itself. The API includes it first as well, where before it didn't include it at all: with ?__debug__ warnings could end up inside the JSON. (cm/livello-errori.php, api/1.0/index.php, manual 13 §2)
  • Cache: personal pages went out with public, max-age=3. Whoever signed in with their account — user area, management — got the page with a Cache-Control that declared it public and reusable for three seconds: after signing out the browser showed the area just seen again, and a shared cache could have served it to another person. Now a page with use_cache(false), or seen by a signed-in user, goes out no-store; for guests the page cache stays as it was. (library/gallery/system/set_cache_page.php, library/gallery/system/cache.php, manual 12 §2)
  • checkUserRights(): impersonation only works for a personal record with an account, and the cookie is no longer rewritten on every page. The helper returns the personal-record ID of whoever is signed in (anagraph.ID, the one in Auth::get()["ID"]) or, for an administrator, that of the person being impersonated (?force_id= or the user-id-value cookie). Now an impersonated ID is honoured only if it is a personal record linked to an account (anagraph.ID_user); otherwise it goes back to the signed-in user and the cookie is deleted. And it's deleted only if it's there: before, every call, for anyone signed in, added a Set-Cookie to the response. (hook.php, manual 08 §2)

Changed 1 entry

  • The database schema declared in the CHANGELOG is checked at every release. joecms.it reads it to decide whether the Download page must warn that the version changes the database. build-zip.sh stops, and the pre-commit blocks the release commit, if the section doesn't have · schema **N** in its heading with N = JC_SCHEMA_VERSION, if the ### Schema group is missing when the schema changes (or is there when it doesn't), or if database.sql has changed without raising it. (.githooks/changelog-schema.php, manual 14 §5)

Docs 1 entry

  • The manual's path-residue guard never fired. The example read the Content Manager from $GLOBALS["cm"], which is empty: cm/main.php runs inside Cms::execute() and its $cm is a local variable. The residue came out empty without errors, and a site that copied it (joecms.it) showed the Guide's index instead of every chapter. Now the example uses cm::getInstance(), and the manual warns that the residue arrives in lowercase (ffCommon_url_normalize()). (manual 01 §4)

1.6.2

28 Sept 2026

Fixed 2 entries

  • media.<domain> images with no cached copy: no more 500s or truncated redirects. When the copy in cache/.thumbs/ is missing and the original exists in uploads/ with the same path, Apache now serves it, in ranges too as videos on iPhone require; resized versions are still generated by cm/error.php and ffMedia. This holds for the .htaccess the wizard writes for new installations (jc_write_htaccess() in install/lib.php) and for the old installer's template (conf/gallery/install/.htaccess-cms.tpl). The wizard and the repo's .htaccess also had the front controller's host condition unanchored: it matched media. too and sent every missing copy into a 500 (exceeded the limit of 10 internal redirects). ffMedia::process() no longer offers redirects to copies that don't exist: for originals it couldn't copy (seen with JPGs and videos) it answered with a permanent 301 to a truncated path (/prodotto-v2/intro.mp4 → tto-v2/intro.mp4), now with a 404. Sites already installed must be updated by hand: their .htaccess doesn't travel with the deploy. (ff/classes/ffMedia.php, manual 11 §5)
  • bin/deploy.sh --svuota-cache no longer deletes cache/.thumbs/, the copies served by media.. Emptying them all at once, on a site whose Rewrite Base also applied to media., sent every image into a 500 (grandchef, 28/9/2026). (manual 14 §4)

1.6.1

27 Sept 2026

Fixed 2 entries

  • Backend on PHP 8: six pages no longer fail. Found by the crawler that walks through frontend and backend on MySQL 8.4; they were already there in 1.5.x.
    • Utility → Sitemap: Call to undefined function cache_get_settings(). sitemap.php used the functions of cache.php without including it, and in the kernel flow only router.php loads them, which the backend never goes through: now it includes them itself. The menu entry pointed to /admin/utility/sitemap, an address with no page that the …/sitemap routing rule sends to the section generator: now it opens the site's sitemap, /sitemap.xml. (library/gallery/system/sitemap.php, conf/contents/admin/mod_restricted.xml)
    • Google Maps and maps module configuration: Undefined constant "TOP_CENTER". The control positions (TOP_CENTER, SMALL, HORIZONTAL_BAR…) were undefined constants, which PHP 7 turned into the string of their own name: now they are strings, with the same value as before. (conf/gallery/services/google.maps/config/index.php, conf/gallery/modules/maps/config/modify.php)
    • Domain editing, and every currency field without decimals: Unsupported operand types: string / int. The empty decimal part of an amount such as 5 was divided as a string: now it is converted to a number, in every language format. (ff/classes/ffData/locale/FormsLocale_*.php)
    • Groups (/restricted/groups): "Cannot determine order field!". The default sorting was "level DESC", but the grid wants the name of the field; the direction now lives on the level field. (conf/gallery/manage/groups/index.php)
    • Component examples (/admin/doc/record): "CM: Unable to find Widget". Removed the two examples with ckuploadify, which depends on CKFinder and is not in the backend theme; the "uploadifive" and "kcuploadifive" examples now use those widgets instead of their twins.
    • Import (/admin/configuration/import): the menu links came out with raw {import_path} and {_import_…}, because that content does not go through the template. Now path and labels are resolved in PHP. (conf/gallery/import/index.php)
  • System emails: no more Undefined constant "EMAIL_DEBUG" fatal. The old installer's config defined it, the wizard's does not, and email_system() reads it: sending service, notifications on content insert and update, email previews, registration module. Now it has an empty default. (conf/gallery/config.php)

1.6.0

27 Sept 2026 DB schema → 4

Fixed 7 entries

  • MySQL 8, Aiven, strict MariaDB: the CMS runs with the default sql_mode of modern servers (ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, NO_ZERO_DATE), without relaxing it. Tested with installation, frontend, back office, registration and saves on MySQL 8.4 (also with Aiven's sql_mode) and MariaDB 12. (manual 07 §1)
    • Queries with disallowed GROUP BY or DISTINCT (#1055, #3065) rewritten in about thirty files: layout modules and permissions, sections, operations menu, back-office grids, APIs, invoices and payments. Where "the first row per group" was meant, the choice is now explicit (in PHP, ROW_NUMBER() or MIN(ID)), whereas before it depended on the server. The checks on invoices without payments grouped them all into one.
    • Schema: explicit DEFAULT on all NOT NULL columns (error #1364 "Field doesn't have a default value"); nullable date columns, and empty dates written as NULL instead of '0000-00-00', which is rejected even just in a comparison.
    • Writes: ffDB_Sql::toSqlColumn() adapts the empty value to the column type (0 for numeric columns, NULL for dates) in ffRecord, ffDetails, Storage and in hand-written queries (error #1366 "Incorrect integer value: ''"). INSERTs with '' on the auto-increment key write NULL.
    • Aiven's ANSI dialect: with PIPES_AS_CONCAT, || concatenates instead of doing OR, without raising an error. The only || in a query, the shipping status of the operations API, is now OR. (conf/gallery/api/get_operation.php)
  • Database port: the installer asked for it but didn't write it, and ffDB_Sql didn't pass it to mysqli, so a database on a non-standard port (Aiven) couldn't connect. Now the wizard writes FF_DATABASE_PORT and the driver also accepts host:porta.
  • PHP 8: no more fatal sem_get(): Argument #1 ($key) must be of type int on cached pages (e.g. /login): the cache semaphore key is always an integer (library/gallery/system/cache.php, vendor/wolfgan/cache/services/sem.php).
  • Payments: the Stripe driver no longer ends in a fatal error without a key or without network. Since 1.5.1 paymentStripe called an errore() method that didn't exist: without a secret key, or with the network down, instead of the error result you got Call to undefined method. Now the error result has the same shape as success (ok set to false, error, error_code). Also, an invoice counts as paid even when Stripe doesn't send the paid field, which recent APIs no longer have: what counts is status equal to paid. (library/payment/services/stripe.php)
  • Multilingual sites: the canonical of English pages pointed to the Italian ones. For a file page in a non-default language set_header_page() used the canonical path on disk: /en/contact declared /contattaci, /en declared /, and Google never indexed the translated version. Now it goes through content_i18n_url(); vgallery pages stay as before. (library/gallery/common/set_header_page.php, manual 12 §2)
  • Registration: the marketing consent is no longer lost, and there's an event after the account. The widget had always sent the newsletter checkbox, but jc_registration_submit() didn't store it. Now, once the account is created, Auth::doEvent("on_registration_done", $account, $dati) fires with ID_user, ID_anagraph, email and the consents (newsletter, privacy), language, IP and browser: the project decides where to write them. With no listeners nothing changes. (modules/auth/contents/registration/index.php, manual 08 §5)
  • ?__nocache__ on a page never cached gave a 500: the file manager's delete() on a file that doesn't exist yet passed null to array_diff_key(). (vendor/wolfgan/filemanager/services/fs_php.php)

Added 2 entries

  • bin/db-allinea-schema.php: brings an already installed database to schema 4 (explicit defaults, nullable dates, zero dates → NULL) by reading the actual columns, without changing any type. Dry run by default, --vai to execute, --config <file> for another config; idempotent. If the connection drops midway (errors 2006, 2013) it reconnects and retries; if it doesn't come back it stops at once, and when run again it resumes from where it got to.
  • Multilingual sitemap. With more than one active language every file page and the home page appear once per language, with the slug from the contents/i18n.php manifest and <xhtml:link rel="alternate" hreflang>; the addresses match the canonicals. With a single language nothing changes. (modules/cms-common/models/Sitemap.php, GUIDA_SITEMAP.md)

Security 1 entry

  • Sign-in, registration, activation, recovery and logout: the return only to a path of the site. ?redirect= and ?ret_url= come from the page address and ended up unchecked in the response and in the templates: /login?redirect=https://altro.sito sent whoever had just signed in elsewhere (open redirect), ?redirect=javascript:… ran code in the login page, and ret_url went raw into an onclick (reflected XSS; the same with redirect in activation and recovery). New Auth::redirectLocale(): only a path that starts with a slash passes (not //, not /\), without spaces, control characters, quotes, < > or backslashes; otherwise the widget behaves as if there were no parameter. The login and logout scripts apply the same rule in the browser. Anyone who redirected after sign-in to an absolute address, even on their own domain, must pass just the path. Stricter than pm_safe_dest() (library/security, not loaded yet) because here the value also ends up in attributes and JavaScript strings. (vendor/wolfgan/auth/Auth.php, vendor/wolfgan/auth/widgets/{login,registration,activation,recover}/index.php, widgets/login/script.js, widgets/logout/script.js, manual 08 §5)

Schema 1 entry

  • 4: DEFAULT on every NOT NULL column, nullable date columns with default NULL, zero dates converted to NULL. On an existing site it's applied with bin/db-allinea-schema.php, before uploading the 1.6.0 code (see the top of this section).

1.5.2

25 Sept 2026

Fixed 2 entries

  • bin/deploy.sh always ships executable. If the checkout the package was built from had lost the execute bit, the installed site answered permission denied to ./bin/deploy.sh. Now build-zip.sh sets it to 0755 before compressing and checks it inside the ZIP; the manual explains how to restore it on a site that is already installed. (build-zip.sh, docs/manuale/14-ambienti-e-deploy.md)
  • Payments: the Stripe driver no longer depends on GDay constants. Stripe dates were converted to the GDAY_FUSO time zone, a constant that only exists in that project: everywhere else it silently fell back to PHP's time zone. They now go through Payment::fuso(), which uses the site's time zone (TIMEZONE), then PHP's, and on an invalid value falls back to UTC without exceptions. References to GDay have also been removed from the driver's comments. (library/payment/Payment.php, library/payment/services/stripe.php, manual 10 §2)

1.5.1

25 Sept 2026

Added 1 entry

  • Payments: a single hub, gateways as drivers. library/payment/Payment.php declares what taking a payment means (opening a session, reading its status back, refunding, verifying a webhook signature) without knowing who does it; the gateway is a driver in library/payment/services/<name>.php, loaded by the hub (autoload.php needs a single case). First driver: Stripe, one-off and recurring. Keys are entered from the Services area (conf/gallery/services/payment.stripe/), and the live environment only switches on with an sk_live_ / rk_live_ key: whoever forgets to change the key doesn't take real money by mistake. Products, credits and receipts stay in the site's module. (manual 10 §2)

Fixed 1 entry

  • Fatal error on the home page for signed-in users (since 1.3.1). On a multilingual site, a signed-in user opening a URL without a language prefix (the home page, for instance) got a blank page: Undefined constant "FF_PHP_EXT". Preferred-language resolution runs in cmsKernel::run(), before the framework is loaded, and to read the preference from the profile it recomputed the language list with get_locale(), which can't work at that point. The list the kernel already provides is now passed to the profile read and write, and reused by the other functions. If the framework isn't ready, get_locale() isn't called. Anonymous visitors are not affected. (library/gallery/common/language_preference.php)

1.5.0

25 Sept 2026

Added 1 entry

  • Multilingual installer (Italian, English, Spanish, French). The wizard opens in the browser's language (English if it isn't one of the four) and has a language selector at the top right. Every text is translated: steps, fields, hints, error messages (database, SMTP, icons), the test email, the final page and the installer-removal page. The chosen language becomes the site's default language, and can still be changed in the Languages step. The proposed time zone and country follow the language. Dictionary in install/i18n.php; the choice lives in the session and in the jc_install_lang cookie. (manual 14 §3)

Fixed 3 entries

  • Token access: no more fatal error. Token verification queried an external service of the original installation and used the PM_CLIENT_* constants, which aren't defined on JoeCMS: the request stopped with a fatal error. The token is now verified against the site's database. A token that doesn't exist is rejected, which didn't happen before: read() returns an empty array, which ended up in the success branch. New tokens get a real expiry (now plus the lifetime): before, only the lifetime was saved, i.e. a date in 1970. (vendor/wolfgan/auth/services/token.php)
  • Activation and password recovery without a configured callback. The activation and recover widgets called the project's callback without checking it existed: if the project didn't define one, the final step failed. The callback is now optional, as it already was in login and registration. (vendor/wolfgan/auth/widgets/activation/index.php, vendor/wolfgan/auth/widgets/recover/index.php)
  • Personal records: no TypeError on an unexpected read result. Anagraph counted the result before checking it was an array; with PHP 8 a non-array result throws a TypeError. (vendor/hcore/anagraph/Anagraph.php)

1.4.2

23 Sept 2026

Fixed 2 entries

  • Email: inline images and attachments become links. Some relays (JoeSMTP, Aruba) reject the whole message if it contains an attachment part — 550 … Attachments are not supported — and cid: images are attachment parts in every respect: emails with the logo weren't going out. Mailer now rewrites cid: as absolute URLs and appends attachments to the body as a list of links (uploads go through CM_SHOWFILES). When the address can't be derived — file outside the docroot, WWW_LINK_ABSOLUTE not defined — the previous behaviour stays, so no project loses images or attachments over a path that doesn't exist. You can revert with MAILER_EMBED_IMAGES and MAILER_EMBED_ATTACHMENTS set to true in the config. (vendor/wolfgan/mailer/Mailer.php, manual 06 §2)
  • Account activation page: error even when the email was sent. The 1.4.0 fix read the result of Notifier::send() as-is, but with a single notification service configured that method returns true when sending succeeds: true ended up in $res["error"] and /attivazione answered 500, with an error with no text, precisely in the good case — the code had been sent. The result now goes through a single point (Auth::erroreInvio(), vendor/wolfgan/auth/Auth.php): it's an error only if it's a non-empty string, or the error key of the array returned when there is more than one service. Applies to both the email and the SMS branch.

Security 1 entry

  • The activation code no longer goes back to the browser. The send-code request (the POST of the activation widget) returned to the client, inside the JSON response, the 6-digit code just emailed: reading it in the developer tools was enough to activate an account without access to the mailbox. The field is now emptied before the response (vendor/wolfgan/auth/widgets/activation/index.php); the widget didn't use it — it takes the code from the fields filled in by whoever received the email — so the page behaves as before. (manual 08 §5)

1.4.1

23 Sept 2026

Fixed 1 entry

  • Account activation page: the button didn't respond on sites that render the widget in their own public shell instead of the CMS layout. The widget script called the theme loader (showLoader), which doesn't exist there: the JS error stopped everything before the server call, and nothing appeared on the page. The loader is now used only if present (vendor/wolfgan/auth/widgets/activation/script.js). In the same pass, a network or server error no longer leaves the page half-done: the button becomes active again and the error message appears.

1.4.0

23 Sept 2026

Added 1 entry

  • Public API: extra endpoints without touching the core, and sub-paths. The whitelist in api/1.0/index.php is extended with the JC_API_ENDPOINTS constant (comma-separated list) in the installation config; auth is always there. Before, every project had to edit the front controller by hand, and the name of a vertical endpoint ended up inside the CMS. api/1.0/.htaccess also routes /api/1.0/<ep>/<resource>/… and passes the rest of the path in _path: before, the path stopped at the first segment, and an endpoint with several resources had to put the "what" in the body, which makes no sense for a GET. Existing endpoints don't change.

Fixed 1 entry

  • Account activation page: when the email with the code didn't go out, /attivazione answered 500 with a blank page instead of saying what went wrong. The result of Notifier::send() was read as an array, but it's a string when sending fails (vendor/wolfgan/auth/Auth.php). The sending error now appears on the page — and the real cause, to be fixed on the SMTP side, stays visible too.

1.3.2

21 Sept 2026

Fixed 2 entries

  • Installer, SMTP test email: with port 587 it always failed (and the installed site sent no mail) because encryption was fixed to SSL. Now it's selectable (SSL/TLS, STARTTLS, none), the password isn't lost after the test and the error shows the server's response (install/index.php, install/lib.php).
  • Installer, Enter key in the Application step: pressed in a field it sent the test email instead of moving on; now it's the same as "Continue".

1.3.1

21 Sept 2026

Added 5 entries

  • Deploy of the active branch to production: bin/deploy.sh (+ bin/deploy.conf.example, bin/.htaccess). Uploads over SSH the HEAD of the git branch you're on — never uncommitted files — and only those changed since the last deploy, which the server remembers in $HOME/.joecms-deploy-rev-<site> (in the SSH user's home, not the docroot: it must not be reachable from the web; the site-name suffix is for when several installations live on the same server under the same user). Replaces single-file uploads, which leave a non-reproducible mix of versions in production.
    • controlla runs server diagnostics: user, docroot found automatically, PHP binaries with mysqli/mbstring, permissions of cache/ and uploads/, recorded commit.
    • Without --vai it's a dry run that doesn't touch the server. Then --completo, --rimuovi, --svuota-cache, --da <sha>, --solo <path>, --forza, --niente-smoke.
    • It won't start if you log in as root without DEPLOY_CHOWN: files would stay owned by root and with suexec or suPHP the site would answer 500 on everything.
    • It never uploads config.remote.php/config.local.php, the root .htaccess (in production it's the one written by the installer with the real domain), install/ (already removed by install/cleanup.php at the end of installation), database.sql, cache/ or working material. When one of these changes it says so in the summary — docs/sql/ migrations to apply before the code, new define()s in config.remote.php.dist, modified .htaccess — instead of uploading it silently.
    • End-of-deploy HTTP smoke test from the deployer's computer, with one path per language on a multilingual site: it's the check that catches the language left behind. If the project has tests/run.php with tests/smoke.config.php, it uses that suite.
    • Configuration lives in bin/deploy.conf, outside git because it's per-installation.
    • Several environments per site (production, staging): --ambiente <name> reads bin/deploy.<name>.conf instead of bin/deploy.conf, and stops if the file is missing instead of falling back to the default environment. bin/.htaccess (Require all denied) keeps the folder off the web.
  • User's preferred language, for pages and communications. library/gallery/common/language_preference.php resolves the language of every public request and remembers the choice in the cookie and, for authenticated users, on the profile (access_users.locale/ID_lang, anagraph.ID_lang). Order: explicit ?lang= → URL prefix → profile → cookie → Accept-Language (root only, first visit) → default. The kernel calls it after Auth::check(), so it also applies to non-cacheable pages; cache_check_lang() now defers to it.
    • The language switcher always links with ?lang=: it's the only signal that also updates the profile. Opening an /en/… link only changes the cookie.
    • Emails and notifications go out in the recipient's language, even from cron and async jobs: process_mail() derives it from the address if the caller doesn't pass a "lang"; Notifier sends once per language; new Mailer::setLang().
    • Helpers for project code: language_pref_for_user(), language_pref_for_email().
  • SMS via JoeSMTP (service sms.joesmtp, driver vendor/hcore/notifier/services/sms_joesmtp.php): Notifier SMS can go out through JoeSMTP's transactional API (/api/1.0/sms-send, the project's client credentials). If both JoeSMTP and Twilio are configured, JoeSMTP is used. Also configurable from the wizard, Services step.
  • Second factor at login (2FA) via email or SMS, enabled with AUTH_2FA in config.remote.php (the installer writes it empty = off). The login widget asks for the code by itself. See manual 08 §5bis.
  • Per-user push: the browser links the OneSignal subscription to the logged-in user (OneSignal.login, ID read from /OneSignalIdentity, never written into cached HTML) and the server reaches it by user ID. New api_key field in the notification.onesignal service.

Fixed 15 entries

  • Fatal error on every URL containing the word source or destination (e.g. /esperto-risponde/sources/nginx.conf, typical of automated scans). The kernel merged the route declared by $schema["page"][...]["router"] into its own table with array_replace(): the keys source and destination became two routes, i.e. two literal unanchored regexps that matched those URLs and sent Cms::execute() to require() the regexp itself. Now mergePageRouter() (vendor/wolfgan/cms/services/kernel.php) merges only the regexp => destination map form; the {source, destination} form remains the data the kernel uses to recognise the page (manual 01 §2).
  • 500 on /INSTALL.md (Sentry urbanrunners): the installer route (^/install(.*) → /conf/gallery/install/$1), which for the service/updater groups is executed by library/gallery/system/init.php, reached require() with $1 not substituted. And since the kernel's route matching is case-insensitive, a documentation URL tried by a crawler ended up there too. It now answers 404.
  • As a safety net on the same path: Cms::execute() answers 404 — instead of dying with a fatal error — if the destination is not an existing file inside the document root, and cmsRouter::run() also substitutes rule groups in "file" destinations, rejecting those where an unresolved $1 remains or where the captured group contains .., a null byte or a protocol scheme.
  • Request stuck until max_execution_time on URLs with a relative path (e.g. /srv/request.tar, which reaches the kernel as .tar). In get_page_properties() (vendor/wolfgan/cms/services/kernel.php) the folder walk-up only exited on reaching /: on a path without a leading slash dirname() returns . forever and the loop never ended, tying up a PHP process for 200 seconds — with enough such requests, the site hangs by itself. It now also exits when dirname() stops shortening the path.
  • Call to undefined function check_function() in reserved areas with their own path (/gestione/… and similar, which aren't in the list of prefixes skipped by the language resolver). language_pref_langs() (library/gallery/common/language_preference.php) used check_function(), defined in library/gallery/common.php: the kernel calls the resolver right after Auth::check(), when that file isn't loaded yet. It now goes through language_pref_has_locale(), which loads get_locale() itself when the CMS autoload isn't there yet (manual 12 §6).
  • Blank home page on an unexpected host: set_header_page() read WWW_LINK as a bare constant to build the title tag. If hook.php didn't define it — old installations defined it only inside a switch ($_SERVER["HTTP_HOST"]), so never on a host with www., with a port or behind a proxy — on PHP 8 it was a fatal Error and the site answered a blank page. The comparison now goes through set_header_page_is_canonical_host(), tolerant of www. and port, and without the constant assumes the canonical domain. The hook.php constants were already defined in every case in this version: the fix protects installations with a hook.php older than the code (manual 14 §3).
  • Registration always saved Italian as the language in anagraph (ID_lang = 1), even for people signing up from /en/. The migration docs/sql/2026-09_lingua-profili-allineamento.sql repairs existing profiles. It only touches data: it doesn't go into database.sql and the schema stays at 3.
  • The "manual needs updating" check (.githooks/manuale-check.sh) had three blind spots, which surfaced with the language work: it ignored a path cited with a line number, discarded docs/sql/ migrations before sending them to chapter 07, and flagged eight chapters on every hook.php change. It now tolerates :line, routes migrations and for hook.php flags only chapters naming a touched function. New --commit <sha> mode to check a commit already made.
  • The manual pre-commit now blocks once instead of warning: Sourcetree shows a hook's output only when it fails, so nobody saw the warning. If the manual doesn't need changing, just repeat the same commit. MANUALE_WARN_ONLY=1 goes back to warning only; MANUALE_STRICT no longer exists.
  • ffDb_Sql in ff/classes: mysqli_report(MYSQLI_REPORT_OFF) in connect(), as already in the copy in vendor/phpformsframework/ffDb_Sql. Since PHP 8.1 mysqli throws mysqli_sql_exception instead of returning false, and the driver (which does @mysqli_*() then checks errno) didn't catch it. Pages always load the vendor copy, but this one is loaded by direct path by the installer (conf/gallery/install/common.php): on PHP 8.1+ the wizard ended in a fatal error at the first SQL error instead of showing the message.
  • Web push: notification.onesignal service moved to Web SDK v16. It loaded the v15 stub from a non-existent file (/themes/site/javascript/OneSignalSDK.min.js), so web push was off on every site. It now uses OneSignalSDK.page.js v16 from the CDN; the root worker /OneSignalSDKWorker.js (and the old /OneSignalSDKUpdaterWorker.js, for those who subscribed with v15) imports OneSignalSDK.sw.js v16. Prompt and bell are configured from the OneSignal dashboard; the page language is passed to OneSignal for multilingual sends. Without an App ID the service injects nothing. Removed gcm_sender_id from the manifest and an old site's excluded paths.
  • Notifier push and SMS didn't work, never used until now. The OneSignal driver hit a fatal error on the first send, the Twilio one made no call at all, and send() with a string message hit a TypeError on PHP 8. Rewritten: OneSignal on the current REST (api.onesignal.com, Authorization: Key), Twilio on REST without the SDK, certificate always verified, result in the return of send() and failures in the notifier_error log.
  • Ineffective login 2FA: the session was opened before sending the code, which was never verified, and was the same for all users within the same minute. The code is now asked before any session or token, is per user and has resend and attempt limits.
  • Notifier: sendMail() passed arguments in the wrong order (actions ended up in the title); getStorage() called setConfig() with one argument (ArgumentCountError on PHP 8, in-app notifications included); a phone number without + was taken for a user ID (Notifier::normalizeTel()).
  • Wizard: Twilio asked only for SID and token, but it can't send without a sender; it now asks for from too.

Removed 3 entries

  • Dead copies of Notifier, Mailer and Storage in library/classes/ and library/gallery/classes/: the CMS only loads those in vendor/. In autoload.php, the block pointing to library/gallery/models/<class>, a non-existent folder.
  • Public test script /api/notifier (conf/gallery/api/notifier/).
  • sendSMSTwilio() and the empty constants MOD_SHARE_TWILIO_* in hook.php, never used: SMS go through Notifier with the credentials from the Services area.

Security 2 entries

  • Removed the server-side connectors of three vulnerable libraries (ported from GDay in commit b50933a5, which by mistake carries the message of that site's data model):
    • themes/library/ckfinder/: the PHP connector (core/connector/php/, ckfinder.php, config.php, plugins). The JavaScript files remain: the ckfinder and ckuploadify widgets of ffField (default and restricted themes) no longer have a backend and file uploads going through them don't work. Anyone using them must switch to kcfinder/kcuploadify or the CMS upload;
    • themes/library/tiny_mce/plugins/filemanager/: the MoxieCode file manager, with example authenticators for Joomla, Mambo, PHPNuke, WordPress and an auth_example.php reachable from the web;
    • themes/library/highcharts/exporting-server/: the chart export server.
  • library/security/bootstrap.php (new): helpers for untrusted input reflected in output — pm_safe_dest() (open redirect), pm_js_value()/pm_js_attr() (XSS in JavaScript), pm_html(), pm_safe_token(). Not loaded by anything yet: the hook in hook.php and the places using it come with the next change. ⚠️ Before loading it, the allowed-domain list of pm_redirect_allowed_domains() must be made configurable — today it contains paginemediche's domains: an absolute redirect to the site's own domain would be discarded (relative paths pass).

Docs 3 entries

  • Manual aligned with the work on notifications, SMS and 2FA: 06 rewritten in sections 1, 3 and 4 (Notifier drivers, services and fields, OneSignal v16, JoeSMTP), 08 §5bis (second factor), 10 and the capability map.
  • Manual aligned with the language work: 12 §Multilingual (resolver and resolution order), 06 §2 (recipient's language), 07 (preference columns, data-only migrations), 01, 08, index. 14: map rules and limits of the check.
  • Manual 14 §4 rewritten: the "deploy without ZIP" section described the manual procedure (listing paths and uploading them by hand), it now documents bin/deploy.sh — configuration, options, what doesn't travel and why, cache, smoke test, what stays manual. Go-live checklist updated accordingly.

1.3.0

18 Sept 2026

Added 2 entries

  • The manual (docs/manuale/) ships in the ZIP (build-zip.sh), as a snapshot of the version: every chapter carries the package version and date at the top, docs/manuale/VERSIONE.txt states which build it comes from, the files are read-only. On the installed site the manual of the installed version stays even when the CMS moves on; the next update brings its own. A docs/.htaccess (Require all denied) keeps it off the web: it describes the platform's internals and is read from the ZIP or via FTP/panel.
  • Automatic "manual needs updating" check, only in the main repository (.githooks/manuale-check.sh). It compares modified files with the paths each chapter cites and flags chapters touched but not updated: the file → chapter map is derived from the manual itself, with no lists to maintain. It fires at the end of a Claude Code turn (Stop hook in .claude/settings.json, which has the chapter updated before closing) and at commit (git pre-commit hook, active with git config core.hooksPath .githooks; warns without blocking, unless MANUALE_STRICT=1). .githooks/ and .claude/ don't go into the package.

Docs 1 entry

  • docs/manuale/14-ambienti-e-deploy.md §5: the manual in the package, the immutable snapshot, the update check; go-live checklist with the manual item.

1.2.2

18 Sept 2026

Security 1 entry

  • Arbitrary PHP code execution from place-search parameters (ffl, pci, pcn, ppi, ppn, pps, pri, prn, psi, psn, pss). vgCommon::getRequest() wrote the incoming request value into an eval() — ?ffl=<php code> on any primary public page executed that code, without authentication (the parameters are enabled by the kernel on every non-reserved primary page). The destination path (["filter"]["place"]["city"]["ID"]) is now resolved by keys with preg_match_all and the assignment is by reference: the value is never interpreted as code, and only scalar values are accepted. Side effect: place search with text values (?pcn=roma) works again — under PHP 8 the eval failed with Error: Undefined constant "roma".

Fixed 2 entries

  • 500 on malformed URLs built by bots (TypeError: urlencode(): Argument #1 ($string) must be of type string, array given, vendor/wolfgan/vgCommon.php). When a scanner sent a parameter with an array value and a "dirty" name (e.g. ?<?php $env[...]=...), building the query of discarded parameters called urlencode() on an array: under PHP 8 that's fatal, so the page answered 500 and the error landed in Sentry. Array values are now serialised with http_build_query().
  • Blank site (500) right after installation, with Error: Undefined constant "DOMAIN_PROD". Domain constants were defined only if the request host matched exactly the domain written in the wizard: a www. difference was enough for every public page to hit a fatal error. hook.php now recognises the domain ignoring www. and port, and defines DOMAIN_PROD, WWW_LINK, WWW_LINK_ABSOLUTE and LOCAL_DOMAIN regardless; the rule setting noindex outside production (library/gallery/common/set_header_page.php) no longer reads bare constants. As a consequence, a staging site served on a host other than the declared one is now really marked noindex,follow.

Changed 1 entry

  • The package no longer contains shell scripts: build-zip.sh (a build tool, useless on the server because it works on git ls-files) and leftover .sh files inside vendor/, library/ and themes/library/ are excluded from the ZIP. An executable .sh in the document root was just extra attack surface. The build flags it in the final check ("shell scripts in the package").

Docs 1 entry

  • New platform manual in docs/manuale/ (15 documents): what the system allows and how it's done, chapter by chapter — request lifecycle and routing, pages/templates/applets, HTTP services and webhooks, internal and public API, cron/jobs/workers, email-notifications-SMS-push, data and content model, auth and permissions, backend and ffGrid/ffRecord sections, modules and third-party services, media and files, cache, observability and CLI, environments and deploy. The index (docs/manuale/00-INDICE.md) contains a capability map with the status of each (in production / to configure / upstream scaffolding) and the list of non-negotiable rules. It covers subsystems never documented in the repo before: the /srv/request service bus, the Jobs class (queue and async calls), Notifier (notifications, OneSignal push, Twilio SMS), multi-driver Storage, showfiles and image modes, $schema["request"] as a parameter whitelist, router walk-up instead of 404. Part of the content was recovered from sister projects on the same stack (JoeSING, JoeQUIZ, JoeSMTP), where general CMS mechanisms were documented only in the project that first used them.

1.2.1

16 Sept 2026

Fixed 1 entry

  • Every page answered 500 on a fresh installation: Error: Undefined constant "FF_PHP_EXT" (index.php, library/gallery/common/content_i18n.php). Loading the localised-slug manifest used FF_PHP_EXT, a constant defined by ff/main.php — which isn't loaded yet at that point, because the framework comes in later from cm/main.php. In development the bug stayed invisible: PHP's built-in server goes through router.php, which loads ff/main.php before index.php. Under Apache/PHP-FPM, instead, index.php is the first file executed and in PHP 8 an undefined constant is a fatal error. The bootstrap now uses __DIR__ and the extension written out, without depending on framework constants.

1.2.0

16 Sept 2026

Added 7 entries

  • Site icon asked at installation, and every format generated from that one image (install/icons.php, new; Appearance step of the wizard). Until now whoever installed JoeCMS kept the JoeCMS favicon until they replaced half a dozen files by hand, each with its own size and name. Now you upload a square image (PNG, JPEG, GIF, WebP, or SVG if the server has Imagick) and the installer writes: favicon.ico — a real multi-size 16/32/48 ICO, written in PHP without dependencies — favicon.png, favicon-16x16.png, favicon-32x32.png, apple-touch-icon.png (180×180 on a solid background, because iOS renders transparency as black), the PWA set iconpreview-NN-NN.png from 36 to 512 px in /media-resource/, the maskable icon for Android, the Windows tiles mstile-*.png and the original in uploads/loghi/icona-sito.png to regenerate later. favicon.svg is rewritten wrapping the new PNG: otherwise it would win, since browsers prefer vector.
  • manifest.json and browserconfig.xml created during installation, filled with the data the wizard already collected: app name and short name, description, default language, start_url/scope accounting for the site path, colours and the list of only the icons actually on disk. No need to upload them: a freshly installed site is already installable as an app and shows the right tile on Windows. If no image is uploaded the set is still generated from the package's JoeCMS icon, so the manifest never points to non-existent files (the case of the old site.webmanifest, which cited an /icon-192.png that never existed). The theme links manifest.json when present, and adds the theme-color, msapplication-config and msapplication-TileColor meta tags.
  • App theme colour and background colour chosen in the Appearance step, with fields that can be left empty: in that case the theme colour is derived from the image (dominant colour, discarding transparency, whites and blacks). They end up in manifest.json, browserconfig.xml and the constants JC_THEME_COLOR/JC_BG_COLOR in config.remote.php.
  • Branded 404 and 500 error pages (cm/errori.php, cm/extras/404.html, cm/extras/500.html). Before, the CMS answered badly both times it matters: the kernel 404 was an <h1> with no page around it, Apache's (ErrorDocument → cm/error.php) came out with an empty body, and a fatal error — with display_errors at 0, as it should be in production — gave a blank page. The three doors now converge on a single function, cms_error_document(), and the pages are JoeCMS cards with inline CSS: no network dependency, because an error page must appear even when everything else is down. A site starting from JoeCMS has them straight away, and replaces them by putting its own in conf/cm/extras/ (that path always wins over cm/extras/).
  • Fatal errors and uncaught exceptions become a readable 500 (cms_error_handler_register(), hooked in index.php right after CMS_START). The page never shows message, file or line: it shows a ten-character reference that also ends up in error_log next to the real error and the URL, so a report can be found with a grep. If output was buffered it's discarded (no truncated page); if it was already sent nothing is printed. Requests under /srv/, /rt/, /api/ and XHRs receive JSON, not HTML. With __debug__ or display_errors on the system steps aside: in development the error must be read. Registered before Sentry on purpose: that way Sentry wraps our handlers instead of replacing them, and the shutdown handler doesn't call exit so as not to prevent the event from being sent.
  • This changelog, reconstructed from git and work sessions, and shipped inside the package: CHANGELOG.md is the only markdown that survives build-zip.sh's exclusions, so whoever installs sees what changes between versions.
  • build-zip.sh warns if the section for the version being built is missing and checks at the end of the build that the changelog made it into the zip.

Fixed 7 entries

  • Session cookie: duplicate cookie with the same name, login impossible (vendor/wolfgan/auth/services/session.php). session_start() was called before setting the cookie parameters, so PHP emitted a host-only cookie without flags; right after, the application emitted a second one with the same name but Domain=.domain. The browser kept both and sent them together: only one survived in $_COOKIE, often the wrong one, and the session was always invalid — the only remedy was deleting cookies by hand. Parameters are now set once before opening the session, and a single cookie is emitted.
  • Logout didn't delete cookies: cookie_destroy() used lifetime (0) as expiry, i.e. it wrote a session cookie instead of deleting it, and only tried the HTTP_HOST domain, which doesn't touch host-only cookies. Expiry is now in the past and both forms are deleted.
  • secure is no longer hard-wired to true: it's derived from the connection (MOD_AUTH_COOKIE_SECURE to force it). Over HTTP the browser discarded the cookie and login didn't hold in development.
  • SameSite goes from None to Lax (MOD_AUTH_COOKIE_SAMESITE to go back to None, still needed only if the site is embedded in a third-party iframe). None exposed the session cookie to every cross-site request.
  • No Domain attribute on localhost and IP addresses: browsers discard the cookie and the session didn't hold in development.
  • session_regenerate_id(true) was invoked after session_destroy(), with no active session: it regenerated nothing. It now comes after session_start().
  • build-zip.sh: the markdown exclusion was case-sensitive and let the vendors' .MD files through (e.g. library/algoliasearch-client/DOCKER_README.MD).

Changed 1 entry

  • SESSION_NAME is derived from the domain, no longer fixed: PHPSESS_[third][second][YYYYMM], with the third level omitted when it's www (quiz.esempio.com → PHPSESS_quizesempio202609). Needed because two installations under the same parent domain share cookies: with the same name the sessions overwrite each other. Year and month are those of installation and stay frozen in the constant — recomputing them on every request would log everyone out at every month change. New function jc_session_name() in install/lib.php; the old installer uses installer_session_name() in conf/gallery/install/common.php.

1.1.0

29 Aug 2026 DB schema → 3

Added 5 entries

  • build-zip.sh — build of the installation package (joecms-<version>.zip, ~77 MB). Packages the files tracked by git in their working-tree state, excludes environment configs (the .dist ones stay), the development .htaccess, root *.md files, source maps and vendors' test/doc/example directories; empties cache/ and keeps only loghi in uploads/. It checks by itself that no secrets end up in the package and that seed and installer are present.
  • Sitemap — its own generator (modules/cms-common/models/Sitemap.php, conf/gallery/sitemap/, per-site configuration in themes/site/conf/sitemap.php). Documented in GUIDA_SITEMAP.md.
  • Admin tools as a service (conf/gallery/services/admin.tools/): the admin bar and alignment guides become two switches in /restricted/services/admin.tools, off by default and per domain.
  • CMS guide generated by the installer (install/guide.php), produced in every active language of the installation.
  • Documentation: PANORAMICA_JOECMS.md (how it's built and what's still open), IGIENE_SEGRETI.md, GUIDA_SITEMAP.md.

Changed 4 entries

  • Secrets hygiene: environment configs (config.local.php, config.remote*.php) have been pulled from the repository; only config.remote.php.dist stays in git. The installer regenerates the real config at first start, with chmod 0640.
  • Generated robots.txt: /search/, /area-utente/, /srv/ also excluded; confirmed the rule for AI crawlers (indexing yes, training no).
  • Multilingual content (content_i18n.php, process/language.php), JS-side admin toolbar, admin frame, site theme typography.
  • Compatibility patches on vendors: google-api-php-client, wolfgan/* (Auth, Storage, Filemanager, vgCommon), ffDb_Sql_mysqli, ffDb_MongoDB.

Schema 1 entry

  • JC_SCHEMA_VERSION 2 → 3 (changes to database.sql).

1.0.6

29 Jul 2026

Changed 4 entries

  • VGallery Next: node editor rewritten and lightened (conf/gallery/manage/vgallery-next/), form contract (FormContract) extended; writing still goes through the original path via $_REQUEST.
  • vgnext theme: dedicated theme_settings.xml and form stylesheet (vgnext-form.css).
  • Language engine (process/language.php) and system cache (system/cache.php) revised; hooked in system/init.php.
  • Site header and installer steps (install/index.php, view.php).

1.0.5

28 Jul 2026

Added 2 entries

  • Internal CMS guide produced at the end of installation.
  • Per-domain settings: options are no longer global but tied to the domain being served.

1.0.3

27 Jul 2026

Added 7 entries

  • User and group management in /restricted/users and /restricted/groups (previously empty pages): lists and edit forms on access_users / registry.
  • VGallery Next — new admin area for nodes (conf/gallery/manage/vgallery-next/) with its own repository, layout and editor; plan in VGALLERY_NEXT_PIANO.md.
  • Admin bar on the front end and alignment guides.
  • Registration migrated to a widget (modules/auth/contents/registration/), with the account managed from the backend; the old contents/registrazione/ was removed and pages renamed to registration.
  • Language management in the wizard and backend; translated authentication pages and language redirects via cookie.
  • Database seed and conf/gallery/config.php aligned.
  • Sentry integration (bootstrap + selftest).

Fixed 4 entries

  • [LANGUAGE_SWITCHER] printed literally on front-end pages (e.g. /login).
  • TRACE_VISITOR undefined → runtime fatal during the wizard.
  • /restricted/{tags,place,resources}: 500 error on the users table.
  • Non-working tabs in backend popups and invisible dialog on the actex field (Structure).

1.0.0

26 Jul 2026

Added 8 entries

  • WordPress-style automatic installer (install/): wizard, config generation, install.lock, self-disabling, install/cleanup.php that deletes /install at the end of installation. Plan in INSTALLER_PIANO.md.
  • Versioning: JC_VERSION and JC_SCHEMA_VERSION, written into the generated config.
  • JoeCMS branding: identity, logo, palette.
  • Authentication API service (api/1.0): client credentials → Bearer token, with the joecms_api_* helpers in hook.php.
  • Complete site-side authentication: registration, login, password recovery, activation.
  • Multilingual, cookie banner, new headers and footers, new home page, new services.
  • Email previewer and sending with an inline logo (cid:, never URL).
  • AI indexing: llms.txt, Markdown version of content, robots rules for AI bots (GUIDA_INDICIZZAZIONE_AI.md).

Removed 1 entry

  • All leftovers of the legacy project the code comes from: over a hundred conf/packages/*.xml (applets and configurations of medici-online / liveinhealth), unused services, references to domains and paths of the old environment, plain-text passwords in the sources.

Pre-1.0

2026-04-29 → 2026-07-20 · PHP 7 → PHP 8 migration
End of history. It all started here.