EvoUI v1.0.2
This release improves EvoUI runtime asset delivery for Evolution CMS modules and prevents manager screens from serving stale copied EvoUI CSS/JS after package updates.
Highlights
- Published EvoUI runtime assets through Evolution CMS
vendor:publishsymlink declarations. - Kept
evo-uiCSS and JavaScript owned by EvoUI instead of requiring consuming modules to publish them manually. - Preserved copy-based config publishing for
config/evo-ui.php. - Documented the recommended update flow:
php artisan vendor:publish --tag=evo-ui --force - Added contract coverage to prevent EvoUI assets from silently returning to plain copied publish paths.
Runtime Assets
EvoUI now declares evo-ui.css and evo-ui.js as symlink publishables.
On Evolution CMS 3.5.7+, vendor:publish links public files under assets/modules/evo-ui back to the package runtime when the filesystem supports symlinks. This keeps installed modules such as sArticles, sLang, sSeo, and dIssues on the current EvoUI frontend runtime after package updates.
If symlinks are unavailable on the hosting environment, Evolution CMS falls back to copying the assets.
Upgrade Notes
After updating EvoUI, run:
php artisan vendor:publish --tag=evo-ui --forceThis refreshes the public EvoUI assets and replaces old copied files with symlinks where possible.