Sitemap options will not be saved when they have not been changed AND they have not been saved before.
Note: Keeping the RC the same and bumping the minor version.
Add non-destructive template exclusions: 4981b9b5
Fix PW version comparison method; few other small fixes. Related commit: 6b296287
- Corrects PW version check
- Ignore options when not set by template
This is a new release candidate. Please test.
This release makes considerable changes to the way in which the module works. Here's the breakdown of notable changes in this release:
Instead of using actual attached fields on a page-by-page basis, the module now saves related data in a centralised manner to its own configuration, and page fields are built on the fly when needed.
This means that, when a template is defined in the module's config to use sitemap options and is later removed from the list, sitemap options for affected pages are not removed. Should the template be added to the list at a later stage, all saved options for pages belonging to that template are 'restored', simply meaning that the module will refer to them during the build process.
The only time sitemap options for a page are removed is when either the page in question is deleted after having been trashed, or when the module is uninstalled (everything gets deleted, in this case).
Due to a bug in Chrome (and possibly other browsers, though untested), the stylesheet is now turned on by default. Further, small aesthetic changes were made to the stylesheet, and a bug regarding the priority column was fixed.
Commit da42cb77 changelog:
- alter stylesheet
- use separate class-loader
- separate methods to traits
- bind options to module-config, instead of page-fields
- use stylesheet by default
- add debug trait
- remove gitignore stuff we don't need
The module now requires at least ProcessWire 2.8.16+ or 3.0.16+, due to the use of
As the module is in Beta, there is no upgrade path. You will need to uninstall Sitemap before installing it again if you would like to remove the redundant system fields. If it doesn't matter, then a normal upgrade will do fine.
Most stable at present. RC will be based on this. New docs site on the way as well.
(Not tagging as a pre-release, as it is actually production ready, for most sites anyway.)