Make domain for format_strawberryfield.iiif_settings.yml optional

[DiegoPino]

What?

This file is one that needs to be changed every time you deploy on a new server. Allowing a relative path that resolves against the current domain and protocol would allow that setting to be left as a partial path.

How?

Check if path is partial on validation, if so test calling the external server by prepending the current domain. If that works, on every call to a IIIF server (see Formatters that use this) append the current domain (needs to include ports if any/and protocol). Then remove all entries to fixed domains. Basically we don't want to keep domains here EXCEPT if the user really uses a different one.

[patdunlavey]

This fix should also apply to format_strawberryfield\Plugin\Field\FieldFormatter\StrawberryBaseFormatter display configs that currently store the full IIIF cantaloupe url (even if none is intentionally provided!).

[DiegoPino]

Yep Diego Pino Navarro Director of Digital Strategy Archipelago architect Metropolitan New York Library Council PO Box 2084 New York, NY 10108

…

On Oct 20, 2022, at 5:13 PM, Pat Dunlavey ***@***.***> wrote: This fix should also apply to format_strawberryfield\Plugin\Field\FieldFormatter\StrawberryBaseFormatter display configs that currently store the full IIIF cantaloupe url (even if none is intentionally provided!). — Reply to this email directly, view it on GitHub <#229 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABU7ZZ3TAE5XD2FP6F62W5LWEGRXHANCNFSM6AAAAAARDP3MF4>. You are receiving this because you authored the thread.