I have a site on concrete 8.5.7 using Modena theme v1.0.3.
Vidal themes have released a version of Modena (2.0.3) for concrete 9.x but it’s not backwards compatible.
Several other 9.x packages I use are backwards to avoid this problem but vidal themes said that there were too many bugs in the 8.5.x core for them to do this.
I tried updating the core to concrete to 9.0.1 but the update fails, front-end and dashboard are broken.
I could change the theme to elemental, run the 9.0.1. update, then reinstall the theme but that would likely cause loss of custom blocks, problems with missing page areas etc. I’d also lose all the style customisation I’ve done on the theme.
Anyone got any thoughts? We have a fairly large site that’s now stuck on 8.5.7 and would take 3-4 days to rebuild manually
I’ve tried running the updates as follows. I’m doing manual updates.
Update Modena to 1.2.3: replace Modena folder in /packages, run update via dashboard - no problems
Replace /concrete folder with one from v9.1.0 (also tried this with 9.1.1)
After a minute or so I get an internal server error. Apache and PHP logs are empty. Tried refreshing the page to see if it would complete the update, internal server error again. After the third try I get a php error:
Argument 1 passed to Concrete\Core\StyleCustomizer\Style\StyleValueList::add() must be an instance of Concrete\Core\StyleCustomizer\Style\StyleValue, instance of Concrete\Core\StyleCustomizer\Style\Value\TypeValue given, called in /Users/simonchilton/Sites/localhost/fingaltri/concrete/src/Page/CustomStyle.php on line 48
Hi @BHyahoo - so you’re getting this error? Argument 1 passed to Concrete\Core\StyleCustomizer\Style\StyleValueList::add() must be an instance of Concrete\Core\StyleCustomizer\Style\StyleValue, instance of Concrete\Core\StyleCustomizer\Style\Value\TypeValue given, called in [localpath]/concrete/src/Page/CustomStyle.php on line 48
I did see this referenced here in this Github issue, not sure if there’s anything helpful there:
And it looks like it has popped up in the past:
Did you happen to migrate this site by any chance? I’m seeing that pop up as a common occurrence in some of these older threads.
I’m wondering if this error is a red herring. I installed a fresh copy of Concrete 8.5.9 and then proceeded to update it to Concrete 9.1.0 by replacing the concrete directory (as described above).
The first thing to watch out for is that Concrete 9.1.0 requires PHP 7.4 or higher. If your pre-9 site is/was running on PHP 7.3.x or something lower, then you’ll need to update PHP first.
After getting past that roadblock, I ran into this error which is also related to the Style Customizer, but in this case, it’s a problem with the database character set:
An exception occurred while executing ‘ALTER TABLE StyleCustomizerInlineStyleSets ADD boxShadowInset TINYINT(1) DEFAULT NULL’: SQLSTATE: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
To get past this, I converted the database from utf8 to utf8mb4 by running the following CLI command from the webroot: