Info/Feature request

[vvinci00]

Hello,

we are trying to update our site from concrete 8 to concrete 9 and we need to migrate also the community store with products and variations.

There's any known way to migrate it or could you suggest any best practice?
We are trying the migration_tool but with several issue and it not detecting community store and it's products.

thanks

[Mesuva]

As you're going from V8 to V9, you shouldn't need a migration tool for that.

It should be a case of upgrading Community Store the latest release, then upgrading from V8 to V9.
Community Store's latest release should be compatible with both v8 and v9 still.

Previously when going from V8 to V9 were some issues with upgrading attributes (in products and orders), but the last time I did this upgrade things went fine.

I'd only attempt this on a copy of a site though, to see how it all goes as a test.
What happens when you try that now?

[vvinci00]

Hi,

the main problem is that the theme we are using in V8 has been published as separate packages for V9 and not as an update. So, we have tried to update the website itself but all pages broke.

The only solution we have found is to create a new V9 instance and migrate the content

[Mesuva]

Wouldn't you be able to swap back to the default theme, remove the existing theme, do the upgrade to V9, then install the 'new' theme and apply it?

That's still going to be easier than trying to rebuilt and reconfigure a whole new site.

[vvinci00]

this what we have firstly done:

1. update to concrete 9
2. update to php 8.3
3. install new theme

now we have tried:

1. switch to elemental theme
2. update to concrete 9
3. update to php 8.3
4. install new theme

the result it's the same: all pages broken

[Mesuva]

What error message are you getting on the broken pages?
Can you show a full debug here?

[vvinci00]

Hi,

no error appear on php or concrete.
The problem is on the theme.

although the theme is the same, the concrete8 (php7) theme package is different, with different handle, from the concrete9 theme package.
When we try to update, all the pages lost their settings and content's organisation and this is why we think that the only way is to create a new server and migrate the content manually.

we have also tried to use the migration tool (https://github.com/concretecms/addon_migration_tool) but we are having a lot of errors on concrete9 and section missing in the new theme package.

[Mesuva]

The migration tool isn't going to help with Community Store.

What that sounds like is that the theme is just a different theme, perhaps using the same name.

I've been updating a lot of V8 sites lately to V9, and even if a theme isn't fully updated for V9, normally it doesn't take too much to work to make it compatible. What happens when you use the existing theme in V9?

[vvinci00]

yes the name and the author it's the same (it's pixel theme) but for concrete V9 it has been published a new package instead of an update.
if we use pixel2 (officially compatibile with concrete 8) in concrete 9 we got several error on variables type in page loading.

Trying to fix the page, adding blocks, after the installation of new theme, we got this error:

Exception thrown with message "No grid framework found. Grid area methods require a valid grid framework defined in a PageTheme class."

