Evolution CMS 3.3.0

Dmi3yy

https://github.com/evolution-cms/evolution/releases/tag/3.3.0

Notice: Minimum PHP version 8.3 is required.
PHP 8.2 and below are no longer supported.

This release makes a decisive move forward — Evolution CMS now officially runs on PHP 8.3 and is fully compatible with PHP 8.4.
We’re aligning with the modern PHP ecosystem (including Laravel) to deliver a faster, cleaner, and more future-proof platform.
Dropping PHP 8.2 support lets us remove outdated code and take advantage of the latest language features, improving both stability and performance.

One of the key updates is the new Priority Service Provider Registration, which allows developers to define the initialization order of extensions.
This change eliminates long-standing plugin conflicts and ensures predictable, consistent boot sequences across the system.

Alongside that, 3.3.0 brings several quality-of-life improvements — configuration fixes, Tailwind CSS multi-file compilation, code cleanup, ISO-standard naming, and small UI refinements.

• [74dd478] – Add Priority registration Service Providers (Seiger) • [8400156] – Add niceEta() – format ETA seconds into human-readable format (Seiger) • [7858c0a] – Add multiple Tailwind CSS file compilation (Seiger) • [f2355a6] – Fix missing value in config (elcreator) • [d6ecb76] – Fix Ignore suffix in Manager Middleware (Seiger) • [bfef7e7] – Deprecate nicesize() → use niceSize() (ISO standard) (Seiger) • [b3a71f2] – Refactor MODX_CLASS → EVO_CLASS (Seiger) • [af8c774] – Add PHP 8.4 support (Seiger)
Full changelog: from 3.2.7 to 3.3.0
https://github.com/evolution-cms/evolution/compare/3.2.7...3.3.0

fourroses666

Good to see there are improvements going on.

efilippi

Good job guys ! Thanks for this announcement.
I'm starting my migration from V2.0.4 to V3 to get full Laravel benefits.
Graffx Design I'll keep you informed how I'm doing with the yams cache concern ...

fourroses666

Cool, still have one site with good old YAMS lol.

fourroses666

I did just update EVO 1.4.35 (my last site on EVO 1.x) -> EVO 3.1.30 and looks like the cache issue is not there anymore.

I used this module; Downloaded it and on Extra's installed it and run.
https://github.com/BBloke/evo-migrate/tree/1.x

(Maybe no related and something was fixed in 3.1.30)

Sofar I can't reproduce that cache issue.

efilippi

Graffx Design OK cool if the cache problem is not there anymore.
I'm in the process of migrating, I will tell you if I see something bad.

For your YAMs error with PHP 8.2. I'm still in PHP 7.4 so I can't try it but I confirm, it's a PHP 8 restriction.
What is your YAMs version, 1.3.1 ? I haven't the same line 288 in yams.plugin.inc.php !

(check the version in assets/modules/yams/README.md)

EDIT : OK, It seems that you are still in v 1.2.0-RC3 or RC6, but I developed in 2020 a new v1.3.0 based on the Deesen v1.2.0-RC7. This line if( ! array_key_exists( $tvIdentifier, $tmplvars ) ) is not in the RC7 code anymore ...

v1.3.0 is for Evo 2.x and php 7.4 compatibility, I've been running this for 5 years in Evo 2.x without any problem. I'll check if I get this bug in v3.1.10. I'm not sure if YAMs v1.3.1 is ok with php 8 so don't upgrade until I'll tell you.

This is my plan :
-1. upgrade to evo 3.1.10 (last evo version that accept php7.4)
1.1. check and adapt Yams for evo V3 and php 8 compatibility => maybe new Yams release
-2. migrate my server to php8
-3. migrate to evo 3.2
3.1 consider a migration plan (if possible) to sLang (because sLang needs Evo 3.2 so I can't do it in 1.)

I'll share it for all people that refrain migrating to V3 because of Yams. Having in mind that the goal is to switch to sLang when possible.

fourroses666

Oke, seems YAMS and PHP 8.2 / EVO 3 shows an error when saving a resource..

array_key_exists(): Argument #2 ($array) must be of type array, null given
Error information 	
File 	/home/.../domains/....nl/public_html/assets/modules/yams/yams.plugin.inc.php
Line 	288
Source 	if ( ! array_key_exists( $tvIdentifier, $tmplvars ) )

fourroses666

1.2.0 RC4, I see in the module.

I have the error message removed, its not there anymore but the source of the issue is not fixed.
I'm using EVO CE because all my sites are CE and don't have a good reason to go to the other one.
I need my alias to stay different on all languages. bLang won't do that. sLang I dunno about.

efilippi

1.2.0 RC4 is not compatible with PHP 8, so I recommand to upgrade YAMs to V1.3.0 which is very stable, I've been using it for 5 years.
v1.3.0

Just copy v1.3.0 files in assets/modules/yams
Don't forget to backup before upgrade, so you secure your data and you keep you yams.config.inc.php safe.

So far I don't have errors on EVO v3 and YAMS v1.3.1. It's running fine. I keep on testing ... and publish the release when it's done.

Next time I'll do the YAMs post in another topic so it doesn't clutter this one 😀