Skip to content

Releases: mitydigital/statamic-sitemapamic

2.3.5

08 Jan 20:38
Compare
Choose a tag to compare

A logic update here which may impact your expected behaviour.

Prior to this update, past/future entries that were configured to be 'unlisted' were incorrectly included in Sitemapamic.

This update corrects this behaviour: only 'public' entries are shown: 'unlisted' and 'private' entries are not included when they are not visible on the main site itself.

2.3.4

27 Nov 22:56
7aed13c
Compare
Choose a tag to compare

Just a typo update, nothing too exciting here.

2.3.3

16 Oct 05:06
Compare
Choose a tag to compare

Updated composer to require PHP 8.1

2.3.2

05 Oct 01:48
Compare
Choose a tag to compare

If you're using our opinionated blueprint for your metadata fields, you may find that "Use default" is resulting in nothing being selected.

This update now allows you to use 'default' as the meta_include_in_xml_sitemap's default key. Using an empty string was too vague.

2.3.1

30 Aug 21:13
Compare
Choose a tag to compare

Well just a small one... 2.3.0's revised cache keys were not listed correctly when you had a single site and a single sitemap. It still cached - but the new list command was showing the wrong key.

This update corrects this.

2.3.0

30 Aug 03:57
Compare
Choose a tag to compare

We started a new multi-site project and needed better multi-site support in Sitemapamic. And now we're sharing this update with you too!

What's new:

  • full support for multi-site
  • new sitemapamic:list command

v2.3.0 improves support for multi-site Statamic sites, offering distinct sitemap creation and caching for multi-site configurations that are either on the same domain (i.e. a /en-au/ path on your main domain), or on an entirely different domain (i.e. https://en-au.your-domain.com).

This update keeps full support for sub-sitemaps too, introduced in v2.2.0.

We've also done some under-the-hood caching updates, and added a new sitemapamic:list command if you wanted to see what cache keys are available for you to individually clear.

2.2.0

08 Aug 23:27
3aae074
Compare
Choose a tag to compare

Adds support for splitting a large sitemap in to multiple sitemaps based on your collection and taxonomy routes. Thanks @jacksleight for this.

If you're not planning on using this feature, there's nothing for you to do.

By default, your existing setup will still work and create a single sitemap with all routes. To use multiple sitemaps, add the mode attribute to your config, and set it to multiple. See Configuration Options.

Also added is the ability to clear sub-sitemaps. See Clearing the cache.

2.1.1

26 May 06:51
Compare
Choose a tag to compare

Just a minor update to add a ttl config option if you'd like to have your Sitemapamic cache cleared more frequently.

The default is 'forever' - meaning until an Entry, Term, Taxonomy or Collection is changed.

With this update, you can now add ttl to your config file, and have your cache live for a set period of time.

Check out the source config file for full notes.

2.1.0

25 May 22:00
Compare
Choose a tag to compare

Welcome to a new day, and a new release.

This release adds a few new features:

  • support for global Taxonomy Term URLs
  • support for adding your own Dynamic Routes.

Check out the README for full details

This release also updates the events that trigger the sitemap cache to clear. The cache will be cleared automatically when any of the following are saved or deleted:

  • Entry
  • Term
  • Taxonomy (added in 2.1.0)
  • Collection (added in 2.1.0)

Finally, the SitemapUrl class has been renamed to SitemapamicUrl - there's a high chance you have not used this class yourself, but just in case you have, make sure you update your code too.

v2.0.1

16 May 00:13
Compare
Choose a tag to compare

Just a little housekeeping update - the config file is cleaned up and now lives in config/sitemapamic.php.

The upgrade process will try to move it for you.

Also added: when an Entry or Term is deleted, the Sitemapamic cache is cleared. Previously it was just on save.

You can also now publish the XML view template too - just in case you need to make changes - check out the readme for more details.