Closed wbetalleluzd closed 3 months ago
@wbetalleluzd Please see #1256 , probably you published the package views previously and now you need to follow the complete Update Procedure. In other words, you need to update the previously published views in order to synchronize them with the new package version.
@wbetalleluzd Please see #1256 , probably you published the package views previously and now you need to follow the complete Update Procedure. In other words, you need to update the previously published views in order to synchronize them with the new package version.
Should this have been a major update rather than a minor? I suppose it's a tricky one where publishing is involved.
I have reverted the patch version v3.9.5 and released the minor version v3.10.0.
Oh, we could actually add backward compatibility by adding again LayoutHerlper::isPreloaderEnabled()
that just call the method that is now in the PreloaderHelper
class, but it will be a redundant method. What do you think @resslinger ?
On the other hand, if you want to access the new features, the review of previously published views is mandatory.
There was not any method called isPreloaderEnabled() in vendor\jeroennoten\laravel-adminlte\src\Helpers\LayoutHelper.php I added the method after line 24:
/**
* Check if the preloader animation is enabled.
*
* @return bool
*/
public static function isPreloaderEnabled()
{
return config('adminlte.preloader.enabled', false);
}
@SammyJoseph The method was moved to a new class, due to a split-out refactor, it's now on the PreloaderHelper.php
class:
Please, follow the update procedure and update your published views to sync them with the newest package version.
I solved it with the following: php artisan adminlte:install --only=main_views --force
Reference: https://github.com/jeroennoten/Laravel-AdminLTE/wiki/Updating
I solved it with the following:
php artisan adminlte:install --only=main_views --force
Reference: https://github.com/jeroennoten/Laravel-AdminLTE/wiki/Updating
@pervilla You should be careful about using --force
, because you will lose previous changes on the published views. You usually publish the views when you need to make a customization. So, it's always recommended to backup your set of published views before executing the previous command.
Closed, a solution to the issue was provided!
Just updated today.
I comment that and is running now.