Home

Awesome

THIS BUNDLE IS NOT MAINTAINED ANYMORE

The used AdminLTE version is old. Both: supported Symfony and PHP version are EOL.

Issues, bug requests and even pull requests will not neither be answered nor merged.

If you are looking for a modern alternative, check out the Tabler bundle at: https://github.com/kevinpapst/TablerBundle

Latest Stable Version Total Downloads License

AdminLTE Bundle for Symfony

This repository contains an upgraded version of the AvanzuAdminThemeBundle, bringing the AdminLTE theme to Symfony 4.

Introduction

Minimum requirements

Compatibility:

Version 3.x should be compatible with Symfony 5 and PHP 8, please leave your feedback.

Features

Some of the main features of this theme bundle:

Installation with Symfony Flex

Installation using Symfony flex:

composer config extra.symfony.allow-contrib true
composer req "kevinpapst/adminlte-bundle:^3.0"

Installation with Composer

Installation using the "traditional" composer approach:

   composer require kevinpapst/adminlte-bundle ^3.0

Afterwards copy the default config to your config/packages/ directory:

cp vendor/kevinpapst/adminlte-bundle/config/packages/admin_lte.yaml config/packages/

Then, enable the bundle by adding it to the list of registered bundles in the config/bundles.php file of your project:

<?php

return [
    // ...
    KevinPapst\AdminLTEBundle\AdminLTEBundle::class => ['all' => true],
];

Difference between AdminLTEBundle and AvanzuAdminThemeBundle

First and foremost: the original repository has a strong backward compatibility in mind, maintenance is only done if Symfony 2 and 3 compatibility is kept (e.g. here).

That means you don't get the new shiny stuff for SF4. As I work on a Symfony 4 project, utilizing webpack-encore I needed a solution.

First I tried to sent PRs for the original repository, but those were not always accepted eg. here. As I really needed an upgraded version, I tried to manage a branch in a fork for a couple of weeks, but that wasn't working well and I found myself overwriting more and more stuff in my project until there was a point were I had to choose between:

  1. doing all the changes in my project
  2. doing the changes in my forked repository and having "dev-" entries in my composer.json
  3. cleanup the fork, merge it with my project changes and release it for the community

The choice 3 was easy and obvious for me: I am doing the work now in this repository with a fresh start and the chance for backward-compatibility breaks (for the users migrating from the AdminThemeBundle).

Main differences

This repository was created from the original master, but with a lot of enhancements on top:

Migration from AvanzuAdminTheme

Be aware: I decided to change some project internals and got rid of some features from the original AdminThemeBundle. I found the all-in-one solution to be more problematic then helpful at several places, so I took the chance to update it to my own interpretation of a theme bundle.

If you previously used the AvanzuAdminTheme you will not be able to "just replace" the composer package. Plan ahead, you will need (depending on the size of your project) a couple of hours for the migration.

I migrated my own project within ~4 hours, but I had to move a lot of the customization to the bundle (e.g. the webpack-encore build) in the same time. See the PRs #202 and #206 for migration examples.

License and contributors

Published under the MIT, read the LICENSE file for more information.

This repository is based on the work of AdminThemeBundle, please check their contributor list as well and give them a star!