3.1.0

What's Changed

• Allow computed value for configs by @wuifdesign in #22

New Contributors

• @wuifdesign made their first contribution in #22

Full Changelog: 3.0.2...3.1.0

3.0.2

Fixes #21 by forcing the external url (ArrayableLink) to be a string.

3.0.1

Remove all references to old Site configuration

3.0.0

Support for Statamic 5
Drops support for Statamic 3 and 4.

2.4.1

Removed Statamic 5 support.
This will be a major update to 3.0.0 (will be tagged shortly)

2.3.9

Corrects an issue (#18) when submit routes were created when single mode was defined.

2.3.8

Adds support for field mappings.

Refer to the revised default config file for the new mappings key that allows you to map Statamic's opinionated field handles with fields of your own:

    /*
    |--------------------------------------------------------------------------
    | Field mappings
    |--------------------------------------------------------------------------
    |
    | Allows you to map your blueprint fields with what Sitemapamic is expecting for controlling
    | the change frequency, inclusion and priority.
    |
    */
    'mappings' => [
        'include' => 'meta_include_in_xml_sitemap',
        'change_frequency' => 'meta_change_frequency',
        'priority' => 'meta_priority',
    ]

If you have your own fields, such as "sitemap_include", "sitemap_change_frequency" and "sitemap_priority", your config file needs:

    'mappings' => [
        'include' => 'sitemap_include',
        'change_frequency' => 'sitemap_change_frequency',
        'priority' => 'sitemap_priority',
    ]

If you don't want to change use the mappings, that's cool: there's nothing to do. Your existing setups will function as they always have.

2.3.7

So hurtful that you want to leave... and just to visit some other site?

Well fine then, I suppose entries with a "link" blueprint (automagically created by Statamic), that have a "redirect" property, and link to an external URL should be excluded from the sitemaps.

See Issue #12.

2.3.6

Hello, handsome. And we're talking to you, Statamic 4.

2.3.5

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.