Download the PHP package justinholtweb/craft-homer without Composer

On this page you can find all versions of the php package justinholtweb/craft-homer. 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 justinholtweb/craft-homer

Informations about the package craft-homer

Homer

Content safety and integrity for Craft CMS. Prevents accidental breakage of content, relationships, assets, and site structure.

Know what will break before it breaks.

Requirements

Installation

Open your terminal and run:

Then go to Settings > Plugins in the Craft control panel and click Install for Homer — or run:

Features

Deletion Safety

Before deleting an entry, asset, or category, Homer checks how many other elements reference it and classifies the risk:

Homer can operate in three modes:

Mode Behavior
Warn Show warnings but allow the action
Confirm Require confirmation before risky actions
Block Prevent risky actions entirely

Relation Safety

Homer builds a usage graph by querying the relations table. For any element, it can tell you:

This powers the impact analysis behind every safety check.

Asset Safety

Assets get special treatment. Homer checks:

Audit Log

Every risky action is logged with:

Logs are retained for a configurable number of days (default: 90).

CP Integration

Homer adds to the Craft control panel:

Permissions

Permission Description
View impact reports Access usage and impact report pages
Bypass safety warnings Proceed past warnings without restriction
Bypass deletion blocks Override block mode (use carefully)
View audit log Access the audit log
Manage Homer settings Change plugin configuration

Configuration

Configure Homer from Settings > Plugins > Homer in the control panel, or create a config/homer.php file:

Multi-Environment

The strictEnvironments setting enforces block mode regardless of the mode setting. By default, production is a strict environment.

Settings Reference

Setting Type Default Description
mode string 'warn' Safety mode: warn, confirm, or block
protectElementTypes array ['entry', 'asset', 'category'] Element types Homer checks
highRiskUsageThreshold int 5 References needed for "high risk"
typedConfirmationThreshold int 20 References needed for typed confirmation
adminBypass bool true Let admins bypass all checks
deletionSafety bool true Enable deletion impact checks
relationSafety bool true Enable relation safety warnings
assetSafety bool true Enable asset usage detection
auditLog bool true Enable audit logging
strictEnvironments array ['production'] Environments that force block mode
auditLogRetentionDays int 90 Days to keep audit log entries

How It Works

  1. An editor tries to delete an entry, asset, or category
  2. Homer's CP JavaScript calls the safety check API
  3. The SafetyService evaluates protection rules, user permissions, and impact data
  4. The ImpactAnalysisService queries the usage graph and classifies risk
  5. A SafetyCheckResult is returned: allow, warn, confirm, or block
  6. If not allowed, a modal shows the risk level, usage breakdown, and recommendation
  7. For critical risk, the editor must type DELETE to confirm
  8. On confirmation, a bypass token is generated and validated server-side
  9. The DeletionGuardService acts as the server-side backstop in block mode
  10. The action is recorded in the audit log

Roadmap

Future versions may include:

License

This plugin requires a commercial license. See LICENSE.md.

All versions of craft-homer with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
craftcms/cms Version ^5.3.0
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 justinholtweb/craft-homer contains the following files

Loading the files please wait ...