Upgrade to Magento CE 2.2.9 from 2.2.6 class name difference cause many frontend customization not applying
Hi
I have the latest Pearl 1.9 (Starter pack).
I recently upgraded my Magento from 2.2.6 to 2.2.9. I am surprise to find that there page layout looks a little different. All my content section of my pages, category, product pages are all set to 1400px width and they all display correctly when I am using Magento 2.2.6. After the upgrade of the Magento core to 2.2.9, I found that content section my pages are now only 1200px and some heading sizes are also different.
After some debugging, I discovered that the class name specific for the theme is different.
This is code extracted from one content page from one of my Magento instances still on 2.2.6:-
<body data-container="body" data-mage-init='{"loaderAjax": {}, "loader": { "icon": "https://bsc.dev3.winterroot.com/pub/static/version1565224300/frontend/Spring/spring_bsc/en_US/images/loader-2.gif"}}' class="theme-pearl store-view-bsc-en wp-sl cms-order-tax-cancellation-return-policies cms-page-view page-layout-1column">
This is the same piece of code in my Magento instance upgraded to 2.2.9:-
<body data-container="body" data-mage-init='{"loaderAjax": {}, "loader": { "icon": "https://bsc.dev1.winterroot.com/pub/static/version1565439961/frontend/Spring/spring_bsc/en_US/images/loader-2.gif"}}' class="theme-pearl store-view-bsc_en wp-sl cms-order-tax-cancellation-return-policies cms-page-view page-layout-1column">
The storeview code for this particular storeview is "bsc_en". It seems that before the upgrade of the Magento core, the class name that was generated is "store-view-bsc-en" which corresponds to the CSS styles defined in css/styles-l.css. After the upgrade, somehow the class name is now "store-view-bsc_en". This resulted in all the CSS that is defined for class ".theme-pearl.store-view-bsc-en" getting ignored.
Does anyone else encounter the same problem?
I suppose to get this problem, you would have to have a storeview code with an underscore.
Regards
Donnie
Please sign in to leave a comment.
Comments
0 comments