Changelog

GraphQL Schema Updates

The Storefront GraphQL currencyCode enum now covers the full ISO 4217 code list, including precious metals, supranational units, and special-purpose codes.

Storefront GraphQL

• New currency codes: the currencyCode enum adds 15 ISO 4217 values. The enum is used wherever the schema accepts or returns a typed currency code, including the currency and currencies fields on Site, the defaultCurrency field on CurrencySettings, and the currencyCode argument on Product.prices, Variant.prices, Category.shopByPriceRanges, and Settings.giftCertificates.
  • National currency: VES (Venezuelan bolívar soberano).
  • Caribbean guilder: XCG, already available in the Admin and Account GraphQL schemas.
  • Precious metals: XAG (silver), XAU (gold), XPD (palladium), and XPT (platinum).
  • Supranational and fund units: XBA, XBB, XBC, and XBD (European bond market units), XDR (IMF special drawing rights), XSU (Sucre), and XUA (ADB unit of account).
  • Special-purpose codes: XTS (reserved for testing) and XXX (no currency).

For schema details, see the Storefront GraphQL API reference:

• currency field on the site query
• currencies field on the site query

Cleaner payment method listings

Payment method listing responses no longer include a small set of internal-only and duplicate payment method IDs that weren’t meant to be shown to merchants or shoppers.

• Fewer stray entries — test-only and superseded/duplicate payment method IDs are excluded from general listing results.
• Cart and order flows unaffected — payment methods tied to an existing cart, checkout, or order (for example, wallet buttons at checkout) continue to resolve normally; only general listing responses are filtered.

For details, see the Payments overview.

Fixed deleting and renaming legacy Image Manager images with uppercase letters or underscores in the filename

Deleting or renaming an Image Manager image uploaded before filenames were slugified, such as Home_Header_5.jpg, silently failed. The image stayed in the Image Manager with no error shown to the merchant.

• Legacy filenames are accepted again: delete and rename now validate the filename directly against path traversal, hidden files, and non-image extensions, instead of rejecting any name containing uppercase letters or underscores.
• Errors reach the browser: failed delete and rename requests now return their error message through the response instead of a body the browser couldn’t parse.

For details, see Image Manager.

View web page creation and modification dates

Merchants can now see when a web page was created and last modified in the control panel, making it easier to investigate unexpected store content changes.

• Page dates — View creation and last modification dates in the Web Pages list and page editor.
• Existing pages — Pages created before date tracking was enabled show an unavailable date instead of an estimated date.

For details, see the Pages overview.