- Can I use kevinpapst/tabler-bundle in a Laravel application?
- No. TablerBundle is built exclusively for Symfony and depends on Symfony's Twig extensions, routing, security and asset components, so it will not install or run as a Laravel package. Treat it as reference material only: you can study its Twig macros, layouts and menu/notification patterns and rebuild them with Blade components. If you commit to it in a Laravel estate, you must budget for a full port rather than a Composer install. Confirm stack alignment before any commitment.
- What Symfony and PHP versions does TablerBundle require?
- The bundle requires Symfony 6.0 or newer and PHP 8.1 or newer; those constraints are restated in release 2.4.1. Symfony 7.x support is not confirmed in the published constraints, which is the largest long-term compatibility bet for the package. If your project is already on Symfony 7 or plans to upgrade soon, verify the composer.json constraints and the maintainer's roadmap before adopting.
- How do I install and configure the Tabler bundle in a Symfony project?
- Run composer require kevinpapst/tabler-bundle, then copy the default configuration into config/packages/tabler.yaml and adjust it to your layout choices. After that you extend the bundle's base templates from your own controllers and Twig views, so the admin chrome and Twig helpers are available immediately. A separate TablerBundle-Demo repository provides a ready-made scaffold you can use as a starting point for new projects.
- Which Tabler.io version does the bundle support, and is Tabler 1.5 compatible?
- Version 2.4.1 explicitly pins the bundle to Tabler 1.4 or lower and is not compatible with Tabler 1.5. That means upstream 1.5 bug fixes, accessibility improvements and security patches are not reachable through the bundle, and any team already on 1.5 assets faces a downgrade or a fork. The pin signals an unresolved upstream incompatibility, so expect a later 2.5.x-style release to lift it with accompanying template and CSS class churn. Ask whether the pin is tracked in an issue with a target removal release before you adopt.
- Does TablerBundle work with Webpack Encore, Vite or the Symfony Asset component?
- The bundle ships Webpack Encore support for building its assets and also works with Symfony's asset component, so you do not have to adopt Encore to use it. Vite is not covered by the bundle's own tooling, meaning you would wire up Tabler 1.4 static assets through your existing pipeline yourself. Decide early how those pinned static assets will be integrated, because that choice affects upgrades when the Tabler version ceiling is lifted.
- What layouts, macros and security pages ship with the bundle?
- It provides two main backend layouts, a vertical and a horizontal one, plus security layouts for login, forgot password and account registration. On top of that you get a large set of Twig helpers, filters, embeds, macros and includes that speed up templating and simplify future upgrades. The theme is built on Bootstrap 5 with FontAwesome 5 icons and no frontend JavaScript framework, so it is plain HTML, CSS and JS rather than a SPA.
- How do I add menu entries, notifications and tasks to the admin interface?
- Menu entries, tasks and notifications are handled in an event-driven way, so you register listeners or subscribers that push items into the bundle's menu and notification services instead of editing templates. This keeps your application code separate from the theme and survives bundle upgrades. A ContextHelper is also available for dynamic layout changes, for example switching layout based on user preferences.
- Can I override the bundle's Twig templates without breaking upgrades?
- Yes, standard Symfony bundle template overriding applies, but expect real customization overhead because the bundle leans heavily on its own templates and macros. If your project already has a UI layer or custom Twig extensions, the shipped helpers and includes can collide with your naming and markup conventions, so plan a partial-adoption strategy rather than a full replacement if you want to limit churn. Security layouts in particular usually need tailoring to match existing OAuth, token or API authentication flows.
- Which languages are the TablerBundle translations available in?
- The bundle ships translations for English, German, Italian, Czech, Spanish, Russian, Arabic, Finnish, Japanese, Swedish, Brazilian Portuguese, Dutch, French, Turkish, Danish, Chinese, Slovak, Basque, Polish, Esperanto, Hebrew and Romanian. Translation updates arrive through the project's Hosted Weblate pipeline, which indicates an active community localization process. Coverage and completeness vary per locale, so verify the specific strings you need before committing to a non-English admin rollout.
- Is TablerBundle actively maintained, and what is the risk of adopting it?
- The bundle is maintained by kevinpapst with recent external contributions, including Weblate translation updates and community pull requests, and 2.4.1 is a dependency-pin and localization release rather than a capability release. The main risks are the Tabler 1.4 version ceiling, a hard dependency on Symfony 6.0+ and PHP 8.1+, and unconfirmed Symfony 7.x support. Bus factor is a single primary maintainer, so factor release cadence and your ability to fork into your long-term maintenance plan.