Stacktrace:
#34 Exception in /var/www/html/www/web/concrete/src/Area/Area.php:163
#33 Concrete\Core\Area\Area:getAreaGridMaximumColumns in /var/www/html/www/web/concrete/src/Block/Menu/Menu.php:138
#32 Concrete\Core\Block\Menu\Menu:__construct in /var/www/html/www/web/concrete/src/Block/Menu/Manager.php:24
#31 Concrete\Core\Block\Menu\Manager:getMenu in /var/www/html/www/web/concrete/elements/block_header_view.php:234
#30 include in /var/www/html/www/web/concrete/src/Block/View/BlockView.php:284
#29 Concrete\Core\Block\View\BlockView:renderViewContents in /var/www/html/www/web/concrete/src/View/AbstractView.php:164
#28 Concrete\Core\View\AbstractView:render in /var/www/html/www/web/concrete/src/Area/Area.php:857
#27 Concrete\Core\Area\Area:display in /var/www/html/www/web/packages/shared/themes/registration/default.php:18
#26 include in /var/www/html/www/web/concrete/src/View/View.php:125
#25 Concrete\Core\View\View:inc in /var/www/html/www/web/packages/shared/themes/registration/full.php:11
#24 include in /var/www/html/www/web/concrete/src/View/View.php:339
#23 Concrete\Core\View\View:renderTemplate in /var/www/html/www/web/concrete/src/View/View.php:301
#22 Concrete\Core\View\View:renderViewContents in /var/www/html/www/web/concrete/src/View/AbstractView.php:164
#21 Concrete\Core\View\AbstractView:render in /var/www/html/www/web/concrete/src/Http/ResponseFactory.php:147
#20 Concrete\Core\Http\ResponseFactory:view in /var/www/html/www/web/concrete/src/Http/ResponseFactory.php:220
#19 Concrete\Core\Http\ResponseFactory:controller in /var/www/html/www/web/concrete/src/Http/ResponseFactory.php:372
#18 Concrete\Core\Http\ResponseFactory:collection in /var/www/html/www/web/concrete/src/Http/DefaultDispatcher.php:132
#17 Concrete\Core\Http\DefaultDispatcher:handleDispatch in /var/www/html/www/web/concrete/src/Http/DefaultDispatcher.php:60
#16 Concrete\Core\Http\DefaultDispatcher:dispatch in /var/www/html/www/web/concrete/src/Http/Middleware/DispatcherDelegate.php:39
#15 Concrete\Core\Http\Middleware\DispatcherDelegate:next in /var/www/html/www/web/concrete/src/Http/Middleware/FrameOptionsMiddleware.php:39
#14 Concrete\Core\Http\Middleware\FrameOptionsMiddleware:process in /var/www/html/www/web/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#13 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/html/www/web/concrete/src/Http/Middleware/StrictTransportSecurityMiddleware.php:36
#12 Concrete\Core\Http\Middleware\StrictTransportSecurityMiddleware:process in /var/www/html/www/web/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#11 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/html/www/web/concrete/src/Http/Middleware/ContentSecurityPolicyMiddleware.php:36
#10 Concrete\Core\Http\Middleware\ContentSecurityPolicyMiddleware:process in /var/www/html/www/web/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#9 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/html/www/web/concrete/src/Http/Middleware/CookieMiddleware.php:35
#8 Concrete\Core\Http\Middleware\CookieMiddleware:process in /var/www/html/www/web/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#7 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/html/www/web/concrete/src/Http/Middleware/ApplicationMiddleware.php:29
#6 Concrete\Core\Http\Middleware\ApplicationMiddleware:process in /var/www/html/www/web/concrete/src/Http/Middleware/MiddlewareDelegate.php:50
#5 Concrete\Core\Http\Middleware\MiddlewareDelegate:next in /var/www/html/www/web/concrete/src/Http/Middleware/MiddlewareStack.php:86
#4 Concrete\Core\Http\Middleware\MiddlewareStack:process in /var/www/html/www/web/concrete/src/Http/DefaultServer.php:85
#3 Concrete\Core\Http\DefaultServer:handleRequest in /var/www/html/www/web/concrete/src/Foundation/Runtime/Run/DefaultRunner.php:128
#2 Concrete\Core\Foundation\Runtime\Run\DefaultRunner:run in /var/www/html/www/web/concrete/src/Foundation/Runtime/DefaultRuntime.php:102
#1 Concrete\Core\Foundation\Runtime\DefaultRuntime:run in /var/www/html/www/web/concrete/dispatcher.php:45
#0 require in /var/www/html/www/web/index.php:2

[Mesuva]

That looks like it's referencing pages in a 'shared' package
/var/www/html/www/web/packages/shared/themes/registration/full.php
/var/www/html/www/web/packages/shared/themes/registration/default.php

Is that some custom theme specifically for this site? Why would they be being referenced here?

Maybe there's some pages that need to be configured to use the new theme.

[mlocati]

The problem is that:

1. pixel2 comes with many useful block types
2. @shahroq published a version of pixel that's compatible with concrete 9, but he changed the handle of the package

Because of 2, it's not possible to simply upgrade the pixel package.
The only solution I can see is to use the migration tool, in the hope that the handles of the block types of pixel9 are the same as the ones of pixel2.