-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to change Contacts Page <title>-Tag with XML #5231
Comments
@grasdaggel |
We are using Magento 2.0.4 Steps to reproduce
Expected result
Actual result
|
I've created an internal ticket MAGETWO-58021 for this issue and linked it to this one. |
Any update on this? Its been a while. |
Hello @grasdaggel, You should create a Then, change the title in it:
BUT you won't be able to translate it, the issue #2951 is still open and is talking about this bug. |
I have tried to change the page title of the Contacts page on Magento 2.2 with XML and it still not working. This issue has been open for over 1 year. When is it going to be fixed? |
@grasdaggel, thank you for your report. |
@grasdaggel, thank you for your report. |
Any solution? |
Hello @valeriaabo CustomModule/Module/etc/di.xml CustomModule/Module/Block/ContactUs/ContactForm.php
|
@Anantkprajapati : your solution worked very fine for me, thank you very much ! |
[Owls] Fix flaky unit tests
Dear community,
I think I may found something unwanted.
Theres a layout default.xml for the contact page in
vendor/magento/module-contact/view/layout/ => default.xml
Line 13:
<argument name="label" xsi:type="string" translate="true">Contact Us</argument>
When I make an duplicate of this file and copy it to
app/design/frontend/ThemeName/Namespace/Magento_Contact/layout/ => default.xml
and change the line from "Contact us" to something else, the changes make no change in the <title>-Tag of the page itself.
Is this intended or a bug, or am I just simply doing something wrong here. What I want to do is to change the <title>-Tag of the contact page, since its not translateable over the backend right now.
This could be a feature in future releases, in order to keep Magento translateable.
The text was updated successfully, but these errors were encountered: