During the regular october install using october:install, the user-defined password is overwritten with the random generated string password. Instead, now it uses random password only if the user-defined password defaults to *admin* and if a user did set a custom password, that is used instead.
Fixes a long standing issue where when safe mode is enabled and the line endings present in the templates differed from the line endings used by the user's browser it would cause safe mode to prevent saving any changes (even when those changes did not include real changes to the code property) because the user's browser would "helpfully" change the original line endings to the line endings of the browser before sending it back to the server.
The web based Updates controller avoids this issue by completing the migration step as a separate AJAX request from the step where the plugin files are installed, thus allowing for the plugins to be registered by the PluginManager prior to migrations being run. As the plugin:install CLI command runs in a single request, it is necessary to manually register the newly installed plugin prior to running any migrations for the plugin so that any dependencies introduced by the plugin are guaranteed to be available prior to plugin code being run.
`artisan theme:sync --target=database --force --paths=layouts/,pages/,partials/`
But at the moment it also synchronizes paths that should not be synchronized. For example: `content/static-pages/`. Because here the pattern applies to `pages/`.
The fix is that the pattern starts at the beginning of the line.
Co-authored-by: Heiko Böhme <hboehme@menadwork.com>
Provides the ability for developers to specify a custom message for bulk deletion actions, as well as a custom message when no records could be deleted due to missing selections or an altered query not finding any applicable records.
It appears that doing this in the "register" process can result, at times, in an exception to be thrown as the connection to the DB is not yet established.
Plugins now have the ability to define quick actions through a "registerQuickActions" method, which follows the same configuration as the "registerNavigation" method. It is still recommended and preferred that most plugin functionality be defined in their own main menu items, but this will allow a plugin to easily define a shortcut (or remove one).
