Optional file name components - Feature requests https://www.oltoolkit.com/forum/feature-requests/optional-file-name-components/ Support Forum en-GB Tue, 09 Jun 2026 15:21:08 +0000 wpForo 60 RE: Optional file name components https://www.oltoolkit.com/forum/feature-requests/optional-file-name-components/#post-30 Thu, 13 Jun 2024 04:33:01 +0000 All good - this one is easy to work around, so not a priority I don't think

]]> Feature requests Luke Speedy-Hutton https://www.oltoolkit.com/forum/feature-requests/optional-file-name-components/#post-30 RE: Optional file name components https://www.oltoolkit.com/forum/feature-requests/optional-file-name-components/#post-28 Thu, 13 Jun 2024 04:31:41 +0000 So Arranger and Orchestrator fields already do this. Interesting question for the other fields. I'll have a think about the ramifications of this - we use the templates to parse the file names back to set things like default print settings for the part e.g. number of copies, paper size etc. so this is potentially not a trivial change.

]]> Feature requests Support https://www.oltoolkit.com/forum/feature-requests/optional-file-name-components/#post-28 Optional file name components https://www.oltoolkit.com/forum/feature-requests/optional-file-name-components/#post-27 Thu, 13 Jun 2024 04:13:23 +0000 We sometimes, but not always, include the edition of a work. But if I include the edition component in my filename but leave it blank, I can't export the files. Is it possible to have empty fields (such as arranger) left blank without altering the components every time?

This may need to apply to spaces/punctuation following them as well.

]]> Feature requests Luke Speedy-Hutton https://www.oltoolkit.com/forum/feature-requests/optional-file-name-components/#post-27