sleeping-owl / admin-lte-template

AdminLTE template for sleeping-owl/admin

AdminLTE template for sleeping-owl/admin

AdminLTE is a free bootstrap admin template from Almsaeed Studio. ###Important Notes: ######Currently only works on sleeping-owl/admin with development tag

Installation

1. Require this package in your composer.json and run composer update:

   "sleeping-owl/admin-lte-template": "dev-master"
   

2. After composer update, add service providers to the config/app.php

   'SleepingOwl\AdminLteTemplate\AdminLteTemplateServiceProvider',
   

3. Publish assets:

   $ php artisan vendor:publish --provider=SleepingOwl/Admin/AdminLteTemplateServiceProvider --tag=assets-lte
   

4. Change current template in admin config (config/admin.php):

   'template'                => 'SleepingOwl\AdminLteTemplate\Template',
   

Copyright and License

Admin was written by Sleeping Owl for the Laravel framework and is released under the MIT License. See the LICENSE file for details.

admin-lte-template's Issues

Handle Notification message

I made a pull request #4 to handle notification message in Admin.

To display notification, we have to flash an error_message or success_message on the session.

Good for displaying to the user that an action have been done or not.

Nothing to publish for tag [assets-lte]

After this

php artisan vendor:publish --provider=SleepingOwl/Admin/AdminLteTemplateServiceProvider --tag=assets-lte

have an error

Nothing to publish for tag [assets-lte].

'template' config option

Hi,

Have been trying to install this, followed this procedure:

1. Added dependency to composer
2. Added service provider
3. Published assets

Next, I looked to add the line into config/admin.php for the template - but I couldn't see an existing array key for this? I tried adding it anyway, but it didn't seem to make a difference. Am I missing something here? I can switch out the bladePrefix to admin-lte:: but this causes errors that I'm guessing that the view() method in Template.php solves.

Thanks for your help!

Publish assets command not working

Hello,

I use admin V3 using Laravel 5.1 and after I run the command:
php artisan vendor:publish --provider=SleepingOwl/Admin/AdminLteTemplateServiceProvider --tag=assets-lte

It gives me this message:
Nothing to publish for tag [assets-lte].

I follow the process step by step.

In app/config.php I add this line for provider:
SleepingOwl\AdminLteTemplate\AdminLteTemplateServiceProvider::class,

Is there something I miss?

Thanks.

Not work setting in config/admin.php

Change current template in admin config (config/admin.php):

'template' => 'SleepingOwl\AdminLteTemplate\Template',

Asset folder "plugin" will not be published

Hi,

currently I'm trying to install the admin lte template.
After running the publish command I have checked the public folder.

in public/packages/sleeping-owl/admin/default

I have only the following folders:

• js
• fonts
• css

In the Repo and in the vendor folder I have the following folders:

• bootstrap
• css
• js
• plugins

Looks like that something is wrong with the publish command :)

Readonly attribute not supported

Using this template the "readonly" attribute is not supported.

FormItem::text('id', 'USER Id')->readonly(true),

For example text.blade.php from

<div class="form-group {{ $errors->has($name) ? 'has-error' : '' }}">
    <label for="{{ $name }}">{{ $label }}</label>
    <input class="form-control" name="{{ $name }}" type="text" id="{{ $name }}" value="{{ $value }}">
    @include(AdminTemplate::view('formitem.errors'))
</div>

should be changed in

<div class="form-group {{ $errors->has($name) ? 'has-error' : '' }}">
    <label for="{{ $name }}">{{ $label }}</label>
    <input class="form-control" name="{{ $name }}" type="text" id="{{ $name }}" value="{{ $value }}" @if(isset($readonly))readonly="{{ $readonly }}" @endif>
    @include(AdminTemplate::view('formitem.errors'))
</div>

Column Action - button position

The column action is placed in a wrong position in the AdminLteTemplate.

TemplateDefault

AdminLteTemplate

I am working to solve this issue.