Any change to default.xml breaks homepage layout
Fairly new to Magento 2. Working from a cloned version of another site and trying to make simple, cosmetic changes to the custom theme homepage here:
app/design/frontend/Vendor/Theme/Magento_Theme/layout/default.xml
Any change I make manifests immediately, but unrelated parts of the page break at the same time. Most of what's in page-header disappears, and a new div called nav-sections appears with all our categories in it.
These exact changes occur regardless of how I alter default.xml -- even adding a character to a string causes them.
My hunch is it's a question of workflow, and I'm still unclear about when and how Magento 2 decides to create and serve files from pub/static, generated, and var/generated.
I should also note that I'm making these changes in production mode, and that running deploy doesn't fix anything.
What am I doing wrong here?
magento2 layout xml deployment
asked Mar 21 '18 at 15:03
mxtthxwmxtthxw
13
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Fairly new to Magento 2. Working from a cloned version of another site and trying to make simple, cosmetic changes to the custom theme homepage here:
app/design/frontend/Vendor/Theme/Magento_Theme/layout/default.xml
Any change I make manifests immediately, but unrelated parts of the page break at the same time. Most of what's in page-header disappears, and a new div called nav-sections appears with all our categories in it.
These exact changes occur regardless of how I alter default.xml -- even adding a character to a string causes them.
My hunch is it's a question of workflow, and I'm still unclear about when and how Magento 2 decides to create and serve files from pub/static, generated, and var/generated.
I should also note that I'm making these changes in production mode, and that running deploy doesn't fix anything.
What am I doing wrong here?
magento2 layout xml deployment
asked Mar 21 '18 at 15:03
mxtthxwmxtthxw
13
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Inproduction mode, you need to deploy the static-content every time you make changes ! command :php bin/magento setup:static-content:deploy
– PЯINCƏ
Mar 21 '18 at 15:23
Thanks, but the layout breaks even before running thedeploycommand, and stays broken after running it.
– mxtthxw
Mar 21 '18 at 16:36
add a comment |
Fairly new to Magento 2. Working from a cloned version of another site and trying to make simple, cosmetic changes to the custom theme homepage here:
app/design/frontend/Vendor/Theme/Magento_Theme/layout/default.xml
Any change I make manifests immediately, but unrelated parts of the page break at the same time. Most of what's in page-header disappears, and a new div called nav-sections appears with all our categories in it.
These exact changes occur regardless of how I alter default.xml -- even adding a character to a string causes them.
My hunch is it's a question of workflow, and I'm still unclear about when and how Magento 2 decides to create and serve files from pub/static, generated, and var/generated.
I should also note that I'm making these changes in production mode, and that running deploy doesn't fix anything.
What am I doing wrong here?
magento2 layout xml deployment
asked Mar 21 '18 at 15:03
mxtthxwmxtthxw
13
Fairly new to Magento 2. Working from a cloned version of another site and trying to make simple, cosmetic changes to the custom theme homepage here:
app/design/frontend/Vendor/Theme/Magento_Theme/layout/default.xml
Any change I make manifests immediately, but unrelated parts of the page break at the same time. Most of what's in page-header disappears, and a new div called nav-sections appears with all our categories in it.
These exact changes occur regardless of how I alter default.xml -- even adding a character to a string causes them.
My hunch is it's a question of workflow, and I'm still unclear about when and how Magento 2 decides to create and serve files from pub/static, generated, and var/generated.
I should also note that I'm making these changes in production mode, and that running deploy doesn't fix anything.
What am I doing wrong here?
magento2 layout xml deployment
magento2 layout xml deployment
asked Mar 21 '18 at 15:03
mxtthxwmxtthxw
13
asked Mar 21 '18 at 15:03
mxtthxwmxtthxw
13
edited Mar 21 '18 at 16:37
mxtthxw
asked Mar 21 '18 at 15:03
mxtthxwmxtthxw
13
asked Mar 21 '18 at 15:03
mxtthxwmxtthxw
13
asked Mar 21 '18 at 15:03
mxtthxwmxtthxw
13
13
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Inproduction mode, you need to deploy the static-content every time you make changes ! command :php bin/magento setup:static-content:deploy
– PЯINCƏ
Mar 21 '18 at 15:23
Thanks, but the layout breaks even before running thedeploycommand, and stays broken after running it.
– mxtthxw
Mar 21 '18 at 16:36
add a comment |
Inproduction mode, you need to deploy the static-content every time you make changes ! command :php bin/magento setup:static-content:deploy
– PЯINCƏ
Mar 21 '18 at 15:23
Thanks, but the layout breaks even before running thedeploycommand, and stays broken after running it.
– mxtthxw
Mar 21 '18 at 16:36
In
production mode, you need to deploy the static-content every time you make changes ! command : php bin/magento setup:static-content:deploy– PЯINCƏ
Mar 21 '18 at 15:23
In
production mode, you need to deploy the static-content every time you make changes ! command : php bin/magento setup:static-content:deploy– PЯINCƏ
Mar 21 '18 at 15:23
Thanks, but the layout breaks even before running the
deploy command, and stays broken after running it.– mxtthxw
Mar 21 '18 at 16:36
Thanks, but the layout breaks even before running the
deploy command, and stays broken after running it.– mxtthxw
Mar 21 '18 at 16:36
add a comment |
2 Answers
2
active
oldest
votes
I think that you have removed some properties from your custom default.xml or you have some errors on it please try this:
- Copy the original default.xml from the parent theme to the custom one.
Clear the content folder of :
pub/static,var/view_preprocessed,var/cacheLaunch this command :
php bin/magento setup:static-content:deploy -fCheck line by line the property who breaks you layout.
answered Mar 21 '18 at 16:55
PЯINCƏPЯINCƏ
8,37131144
add a comment |
It's simple solution.
by default Magento 2 just join file so core file with your get compile to one.
Block and component with are initialize with the same name as core will dissapear (after copying to theme folder).
You need to replace name in:
app/design/frontend/Vendor/Theme/Magento_Theme/layout/default.xml
Change name attribute only in: <block... or <container...
References don't need to be fixed. Be sure that name is uniquely across system.
Example:
From:
<block class="MagentoThemeBlockHtmlTitle" name="page.main.title" template="Magento_Theme::html/title.phtml"/>
To:
<block class="MagentoThemeBlockHtmlTitle" name="custom.page.main.title" template="Magento_Theme::html/title.phtml"/>
WARNING: This will create new block after existing one. If you need to
replace then replace<block...to<referenceBlock...as described
in
http://devdocs.magento.com/guides/v2.0/frontend-dev-guide/layouts/xml-instructions.html
answered Mar 21 '18 at 18:04
Patryk PadusPatryk Padus
1748
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f219263%2fany-change-to-default-xml-breaks-homepage-layout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think that you have removed some properties from your custom default.xml or you have some errors on it please try this:
- Copy the original default.xml from the parent theme to the custom one.
Clear the content folder of :
pub/static,var/view_preprocessed,var/cacheLaunch this command :
php bin/magento setup:static-content:deploy -fCheck line by line the property who breaks you layout.
answered Mar 21 '18 at 16:55
PЯINCƏPЯINCƏ
8,37131144
add a comment |
I think that you have removed some properties from your custom default.xml or you have some errors on it please try this:
- Copy the original default.xml from the parent theme to the custom one.
Clear the content folder of :
pub/static,var/view_preprocessed,var/cacheLaunch this command :
php bin/magento setup:static-content:deploy -fCheck line by line the property who breaks you layout.
answered Mar 21 '18 at 16:55
PЯINCƏPЯINCƏ
8,37131144
add a comment |
I think that you have removed some properties from your custom default.xml or you have some errors on it please try this:
- Copy the original default.xml from the parent theme to the custom one.
Clear the content folder of :
pub/static,var/view_preprocessed,var/cacheLaunch this command :
php bin/magento setup:static-content:deploy -fCheck line by line the property who breaks you layout.
answered Mar 21 '18 at 16:55
PЯINCƏPЯINCƏ
8,37131144
I think that you have removed some properties from your custom default.xml or you have some errors on it please try this:
- Copy the original default.xml from the parent theme to the custom one.
Clear the content folder of :
pub/static,var/view_preprocessed,var/cacheLaunch this command :
php bin/magento setup:static-content:deploy -fCheck line by line the property who breaks you layout.
answered Mar 21 '18 at 16:55
PЯINCƏPЯINCƏ
8,37131144
answered Mar 21 '18 at 16:55
PЯINCƏPЯINCƏ
8,37131144
answered Mar 21 '18 at 16:55
PЯINCƏPЯINCƏ
8,37131144
answered Mar 21 '18 at 16:55
PЯINCƏPЯINCƏ
8,37131144
8,37131144
add a comment |
add a comment |
It's simple solution.
by default Magento 2 just join file so core file with your get compile to one.
Block and component with are initialize with the same name as core will dissapear (after copying to theme folder).
You need to replace name in:
app/design/frontend/Vendor/Theme/Magento_Theme/layout/default.xml
Change name attribute only in: <block... or <container...
References don't need to be fixed. Be sure that name is uniquely across system.
Example:
From:
<block class="MagentoThemeBlockHtmlTitle" name="page.main.title" template="Magento_Theme::html/title.phtml"/>
To:
<block class="MagentoThemeBlockHtmlTitle" name="custom.page.main.title" template="Magento_Theme::html/title.phtml"/>
WARNING: This will create new block after existing one. If you need to
replace then replace<block...to<referenceBlock...as described
in
http://devdocs.magento.com/guides/v2.0/frontend-dev-guide/layouts/xml-instructions.html
answered Mar 21 '18 at 18:04
Patryk PadusPatryk Padus
1748
add a comment |
It's simple solution.
by default Magento 2 just join file so core file with your get compile to one.
Block and component with are initialize with the same name as core will dissapear (after copying to theme folder).
You need to replace name in:
app/design/frontend/Vendor/Theme/Magento_Theme/layout/default.xml
Change name attribute only in: <block... or <container...
References don't need to be fixed. Be sure that name is uniquely across system.
Example:
From:
<block class="MagentoThemeBlockHtmlTitle" name="page.main.title" template="Magento_Theme::html/title.phtml"/>
To:
<block class="MagentoThemeBlockHtmlTitle" name="custom.page.main.title" template="Magento_Theme::html/title.phtml"/>
WARNING: This will create new block after existing one. If you need to
replace then replace<block...to<referenceBlock...as described
in
http://devdocs.magento.com/guides/v2.0/frontend-dev-guide/layouts/xml-instructions.html
answered Mar 21 '18 at 18:04
Patryk PadusPatryk Padus
1748
add a comment |
It's simple solution.
by default Magento 2 just join file so core file with your get compile to one.
Block and component with are initialize with the same name as core will dissapear (after copying to theme folder).
You need to replace name in:
app/design/frontend/Vendor/Theme/Magento_Theme/layout/default.xml
Change name attribute only in: <block... or <container...
References don't need to be fixed. Be sure that name is uniquely across system.
Example:
From:
<block class="MagentoThemeBlockHtmlTitle" name="page.main.title" template="Magento_Theme::html/title.phtml"/>
To:
<block class="MagentoThemeBlockHtmlTitle" name="custom.page.main.title" template="Magento_Theme::html/title.phtml"/>
WARNING: This will create new block after existing one. If you need to
replace then replace<block...to<referenceBlock...as described
in
http://devdocs.magento.com/guides/v2.0/frontend-dev-guide/layouts/xml-instructions.html
answered Mar 21 '18 at 18:04
Patryk PadusPatryk Padus
1748
It's simple solution.
by default Magento 2 just join file so core file with your get compile to one.
Block and component with are initialize with the same name as core will dissapear (after copying to theme folder).
You need to replace name in:
app/design/frontend/Vendor/Theme/Magento_Theme/layout/default.xml
Change name attribute only in: <block... or <container...
References don't need to be fixed. Be sure that name is uniquely across system.
Example:
From:
<block class="MagentoThemeBlockHtmlTitle" name="page.main.title" template="Magento_Theme::html/title.phtml"/>
To:
<block class="MagentoThemeBlockHtmlTitle" name="custom.page.main.title" template="Magento_Theme::html/title.phtml"/>
WARNING: This will create new block after existing one. If you need to
replace then replace<block...to<referenceBlock...as described
in
http://devdocs.magento.com/guides/v2.0/frontend-dev-guide/layouts/xml-instructions.html
answered Mar 21 '18 at 18:04
Patryk PadusPatryk Padus
1748
answered Mar 21 '18 at 18:04
Patryk PadusPatryk Padus
1748
answered Mar 21 '18 at 18:04
Patryk PadusPatryk Padus
1748
answered Mar 21 '18 at 18:04
Patryk PadusPatryk Padus
1748
1748
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f219263%2fany-change-to-default-xml-breaks-homepage-layout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
In
production mode, you need to deploy the static-content every time you make changes ! command :php bin/magento setup:static-content:deploy– PЯINCƏ
Mar 21 '18 at 15:23
Thanks, but the layout breaks even before running the
deploycommand, and stays broken after running it.– mxtthxw
Mar 21 '18 at 16:36