Welcome to eZpedia!
| The free eZ Publish encyclopedia that anyone can edit. eZpedia has accumulated 722 english articles since 2006. We encourage you to create an account and create or edit a page yourself. Some folks create an article in the people namespace with their full name as the article name with a brief description of who they are, their interests, goals and objectives. Ask A QuestionDo you have an eZ Publish question, do you need an eZ Publish answer? Simply login and ask your question in our discussion forum. We publicly write free documentation based on your submissions. Posting on eZpedia is a great way to get answers you need and contribute to our freely available community documentation for eZ Publish. Chat with other eZ Publish Developers LIVE from around the World!EcosystemRead about what is going on within the various eZ Publish related websites on internet. Recent development activityTrack the development progress through the roadmap by reviewing recent Exponential Git activity from the github repository. Last updated: 2026-07-16T11:39:22Z
2026-07-16T11:39:22Z
Renamed: Renamed kickstarter.ini to avoid clean install conflicts. Bugfix.
2026-07-16T10:51:49Z
Updated: Updated filelist.md5 file hashes
2026-07-16T09:35:42Z
Refactor setup wizard to avoid MySQL system database access and improve error handling. This change makes the installer safer for shared-hosting environments by: - No longer requiring SHOW DATABASES or access to the mysql system database. - Adding a Database name input for MySQL/MariaDB in database_init.tpl. - Catching MySQLi errors during connect/select_db/set_charset instead of fataling. - Fixing expScriptStatus so the undefined STDOUT constant does not crash web requests. - Ensuring eZDebug::setHandleType(HANDLE_NONE) cleans up the error handler. - Adding installer logging so database failures are written to setup.log/error.log. End users can now complete setup with only privileges on their own database, and any connection issues are reported as friendly on-screen errors with details logged server-side for easier troubleshooting.
2026-07-14T20:44:05Z
Add #[AllowDynamicProperties] to eZINI, eZPersistentObject, eZWorkflowProcess
2026-07-13T05:03:27Z
Add documentation for the Kickstarter CLI and kickstart.ini workflow. - Adds `doc/bc/6.0/kickstartercli.md` covering the Kickstarter CLI entry points (`bin/php/console exp:kickstarter` and `bin/php/kickstarter.php`). - Documents `kickstart.ini` section-by-section and the command-line options `--dry-run`, `--force`, `--start-step`, `--stop-step`. - Explains remote package handling (the `index.xml` vs `package.xml` version mismatch) and the dry-run temporary `dryrun/` repository with cleanup. - Includes a quick-start guide, installation workflow, examples, FAQ, troubleshooting, and implementation notes. - Provides a command reference table and describes the `eZPackage::import()` `skipExisting` parameter and `eZStepSiteTypes` remote-preference logic. - Adds safety/stability notes for the normal web setup wizard, `eZPackage` backward compatibility, and the `dryrun/` cleanup. Benefits: gives operators and developers a single, self-contained reference for automated site installs, validating remote packages, and understanding the dry-run flow without the web setup wizard.
2026-07-13T04:39:23Z
Updated: Added git_manager to 6.0.15 release composer.json. Feature
2026-07-13T04:27:27Z
Add Kickstarter CLI, remote package dry-run support, and script status refactor. This commit introduces the Kickstarter CLI and the supporting plumbing that allows unattended, configuration-driven site installs and safe remote package validation. Features: - bin/php/kickstarter.php: new standalone entry point for the `ini` generator and `run` setup commands. Mirrors `exp:kickstarter` for environments that do not use the Exponential Console. - bin/php/console: discovers `bin/php/*` subdirectories as namespaced CLI commands (e.g. `kickstarter:ini`), keeping the console extensible. - kernel/classes/expkickstarter.php: non-interactive setup wizard driver. Adds `--dry-run` (runs through `Registration` to test remote downloads and stops before `CreateSites`), `--force` for installation, `--start-step`/`--stop-step` for resumable runs, and cleanup of the temporary `dryrun/` package repository. - kernel/classes/expkickstarterini.php: interactive `kickstart.ini` generator that walks the same sections as the web setup wizard. - kernel/classes/expscriptstatus.php: rename/refactor of `eZPMStatus` into a general-purpose CLI progress reporter used by `ezpm` and the package export handler. - autoload/ezp_kernel.php: registers the new `expScriptStatus`, `expKickstarterIni`, and `expKickstarter` classes. - kernel/classes/ezpackage.php: adds optional `$skipExisting` parameter to `import()` so temporary/dry-run repositories can import a package without hitting `STATUS_ALREADY_EXISTS` when a local copy already exists. - kernel/setup/steps/ezstep_site_types.php: prefers remote packages when `kickstart.ini` `[site_types]` is active, handles the `index.xml` vs `package.xml` version mismatch, and passes `$repositoryID`/`$skipExisting` to the download helpers for dry-run support. - kernel/setup/steps/ezstep_package_language_options.php: casts the site language list to an array so an empty `Languages[]` no longer fatals inside `array_diff()`. - ezpm.php: switches from `eZPMStatus` to `expScriptStatus` for consistent, reusable progress output. - kernel/classes/packagehandlers/ezcontentobject/ezcontentobjectpackagehandler.php: uses `expScriptStatus` during content-object package export. - kickstart.ini: generated configuration for the Kickstarter CLI, with the database password left empty so the real value is not stored in the repository. - share/filelist.md5: updated to reflect the new and modified files. Benefits: - Site installs can be fully automated from `kickstart.ini` instead of relying on the web wizard. - `bin/php/console exp:kickstarter run --dry-run` verifies remote package availability and downloads without modifying the database or siteaccess. - The `expScriptStatus` reporter is reusable by any CLI tool, not just `ezpm`. - The setup wizard steps are safer: missing/empty language lists do not fatal, and dry-run package imports avoid overwriting existing local packages. |
Recent discussionsRead what others are discussing |
|
Recently updated articlesRead recently modified articles
|
||
