Download the PHP package wotz/filament-admin-bar without Composer

On this page you can find all versions of the php package wotz/filament-admin-bar. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of wotz/filament-admin-bar

Informations about the package filament-admin-bar

Admin bar for filament

This package will add an admin bar to the frontend, only visible for logged in Filament users.

Tabs

Five tabs ship with the package, and each decides for itself whether it has anything to show:

Tab Shows
SEO What the page reports to search engines
Translatable strings The copy on this page, editable in place
Media The images on this page, and which of them have no alt text
Records The CMS records behind this page, linked to their edit screens
Redirect Only on a 404: create a redirect from the URL that just failed

Only the active tab is rendered. Listing a tab therefore costs what it costs when somebody opens it, not on every frontend request an admin makes.

Telling the bar which record a page is

Detail pages need no wiring: anything bound to the route is picked up, so the "Edit page in CMS" action and the Records tab work on them out of the box.

Index and home pages resolve their record some other way, so they say so — usually from the one place an application already funnels them through:

The header action opens the primary record. Everything else is a click away in the Records tab.

Sharing the corner

The closed trigger sits against the bottom edge, and so does everything else that wants to be permanent — a dev toolbar, a cookie strip. It steps along the edge to clear anything small parked in its corner, and takes itself out of the way entirely while something spans that edge, coming back when it closes. Laravel Debugbar does all three: a corner button, a full-width strip, and an open panel.

inset_inline sets where it rests when the corner is free.

Telling the bar which images a page draws

The Media tab lists the images the page loaded and flags the ones with no alt text. A page draws them from a great many templates and from one model, so the model is where to say it:

Nothing is collected outside a page view, so a queued job that walks the whole library costs nothing.

The redirect tab

It only appears on a 404, which is the one moment the old URL is in front of you. Your error view has to say so before the layout renders the bar:

Editable strings

The package ships a Translator that records which keys a page resolved, so the Translatable strings tab knows what to offer. TranslationLoader swaps it in for Laravel's own — register it in bootstrap/providers.php, before anything that resolves a translation:

Keys are collected for the whole page view, including the lazy Livewire components and deferred islands it renders afterwards, and the list starts empty on the next page. Nothing is recorded for a visitor who is not signed in to the panel.

Installation

You can install the package via composer:

DO NOT forget to publish the CSS files, or the bar will not be visible:

You can publish the config file with:

This is the contents of the published config file:

Optionally, you can publish the views using

Usage

Documentation

For the full documentation, check here.

Testing

Changelog

Please see CHANGELOG for more information on what has changed recently.

Upgrading

Please see UPGRADING for more information on how to upgrade to a new version.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

If you discover any security-related issues, please email [email protected] instead of using the issue tracker.

License

The MIT License (MIT). Please see License File for more information.

All versions of filament-admin-bar with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
filament/filament Version ^4.0|^5.0
illuminate/contracts Version ^12.0|^13.0
livewire/livewire Version ^3.2|^4.0
spatie/laravel-package-tools Version ^1.12
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wotz/filament-admin-bar contains the following files

Loading the files please wait ...