Page settings reverting back to default when using a custom user template

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

I have created a custom template that has some of the Format > Page settings tweaked.

Changes:

• Stave space: 1.400mm
• Page margins (horizontal): 13.00mm
• Bottom page margin: 9.50mm

However, every time I use this template, the page settings are reverted back to default. All of the Format > Style is kept however this isn't.

I have also tried this on the latest nightly build for windows and the same still happens. I have even tried making a new template only changing the page settings in both the latest public release and nightly build and page settings still do not save.

I have attached the template below.

Extra information can be found here about other people using the template https://musescore.org/en/node/381351#comment-1301090

Supporting files, videos and screenshots

Layout.zip
(inside is the .mcsz template)

What is the latest version of MuseScore Studio where this issue is present?

MuseScore 4.5.2

Regression

I was unable to check

Operating system

Windows 11

Additional context

Note: I have used a custom font so some may default back to Edwin.

Quoting Marc Sabetella from the MuseScore Forums
"Seems to relate to a Letter vs A4 difference, somehow. I can reproduce the issue when creating a score from your template - which is explicitly set to A4 - but not if I resave the template with Letter as the page size. I'm in the US, so score created from templates set to A4 automatically convert to Letter on my my system (by design). But somehow in that conversion, it seems the other page settings are lost. That's a bug; please report it on GitHub. Not sure if you intend that to be A4 or it you live in a region where A4 is the default (and hence the opposite conversion happens), but probably whatever you are seeing is related."

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible