Skip to main content
LucentUI 3.0 updates use the same outer bundle and two inner ZIP files as a fresh installation.
Back up local Blade, CSS, or JavaScript modifications before replacing the theme. Saved Editor settings remain in Paymenter’s database, but direct file edits are overwritten by the new package.
1

Read the release notes

Check the LucentUI changelog for compatibility notes and changes that may affect custom code or extension overrides.
2

Extract the downloaded bundle

Open LucentUI-3.0.0-bundle.zip on your computer and keep both inner installation ZIP files intact.
3

Export the current design

Open LucentUI Editor and select Export. Store the resulting JSON file with your server backup. This gives you a portable copy of all lucentui_* settings.
4

Back up files

5

Replace theme source and public assets

Extract the new theme ZIP over themes/lucentui, then republish the bundled assets.
6

Upload the new Editor package

Use Extensions → Available Extensions → Ready to Install / Upload → Upload Extension and select the new LucentUIEditor-3.0.0-upload.zip. Paymenter detects the installed copy, replaces the extension files, and runs its update lifecycle.
7

Clear caches and verify

Reload the administrator panel and storefront. Confirm the version in themes/lucentui/theme.php, then test both color modes and critical client routes.

​
Roll back

If the update fails, restore both backed-up directories, clear caches, and reload the site. Import the Editor JSON only if the saved database configuration was deliberately changed during troubleshooting.
Old hashed asset files are harmless when the active manifest.json points to the new files. For a tidy deployment, synchronize the public directory from the release rather than deleting broad application paths.
Last modified on September 10, 2026