Download the PHP package mmoollllee/filament-consent-control without Composer

On this page you can find all versions of the php package mmoollllee/filament-consent-control. 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 mmoollllee/filament-consent-control

Informations about the package filament-consent-control

Filament Consent Control

The Filament admin layer for consent-control: an opt-in settings page/form and a RichEditor plugin for embedding consent-gated iframes.

Part of a three-package stack:

Package Role
consent-control (npm) Framework-agnostic runtime + CSS.
laravel-consent-control Blade components, config, drivers, translations, server helpers.
filament-consent-control (this package) Filament settings UI + RichEditor consent-iframe plugin.

The frontend banner, blocking and configuration come from laravel-consent-control (installed automatically). A single config file is enough — this package only adds optional admin convenience on top.

Requirements

Installation

This pulls in laravel-consent-control. Publish its config and runtime assets, then set up the frontend as described in its README:

Register the plugin in your panel (does nothing by itself unless you opt in below):

Frontend assets

The banner, content blocking and JS runtime come from laravel-consent-control (pulled in automatically) — this package only adds the Filament admin + the RichEditor iframe plugin.

Recommended: bundle the runtime yourself so JS/CSS ship with your Vite build instead of extra requests, and render only the boot config on your site layout:

All options (published assets, no-Tailwind fallback, view publishing) are documented in the laravel-consent-control README.

To let visitors reopen the banner (e.g. from the privacy policy page), place a button with the consent-control--open class anywhere — the runtime binds it automatically:

Merge tag for editors (filament-cms)

On a site running mmoollllee/filament-cms that button is available to editors without typing HTML: the package registers itself with the CMS shortcode registry on boot — nothing to wire up.

The label defaults to filament-consent-control::consent.reopen_button — publish the translations to change it globally:

Without filament-cms (or on a version older than Shortcodes::registerMergeTag()) nothing is registered; Support\ConsentSettingsButton::html() renders the same markup for your own views.

Editing settings in Filament (opt-in)

By default settings are read from config/consent-control.php. To edit them at runtime, opt in to the eloquent driver and one of the two admin options below.

Option A — ready-made settings page

Adds a "Consent Settings" page to the panel that reads/writes the configured model.

Option B — embed the form in your own resource/page

RichEditor: embed consent-gated iframes

The toolbar gets an "Embed iframe" action (URL, consent category, width, height). Pasted YouTube/Vimeo links are auto-converted to privacy-friendly embed URLs (YouTube → nocookie). Stored iframes are rendered on the frontend as blocked .consent-message--wrapper markup (data-src) and only load once the visitor grants the chosen category — handled by the shared runtime, so make sure <x-consent-control-scripts /> is on the page.

License

MIT. See LICENSE.md.

All versions of filament-consent-control with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
filament/filament Version ^5.0
filament/forms Version ^5.0
filament/support Version ^5.0
mmoollllee/laravel-consent-control Version ^0.1
spatie/laravel-package-tools Version ^1.16
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 mmoollllee/filament-consent-control contains the following files

Loading the files please wait ...