Open sunel opened 4 years ago
Hi, Can you record your browser along with developer console ?
Hi. I must say I'm impressed with your work. Thank you for sharing.
Same issue here.
Magento version: 2.4.5, php 8.1, nginx, firefox / chromium, *.test domain. Had a node (~10) version warning on theme yarn install, ignored. Added empty child theme with parent "Creativestyle/theme-creativeshop". Custom code deregistered. All grinders disabled (bundling, merge, minification, signing). Full generated cleanup and c:c. Nothing abnormal in logs. Most of m2 crapware removed (can attach replacements), msi present, composer require:
"require": {
"ext-fileinfo": "*",
"ext-json": "*",
"ext-mbstring": "*",
"ext-soap": "*",
"bluepayment-plugin/module-bluepayment": "^2.21",
"creativestyle/magesuite-elasticsuite-virtual-category-indexer": "^1.1.10",
"creativestyle/magesuite-magepack": "^1.1",
"creativestyle/magesuite": "~v12.0.0",
"integer-net/magento2-global-custom-layout": "^1.1",
"magefan/module-blog": "^2.2.8",
"magento/composer-root-update-plugin": "~2.0",
"magento/product-community-edition": "2.4.5",
"mageplaza/magento-2-polish-language-pack": "dev-master",
"mageplaza/module-smtp": "^4.6",
"sparsh/magento-2-faq-extension": "~1.2",
},
As far as I was able to look around. I'm missing viewport size selector on top of CMS Page > Content Tab.
Once any component selected console throws
Uncaught TypeError: this.ccConfig.sections is undefined
or in chrome:
Uncaught TypeError: Cannot read properties of undefined (reading 'defaults')
Thanks for your time.
Can you show a print screen of themes configuration in the admin panel?
The error suggests to me that theme creativeshop is not selected as the main theme there.
Sure. I'm using a child which has Creativestyle/theme-creativeshop as parent. But also tried switching to creativeshop - no luck. Will play around with it a bit more in couple. Need to afk atm.
The design configuration screenshot looks really weird, it should have at least 3 rows by default, not only one.
Yes, that's probably because I have Single Store Mode On.
We have never tested it with Enable Single-Store mode so it might not work with such a setting.
Yes that is confirmed. Disabling Single-Store Mode and configuring "Theme Creativeshop" as global under Content > Design > Configuration solved my issue. All looking good now.
Thank you Krzysztof!
After selecting the component from component section page nothing happens, No errors in the console.