Skip to content
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

XML Sitemaps module - Remove Filename Prefix field #520

Closed
wpsmort opened this issue Sep 29, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@wpsmort
Copy link
Member

commented Sep 29, 2016

We should remove this field but make sure we support users who have entered something different from the default name (sitemap).

screen-capture

@wpsmort wpsmort added the Enhancement label Sep 29, 2016

@contactashish13

This comment has been minimized.

Copy link
Contributor

commented Jan 2, 2018

@wpsmort PR: #1449

Should something similar be supported for the video sitemap module as well?

contactashish13 added a commit to contactashish13/all-in-one-seo-pack that referenced this issue Mar 17, 2018

@michaeltorbert michaeltorbert added this to the 2.7 milestone Mar 22, 2018

@wpsmort wpsmort modified the milestones: 2.7, 2.8, 2.6 May 15, 2018

@wpsmort wpsmort removed their assignment May 21, 2018

@frankf2

This comment has been minimized.

Copy link

commented May 25, 2018

For those of us who manage private websites, e.g., HS Class, in addition to public sites, retaining the ability to specify a custom sitemap name is helpful. It allows us to use a caching program (W3 Total Cache - fixed) that reads the sitemap to prime the page cache, while not exposing (due to custom sitemap name) a list of pages, images, and associated page name content to outsiders, including malicious parties, due to the well-known sitemap name.

@michaeltorbert

This comment has been minimized.

Copy link
Member

commented May 25, 2018

Hi Frank,

Thank you for sharing your thoughts. This is certainly open for discussion, as we want to develop the plugin with the best interest of users in mind.

The reason we did this was to make the UI more less complex/confusing, and this is something that very few people would use, and in most cases isn't at all necessary.

Also, we were already planning on introducing a new API filter hook to let site owners change the sitemap name, in lieu of the option.
For those with sitemap names already changed prior to version 2.6, this will be respected, rather than reverting back to sitemap.xml

@frankf2

This comment has been minimized.

Copy link

commented May 25, 2018

Thanks for considering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.