Quantcast
Channel: Issues for XML sitemap
Viewing all articles
Browse latest Browse all 1238

Consider moving non-constant configuration values for specific sitemap instances out of config.

$
0
0

I think it would be good to move out frequently changing non static elements from configuration to another storage space. I am thinking about items like max_filesize, updated stamp, links, and context from an xmlsitemap instance. These are constantly changing values (perhaps) and configuration synch will reset them to incorrect values.

Is this a direction you'd like to move forward with?

Background: We export our configuration to a known good configuration for production deployment. We will then bring production db down and run configuration imports locally for feature development ultimately resulting in configuration export as a feature branch is complete and ready to be merged into our production branch.

There are several xmlsitemap configuration entities that are exported. That is known good configuration and we like that. We also export our xmlsitemap instance. Because the instance config is always being updated by new nodes it will always overwrite good data with old data which is not desirable behavior.


Viewing all articles
Browse latest Browse all 1238

Trending Articles