Download the PHP package considbrs-webdev/eslov-customisation without Composer

On this page you can find all versions of the php package considbrs-webdev/eslov-customisation. 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?

Informations about the package eslov-customisation

Eslöv Customisation

Site-specific WordPress plugin for the Eslöv municipio-deployment migration. All Eslöv-specific DB transforms and runtime shims live here — not in the theme or LTS plugin ports.

Fix types

Type Purpose Lifecycle
One-time migration Rewrite DB: meta keys, module JSON, options wp eslov migrate … — idempotent, --dry-run
Runtime shim Bridge unmigrated rows or permanent site preference Hook/filter in Customisations/

Log every fix in .cursor/plans/db-migration.md.

Installation

WP-CLI

Individual commands (also run by migrate all when status is ready):

Adding a migration

  1. Add transform logic in source/php/Migration/ (pure PHP, no WP-CLI coupling).
  2. Add source/php/Cli/Migrate/YourCommand.php extending AbstractMigrateCommand.
  3. Register in CliBootstrap::register().
  4. Add an entry to Migration/MigrationRegistry.php (set run_order when status is ready).

Adding a runtime shim

  1. Create a class in source/php/Customisations/.
  2. Register hooks in __construct().
  3. Add the class to App::registerInstances().

SMTP

Customisations\Smtp routes outgoing mail through SMTP (via phpmailer_init). It is a no-op until all six constants below are defined.

Add a config/smtp.php (there's no built-in one), following the pattern of config-example/sentry-example.php in municipio-deployment:

...and register it in wp-config.php's $configFiles list, alongside sentry.php etc. The (#token#) placeholders are filled in per environment by the deploy pipeline, same as DB_PASSWORD and the other secrets in config-example/.

This replaces the old web/app/mu-plugins/smtp.php mu-plugin — no mu-plugin changes are needed.

Plugin layout (Piteå-style)

Custom Modularity modules register in eslov-customisation.php (init priority 5), same pattern as Piteå AccButtons.

Blade view overrides

Assets (Vite)

Site CSS/JS and module styles use separate Vite builds and manifests. Built files land in assets/dist/ (gitignored) — run npm run build locally or via build.php.

Build Config Output Enqueued by
Site CSS + JS vite.config.mjs assets/dist/ SiteStyles + SiteScripts (global)
mod-navigation vite.navigation.config.mjs Modules/Navigation/assets/dist/ Navigation::style() (on-page only)

License

MIT

Imported-event review is disabled

Events are reviewed at the source site. The registrations for SubsiteImportReview, SubsiteImportReviewList and SubsiteImportReviewChanges are commented out in source/php/App.php. External Content follows its normal publication behavior, with no additional review buttons or change-review metabox.

The handler code remains available for future reuse. There is no site option to switch these handlers on or off; restoring them requires a code change. This applies wherever this plugin runs. Existing pending posts are not automatically published, and checksum-based synchronization may skip unchanged source events.


All versions of eslov-customisation with dependencies

PHP Build Version
Package Version
Requires php Version >=8.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 considbrs-webdev/eslov-customisation contains the following files

Loading the files please wait ...