« Changelog History


CraftCMS v3.0.23 Release Notes

Release Date: 2018-09-04 // over 5 years ago

  • 🔄 Changed

    • 💻 Browser-based form validation is now disabled for page forms. (#3247)
    • 👍 craft\base\Model::hasErrors() now supports passing an attribute name with a .* suffix, which will return whether any errors exist for the given attribute or any nested model attributes.
    • ➕ Added json to the default allowedFileExtensions config setting value. (#3254)
    • 0️⃣ Exception call stacks now collapse internal Twig methods by default.
    • 👻 Twig exception call stacks now show all of the steps leading up to the error.
    • Live Preview now reloads the preview pane automatically after an asset is saved from the Image Editor. (#3265)

    🗄 Deprecated

    • 🗄 Deprecated craft\services\Matrix::getContentTableName(). craft\fields\Matrix::$contentTable should be used instead.

    ✂ Removed

    • ✂ Removed craft\services\Matrix::getParentMatrixField().

    🛠 Fixed

    • 🛠 Fixed a bug where element selection modals could be initialized without a default source selected, if some of the sources were hidden for not being available on the currently-selected site. (#3227)
    • 🛠 Fixed a bug where edit pages for categories, entries, global sets, and users weren’t revealing which tab(s) had errors on it, if the errors occurred within a Matrix field. (#3248)
    • 🛠 Fixed a SQL error that occurred when saving a Matrix field with new sub-fields on PostgreSQL. (#3252)
    • 🛠 Fixed a bug where custom user fields weren’t showing up on the My Account page when running Craft Solo edition. (#3228)
    • 🛠 Fixed a bug where multiple Matrix fields could share the same content table. (#3249)
    • 🛠 Fixed a “cache is corrupted” Twig error that could occur when editing or saving an element if it had an Assets field with an unresolvable subfolder path template. (#3257)
    • 🛠 Fixed a bug where the Dev Mode indicator strip wasn’t visible on Chrome/Windows when using a scaled display. (#3259)
    • 🛠 Fixed a SQL error that could occur when validating an attribute using craft\validators\UniqueValidator, if the target record’s find() method joined in another table.