JCB Release Candidate Testing – We Need Your Help!

[Llewellynvdm]

We’re excited to announce the release candidates for JCB 5 and 4! This update brings a significant improvement: all IDs across the database have been completely decoupled, ensuring that every component is now linked to its respective entities via globally unique IDs. This is a major step forward for JCB, and we need your help to ensure everything works smoothly before the stable release.

• JCV v5.1.0-rc1
• JCV v4.1.0-rc1
• JCV v3.2.5-rc1

How You Can Help

The best way to test is by upgrading an existing project:

1. Clone Your Existing System – Before installing the release candidate, create a backup of your project.
2. Build & Commit – Build your current extension and commit it to a Git repository.
3. Upgrade – Install the release candidate package and compile the extension again.
4. Compare & Verify – Delete the old extension files, replace them with the newly compiled ones, and use git diff to compare the changes.
5. Report Issues – If you notice any serious discrepancies, please open an issue so we can address them before the stable release.

We’ve conducted extensive internal testing, but we want to ensure a smooth transition for everyone. Your feedback is invaluable in catching any unexpected issues.

Thank you for your support—we appreciate your help in making JCB even better!

Get started now and let us know your findings!

[oxido21]

Can not install v.5.1.0-rc3, I get this on first installation:
Unknown column 'add_custom_import' in 'INSERT INTO'

If I try tor reinstall after I get the first error, I get a new one:
JInstaller: :Install: Error SQL Duplicate entry '25' for key 'PRIMARY'

It can be installed only if a previous version of JCB it is installerd already

[Llewellynvdm]

This was fixed in the next RC4 release.