Copying eCommerce product_detail.php into theme (to customize) breaks ALL CSS and ???
Permalink
I'm trying to do something that should be simple,
I want to modify the core eCommerce product detail page so I can have a sidebar for the Specifications Tables. So, I'm following the simple enough instructions here.
https://www.concrete5.org/marketplace/addons/ecommerce/documentation...
But as soon as I copy the product_detail.php into the theme, when I go into Page Types and click DEFAULTS to edit the page type, I find it broken (ALL the css and ???...
see the screenshots for before and after ).
This happens even with an unedited copy of the original product_detail.php file
(so it seems it has nothing to do with my edits).
Are these instructions somehow outdated? If not, what the heck is happening?
This is in 5.6.3.3 with the latest Core Commerce
I want to modify the core eCommerce product detail page so I can have a sidebar for the Specifications Tables. So, I'm following the simple enough instructions here.
https://www.concrete5.org/marketplace/addons/ecommerce/documentation...
But as soon as I copy the product_detail.php into the theme, when I go into Page Types and click DEFAULTS to edit the page type, I find it broken (ALL the css and ???...
see the screenshots for before and after ).
This happens even with an unedited copy of the original product_detail.php file
(so it seems it has nothing to do with my edits).
Are these instructions somehow outdated? If not, what the heck is happening?
This is in 5.6.3.3 with the latest Core Commerce
So, when you copy a page template from a package into a theme to override it, you have to add in the header and footer elements.
I did wonder why those elements were missing, and silly me, I initially thought it might be something unique about the Core Commerce block.
Thanks Ryan @Mesuva. He explained how because when you have a page type outside of a theme, it uses view.php as the wrapper.. but when it is inside the theme it doesn't.
Even though everyone builds their themes a bit differently (so there's no hard-and-fast rule of what needs to be done), this probably should be included in the documentation page above!