Sitemap Enable submission to robots.txt has wrong URL

[dverkade]

Preconditions

1. Magento 2.3.5
2. Have nginx pointing to the /pub folder as root

Steps to reproduce

1. Go to Marketing -> Sitemap and create a sitemap
2. Enable "Submit sitemap to robots.txt" under Stores -> Configuration -> Sitemap XML

Expected result

1. Sitemap does not have the "pub" folder in the URL
2. Robots.txt does not reference the "pub" folder in the sitemap URL

Actual result

1. Sitemap has the /pub/ folder in it, see screenshot: https://2667042cf8efa924a5b80b43b37079a1-2-4-develop.instances.magento-community.engineering/pub/sitemap.xml
2. Robots.txt has reference to the sitemap with /pub/ in it: https://2667042cf8efa924a5b80b43b37079a1-2-4-develop.instances.magento-community.engineering/pub/sitemap.xml

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @dverkade. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[dverkade]

@magento I am working on this

[dverkade]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @dverkade. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @dverkade, here is your Magento Instance: https://2667042cf8efa924a5b80b43b37079a1-2-4-develop.instances.magento-community.engineering
Admin access: https://2667042cf8efa924a5b80b43b37079a1-2-4-develop.instances.magento-community.engineering/admin_c808
Login: 91953b72
Password: c83e2ac83107

[m2-assistant]

Hi @ihor-sviziev. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[ihor-sviziev]

Hi @dverkade,
In 2.4-develop branch non-pub folder installation was already removed at all in 640cad5#diff-2323d6157444b3cf24d4d76635f27185a4e6ad979b0ec2af53e6592d3ca465d5R13
but till Magento 2.4.2 you can add following thing to your env.php file and it should solve the issue:

'directories' => [
    'document_root_is_pub' => true
]

https://devdocs.magento.com/guides/v2.4/install-gde/tutorials/change-docroot-to-pub.html#3-update-the-envphp-file

Could you confirm that issue is fixing by adding this flag?

[ihor-sviziev]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @ihor-sviziev. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @ihor-sviziev, here is your Magento Instance: https://2667042cf8efa924a5b80b43b37079a1-2-4-develop.instances.magento-community.engineering
Admin access: https://2667042cf8efa924a5b80b43b37079a1-2-4-develop.instances.magento-community.engineering/admin_9e54
Login: fc614768
Password: f82903d39705

[ihor-sviziev]

Just re-checked 2.4-develop branch on test instance - this issue IS reproducing on 2.4-develop.

1. ✔ Changed "Enable Submission to Robots.txt" to "Yes":
   

2. ✔Created & generated sitemap.xml
   ❌Generated URL contains /pub/
   

3. ❌ in robots.txt we have incorrect link to sitemap.xml file
   

[magento-engcom-team]

@ihor-sviziev Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

✅ Confirmed by @ihor-sviziev
Thank you for verifying the issue. Based on the provided information internal tickets MC-39075 were created

Issue Available: @ihor-sviziev, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[dverkade]

@ihor-sviziev, thanks for verifying. We've tested this on our development environment as well and can verify that it doesn't work currently.

[dani97]

@ihor-sviziev verified it today on 2.4-develop and it is working fine

[dani97]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @dani97. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @dani97, here is your Magento Instance: https://2667042cf8efa924a5b80b43b37079a1-2-4-develop.instances.magento-community.engineering
Admin access: https://2667042cf8efa924a5b80b43b37079a1-2-4-develop.instances.magento-community.engineering/admin_bf3d
Login: 74f54116
Password: 87724ed77e56

[dani97]

I could reproduce this in magento instance but not in my local 2.4-develop branch, I have disabled 'document_root_is_pub' setting also

[Bartlomiejsz]

@ihor-sviziev just one note, not sure if it's still the case but I remember that some time ago test instances created here on github had document root placed in ROOT, so one directory above pub (which was really weird since it was not according to Magento best practices).

It would be worth checking if that's still the case since it could be the only configuration in which pub is still added to the url

[ihor-sviziev]

@sidolov @sivaschenko @gabrieldagama,
It seems like an issue with test instances or related to a specific configuration used there. People are saying that it's not reproducing on local env while reproducing on test instances.
Could you look at it?
Thank you!

[dverkade]

@ihor-sviziev as mentioned in the initial ticket description this issue is reproducible local and on production environments. Test instance from Magento Github reflect this as well, so this is an active issue that needs to be worked on.

[Alexander-Khohklov]

@magento I am working on this

[m2-assistant]

Hi @Alexander-Khohklov! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[Alexander-Khohklov]

@magento add to contributors team

[m2-assistant]

Hi @Alexander-Khohklov! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[Alexander-Khohklov]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @Alexander-Khohklov. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @Alexander-Khohklov, here is your Magento Instance: https://593d30564ad293287b2b8ebcb68c0711.instances.magento-community.engineering
Admin access: https://593d30564ad293287b2b8ebcb68c0711.instances.magento-community.engineering/admin_c706
Login: 97b7849d
Password: b45dc86a15bd

[Balex70]

More than two years and this issue is still open :(