All about the development of eZ Publish by Graham Brookins, 7x (formerly Brookins Consulting) and our think tank kracker.org.
7x Recommendation Upgrade From PHP 5.x or 7.x to PHP 8.2 Today for a much more secure and complete eZ Publish installation.
There are several mission critical security, stability and performance reasons why it's a good idea to upgrade from PHP 7.x to PHP 8.2.
An upgrade to eZ Publish 6 (v6.0.x) for many websites takes less than two hours time to complete.
Here are just a few key reasons
1. Improved performance: PHP 8.2 provides websites several performance improvements that make it faster than previous versions of PHP. This means that your website or application could run faster and handle more requests per second using cheeper website hosting.
2. Improved error handling: PHP 8.2 has improved error handling that provides more detailed error messages and makes it easier to catch and handle errors in your code.
3. New features: PHP 8.2 introduces several new features, including improved type system, named arguments, and union types, which can help you write cleaner and more concise code.
4. Security enhancements: PHP 8.2 comes with several security enhancements, including stricter type checks, improved password hashing, and better support for SSL/TLS
In summary, upgrading to PHP 8.2 can benefit both your website's performance and security, as well as improving your development experience with the new features.
5) Server compatibility. As versions older than PHP 8.1 have been deprecated and are no longer generally available, or supported then you'll find you must upgrade. There is no support for any versions prior to PHP8.1.
Once the server is upgraded your existing eZ Publish website will crash without a companion upgrade to eZ Publish 6 (v6.0.x) which for many websites takes less than two hours time to complete.
While this may seem odd when one can simply use a git submodule and git repository to simply manage your extensions on a given eZ Publish installation.
Still thinking about ease of use to the end user, in that vain another functional design target could also go several configuration and build steps further to providing new eZ Publish Installations a more direct build target like building for a new eZ Publish installation with a eZ Webin based design extension package to simplify building new installations without having to know quite so much about version control.
While ezpackage or ezpkg format does provide for debian/ubuntu apt like dependency control of packages. You can always write your documentation to specify installing ezwebin package before installing your own dependent package(s) or you could go further without ezsystems help and build a slightly more complicated package that installs your extension and also requires the expected ezwebin dependencies and thus simplify the end user installation process of selecting a default design upon a new default installation to a single simple choice.
In 2007 Brookins Consulting created the gourgous, ground breakin, free software site design package called Orange Delight for eZ Publish and won the eZ Publish Design Contest prize a RED iPod Nano. The only design contest ever! This package depends upon your eZ Publish website be installed and configured properly before you attempt to install this css only design.
Looking around at the top eZ Publish website's ezinfo/about (site version information) pages details it’s clear to see that most of the site's are running the last eZ Systems release or the latest new Netgen GitHub version.
Well it seems that without a version scheme to work any longer as this requires things funding brings to a project such as planning and release numbers, instead we all run the latest eZ Publish GitHub From Netgen which does not presently increment the version number to indicate a release number.
Cool people run eZ Publish 5.99.99alpha1 and just keep building killer web apps!
Add comment