Moving from Rhymix or XE
This page covers what you need to know when moving a site that ran on Rhymix or XE to Zittme.
From Rhymix to Zittme
Zittme was forked from Rhymix 2.1.35 and stays compatible with it.
- Most third-party modules, add-ons, skins, and layouts work as is. The core
Rhymix\namespace remains as a compatibility alias. - The migration process is the same as an update: back up, overwrite with the Zittme release, and open the admin screen.
- The DB structure is compatible with Rhymix 2.1.35. Tables for Zittme-specific features are added automatically when you access the admin screen.
Things to watch for:
- If you had modified Rhymix core files directly, those changes are lost when you overwrite.
- After the migration, zittEditor is suggested as the default editor. If you had explicitly chosen ckeditor, that choice is kept.
- Going back (Zittme → Rhymix) means accepting that data from Zittme-specific features (themes, repeat fields, and so on) will be ignored, and it is not recommended. Always keep a backup from before the migration.
From XE 1.x to Zittme
After upgrading, you cannot go back to XE. The only way to recover is a backup made beforehand.
Prerequisites
- You need XE 1.8 or later to upgrade directly. If you are on an older version, first upgrade to the latest XE (1.11), finish all module updates and table creation, and then proceed.
- Make sure the server runs PHP 7.4 or later (XE ran on 5.x, but Zittme does not).
- Back up your FTP files and DB in a form you can restore yourself.
- Start the work while logged in as the top administrator.
Steps
- Download the Zittme release and overwrite everything in the XE installation folder. Confirm a 100% upload so new folders (such as
common/framework) are not missed. FTP sometimes drops a few of thousands of files. - Refresh the admin screen and prompts for module updates and table creation appear. Run all of them.
- Run cache file regeneration. If it fails, you can delete the contents of
files/cachevia FTP. - Review the site and security settings in System settings.
- Review the third-party checklist below, and turn features that were absorbed into the core back on in their new locations.
- Use the unneeded core file cleanup on the admin dashboard to remove leftover XE files.
- Back up the live site's
files/and DB - Practice the migration on a copy server first
- Sort out resources that appear in the checklist above
- Replace the files with the Zittme release, open the admin screen, and run the DB conversion
- Check pages, login, posting, and attachments
Large sites take time to convert. Always practice on a copy server first; separate migration tools are not recommended.
XE third-party resource checklist
Many resources from the XE era have either been absorbed into the core or no longer work.
| Resource | Status | Action |
|---|---|---|
| Advanced mail module | Partially absorbed | Recheck the mail sending method in System settings > Notification settings |
| Auto login module | Fully absorbed | Use the core feature. Existing auto logins are reset |
| Multidomain module | Fully absorbed | System settings > Site settings |
| SEO module | Moved | System settings > SEO settings |
| Error log module | Moved | System settings > Debug settings |
| Session shield add-on | Moved | Session security key in System settings > Advanced settings |
| Script compression (ZipperUpper) | Moved | System settings > Advanced settings |
| Communication add-on | Not needed | Messaging is in the core communication module |
| CAPTCHA add-on | Does not work | Replace with reCAPTCHA |
| External jQuery loader add-ons | Not supported | Remove |
| CafeXE / Homepage module | Not supported | Conflicts with multidomain. Upgrading is not recommended |
Criteria: Fully absorbed (integrated into the core, configure in the new location) / Partially absorbed (only partly integrated) / Moved (moved to a different menu) / Not supported (replacement needed) / Does not work (replace immediately).