Hi all,
For anyone running 4.7.0b: updating or reinstalling SEBLOD in that state corrupts your Seblod configuration and data. The installer runs an old, destructive migration path against your current site, which can damage content types, fields, folders and more. The exact impact varies from site to site. One visible symptom is lists (e.g. seb_table) losing their assigned fields and assigned template, and the process ending with a Call to undefined method stdClass::get() error. The catch is that 4.7.0b on its own doesn't break anything, the damage happens the moment you install SEBLOD 6 on top of it or even the same 4.7.0b. So if you're on 4.7.0b and haven't updated or reinstalled yet, you're still in time.
What NOT to do for now if you're on 4.7.0b:
- Don't install Seblod 6 on top of it
- Don't reinstall Seblod 4.7.0b over itself (that triggers the failure too)
The installer's postflight (plg_content_cck) decides which migrations to run by looking up the installed version in an internal version array that ends at 4.6.2 and doesn't include 4.7.0. When it can't find the version, that lookup returns false, and because of how that value is used afterwards, the installer ends up running a branch of old migrations (meant for much earlier versions) against a current site. That's what corrupts the content types. Updating from any version prior to 4.7.0b works fine; the failure only shows up (and always does) when starting from 4.7.0b, because that's the version that introduced the version number the installer doesn't recognize.
Workaround if you need to update now (tested on a staging site; take a full backup first): set the recorded version back to one the installer does recognize, then install Seblod 6 as usual.
UPDATE `#__extensions`
SET manifest_cache = REPLACE(manifest_cache, '"version":"4.7.0"', '"version":"4.6.2"')
WHERE element = 'com_cck' AND type = 'component';
(Adjust the #__ prefix to match your installation)
It would be great if the team could look into this and release a version that fixes the installer, so nobody has to edit the database by hand.
Best regards,
Adonay
Hi,
Perhaps some of my problems are related to this (there are only on 4.7.0b)
Several issues when editing certain Content Types as a Super User
I have noticed several issues that occur when a Super User edits certain SEBLOD Content Types:
All List & Search results disappear
All SEBLOD List & Search instances stop displaying their data. This affects both:
List & Search instances displayed in modules;
fields of the List type used inside the form.
The modules/field containers themselves are still rendered, but the list results are empty.
Multiple console warnings related to TinyMCE
The following warning appears repeatedly in the browser console:
[Violation] Permissions policy violation: unload is
not allowed in this document.
The warning is related to tinymce.js.
For example, when editing an Article-based Content Type, this warning is displayed 26 times.
Multiple JCE plugin.js requests
When editing these Content Types, there are
numerous requests for JCE plugin.js files.
According to the browser Network panel, the
initiator of these requests is tinymce.js.
These issues occur when the page is accessed as a Super User. When the same page is accessed as Public, the List & Search results are displayed correctly and the additional TinyMCE/JCE activity is not present.
These issues appear to be related, as they
occur under the same conditions and only in the Super User context.
Stas
Hi Stas,
If you're on 4.7.0b and you haven't updated to Joomla 6 nor reinstalled 4.7.0b on top, it won't be the same problem. If you have done so, it's quite possible.
Best regards
Thank you for sharing the analysis of the problem.
So, I run the SQL query mentioned above, update Joomla 5 to Joomla 6, and then install Seblod 6.0.1?
And I skip Seblod version 5.0.0 because it’s not needed in this case?
Hi Casper,
Yes, you can skip Seblod 5.0.0, just as Saba said.
Yes, if you already have production running on 4.7.0b, as happened to me, the only way to be able to update to Seblod 6 is by changing the version in the extension's manifest_cache column to 4.6.2 (at most) and then updating. If you update without that change, the entire site will become unusable.
Kind regards
Adonay