CraftCMS v4.2.5 Release Notes

Release Date: 2022-09-20 // over 1 year ago
  • ➕ Added

    • ➕ Added craft\helpers\Image::targetDimensions().

    🔄 Changed

    • Edit Asset pages now show the “View” button for all file types, not just images, PDFs, and text files. (#11936)

    ✂ Removed

    • ✂ Removed the Punycode PHP library. (#11948)

    🛠 Fixed

    • 🛠 Fixed a bug where image transforms weren’t always getting applied properly to all animation frames. (#11937)
    • 🛠 Fixed a bug where animated WebP images would lose their animation frames when transformed. (#11937)
    • 🛠 Fixed a bug where image transform dimensions could be calculated incorrectly when upscaleImages was false. (#11837)
    • 🛠 Fixed a bug where the users/send-password-reset-email action wasn’t passing errors back to the template. (#11933)
    • 🛠 Fixed an error that occurred when setting a non-numeric width or height on an image transform. (#11837)
    • 🛠 Fixed a bug where the database connection wasn’t being configured properly when fluent config methods and environment variable overrides were being used in combination. (#11941)
    • 🛠 Fixed a bug where slideouts lost their shadows when focused.
    • 🛠 Fixed a bug where relatedTo* arguments weren’t supported by children fields in GraphQL. (#11918)
    • 🛠 Fixed a bug where Image Editor and slideout action buttons were obstructed when the Debug Toolbar was enabled. (#11965)
    • Fixed an error that occurred when installing Craft when MySQL’s sql_require_primary_key setting was enabled. (#11374)
    • 🛠 Fixed a bug subfolders created by Assets fields could be reported as missing when updating asset indexes, even if they contained assets. (#11949)
    • 🛠 Fixed a PHP error that could occur in a potential race condition when calling craft\helpers\FileHelper::clearDirectory().
    • 🛠 Fixed a bug where Structure section entries that were duplicated via the “Save as a new entry” action on a provisional draft weren’t being placed within the structure properly.
    • 🛠 Fixed a bug where element’s searchScore properties would be set to null when their original score was below 1, rather than rounding to 0 or 1. (#11973)