Development and testing releases
Test the next JEM release
Beta versions allow the JEM community to test new functionality, migration paths and bug fixes before a stable release is published.
Beta versions are not intended for production websites
Install beta packages only on a test website or a complete clone of your production installation. Always create a full backup of the files and database before installing or updating JEM.
JEM 5.0.1 Beta 1
For Joomla 5 and Joomla 6
JEM 5.0.1 Beta 1 is the first public test package for the next JEM 5 maintenance release.
One of the main objectives of this beta is to test the migration process from JEM 4.4.0 and later to the JEM 5 release line.
Community testing helps identify installation, migration and compatibility problems before the stable version is released.
- Version
- 5.0.1 Beta 1
- Status
- Beta
- Joomla
- 5 and 6
- Package
- Full JEM package
Community testing
Who should test this beta?
Different installation scenarios are useful for detecting migration and compatibility problems.
Existing JEM 4 users
Test the migration from JEM 4.4.0 or a later JEM 4 version using a cloned website with representative events, venues, categories and registrations.
Existing JEM 5 users
Test the update from JEM 5.0.0 and verify that existing events, modules, menu items, settings and frontend layouts continue to work correctly.
New installations
Test a clean installation, sample data, initial configuration, event creation and the main frontend and administrator views.
Migration testing
Choose the correct test path
Test the normal update
Update a test installation from JEM 5.0.0 to JEM 5.0.1 Beta 1.
Check the administrator, frontend layouts, modules, plugins and existing configuration.
Test the JEM 4 migration
Use this beta to test migration from JEM 4.4.0 or a later JEM 4 release to the JEM 5 release line.
Verify events, venues, categories, registrations, menu items, modules and database structure after migration.
Use the legacy migration path
Installations older than JEM 4.4.0 should not test a direct migration to JEM 5.0.1 Beta 1.
Update first using the documented JEM 4.5.0 migration procedure.
Read the migration guideTest checklist
What should be checked?
Test the functions that are important for your website and report any differences from the previous JEM version.
- Installation and database update
- Existing events, venues and categories
- Registrations and attendee information
- Recurring events
- Menu items and frontend views
- JEM modules and plugins
- Multilingual websites
- Template overrides and custom CSS
Before installing the beta
- Create a complete backup of the website files and database.
- Restore or clone the website in a separate testing environment.
- Record the Joomla, JEM, PHP and database versions.
- Check whether the website uses JEM template overrides.
- Install the beta package using the Joomla extension installer.
- Clear the Joomla and browser caches before testing the frontend and administrator.
Important notice about template overrides
Older JEM template overrides may not be compatible with current JEM layouts.
When a frontend problem appears after the update, temporarily rename or disable the JEM override and test the original JEM layout. Report whether the problem also occurs without the override.
Feedback
Report a beta problem
Clear and reproducible reports help the development team identify and correct problems more quickly.
Include the following information:
- Joomla version
- Previous JEM version
- PHP and database versions
- Fresh installation, update or migration
- Exact steps required to reproduce the problem
- Expected and actual result
- Complete error message or relevant log entry
- Whether JEM template overrides are enabled
Where to report
Use the JEM forum for testing discussions and GitHub for confirmed, reproducible software issues.
Need a production-ready version?
Use the current stable JEM release for live Joomla websites. Beta packages should only be used for testing.
Download the stable JEM release