When removing a plugin via CLI or rolling back all DB migrations, we will now require the user to type out the plugin name (or "DELETE" for "winter:down") as a confirmation in order to proceed. This ensures that the user is well aware of what they are doing.
The "plugin:remove" command has now been added a "--no-rollback" option. When used, the plugin files will be removed, but the DB will remain untouched, allowing people to remove a plugin without losing their data.
Refs: https://github.com/wintercms/wn-translate-plugin/issues/13#issuecomment-988364253
Fixes#350. Refs https://github.com/laravel/framework/pull/38724. Final solution in v1.2 will be to extend the base Laravel Cache serviceprovider and make it no longer a deferred provider as well as consolidating the MemoryCache implementations currently present in QueryBuilder, Halcyon Models, and the Halcyon ServiceProvider into the Winter Cache service provider.
These values have always traditionally been strings, but some custom implementations use integers (eg. for ID selections) which did not work previously.
This coerces both the selected items and available items to strings for comparison, which should allow integers to be used.
Fixes https://github.com/wintercms/winter/issues/351
To allow more flexibility of where we can put handler methods for dynamic properties in the Inspector, we should try and call the given class' constructor with whatever required parameters it needs. The current implementation assumes that one argument will be provided to any given property class (with the value given being null). Ideally, we should make these methods static and have a look at this more thoroughly later, but this is a useful compromise for now.
Credit to @RomainMazB. Documented in https://github.com/wintercms/docs/pull/34. Proposed in #201.
Co-authored-by: Luke Towers <github@luketowers.ca>
Co-authored-by: Ben Thomson <ben@abweb.com.au>
Co-authored-by: Jack Wilkinson <me@jackwilky.com>
We'll prompt people to upgrade to the next major version, but if they opt to stay on their current branch, to ensure that they don't end up filled with extraneous info, we'll just show the changelog of their current branch and those branches below the current one.
Chrome exhibits an issue in stretch mode with the double min-height definition of the surrounding field container and the editor writing area where the height is interpreted incorrectly and the editor content is clipped if the viewport shrinks the editor below the minimum height.
This fix will define a minimum height just for the editor writing area based on the "size" option, and will still allow stretch to increase the height of the editor further as required.
Partially reverts the "improvements" in d7117f9cb2
Fixes https://github.com/wintercms/winter/issues/322
Prevents impersonators from having access to any permissions on the impersonated user's account that they don't already have access to
Prevents super users from being impersonated
Allows skin developers to target the body class in the auth layout for specific pages within the Auth controller. The sign in page already specified a "signin" class, so this brings the other pages into parity.
