CraftCMS v3.4.19 Release Notes

Release Date: 2020-05-12 // almost 4 years ago
  • ➕ Added

    • ➕ Added craft\fields\BaseRelationField::inputSiteId().
    • ➕ Added craft\helpers\App::isNitro().

    🔄 Changed

    • 0️⃣ The web-based installer now defaults the database server to 127.0.0.1 instead of localhost.
    • 🌐 The web-based installer and setup command now skip asking for the database server name/IP, username, and password, if they are able to detect that Craft is running within Nitro.
    • 📜 craft\web\View::renderObjectTemplate() now injects {% verbatim %} tags around inline code and code blocks, preventing their contents from being parsed by Twig.
    • ⚡️ Updated jQuery to 3.5.1. (#6039)

    🛠 Fixed

    • 🛠 Fixed a 403 error that occurred when a user double-clicked on an asset immediately after selecting it in an Assets field, if they didn’t have access to the primary site. (#5949)
    • 🛠 Fixed a bug where resave/* commands’ output didn’t take the limit into account. (#6036)
    • 🛠 Fixed an error that could occur when processing project config changes that included deleted user groups. (#6011)
    • 🛠 Fixed a bug where Date/Time fields weren’t taking their “Show date”/“Show time” settings into account when displaying their values in element indexes. (#6038)
    • 🛠 Fixed a PHP error that occurred when requesting the GraphQL API with a token that didn’t have a schema assigned to it. (#6043)
    • 🛠 Fixed a bug where Single sections’ entry type handles weren’t getting updated if both the section name and handle changed at the same time. (#6044)
    • 🛠 Fixed a bug where updating a transform would not bust the generated transform caches on volumes with the expires setting set.
    • 🛠 Fixed a bug where it wasn’t possible to create new Dashboard widgets that had settings.
    • 🛠 Fixed a bug where relational fields weren’t always showing related elements in the selected site on element indexes. (#6052)
    • 🛠 Fixed various UI bugs related to breaking changes in jQuery 3.5. (#6049, #6053)
    • 🛠 Fixed a bug where disabled multi-site entries would become enabled if they became single-site entries per a change to their section’s Propagation Method setting. (#6054)
    • 🛠 Fixed a bug where it wasn’t possible to double-click on Single entries to edit them. (#6058)
    • 🛠 Fixed a bug where querying for disabled elements wouldn’t include elements that were disabled for the current site.

    🔒 Security

    • 🛠 Fixed a bug where database connection details were getting cached. (#6047)