Download the PHP package leuchtfeuer/mautic-segmentcrud-bundle without Composer

On this page you can find all versions of the php package leuchtfeuer/mautic-segmentcrud-bundle. 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 leuchtfeuer/mautic-segmentcrud-bundle

Informations about the package mautic-segmentcrud-bundle

Leuchtfeuer Segment CRUD

Console tooling to create or update lead segments by alias or id, and optionally clear segment membership in two ways: --clear deletes rows from lead_lists_leads (soft), or --permanent-clear sets manually_removed = 1 on active rows while keeping the records (useful for Databridge-style / prep workflows where you need one or the other).

Overview

Requirements

[!TIP] Other releases of this plugin may target different Mautic versions.

Installation

Composer

Install the package and ensure it is deployed under plugins/LeuchtfeuerSegmentCrudBundle (see Composer extra.install-directory-name).

Manual Installation

  1. Download / copy the plugin into the Mautic plugins directory.
  2. The folder name must be LeuchtfeuerSegmentCrudBundle.

  3. In the Mautic UI as an administrator: Plugins → Install/Upgrade Plugins.

    Or with shell access from the Mautic project root:

Configuration

The console command checks that the integration is published. If it is disabled, the command exits with an error and asks you to enable it.

  1. Log in as an administrator.
  2. Open Settings (cog) → Plugins (or Integrations, depending on your Mautic layout).
  3. Open Leuchtfeuer Segment CRUD (integration key: SegmentCrud).
  4. Publish / enable the integration and save.

Until this is done, leuchtfeuer:segment:prepare will refuse to run.

Usage

From the Mautic project root (where bin/console lives):

That lists all options (--alias, --id, --name, --desc, --noupdate, --nocreate, --clear, --permanent-clear, --batch-size, etc.).

Typical examples (after the plugin is published):

Use --help for the authoritative option list and defaults (e.g. --batch-size applies to both --clear and --permanent-clear).

Do not pass --clear and --permanent-clear together — the command exits with an error.

Mautic events

This command is a direct console path and does not participate in Mautic’s event system the way UI- or API-driven segment flows do. In particular, do not expect the same subscribers / follow-up events (e.g. segment membership or list change events) to be dispatched or to run in the same order as in core segment processing. If you rely on custom plugins that listen for segment-related events, validate behaviour separately or trigger those side effects by another supported mechanism.

Tests

Unit tests (plugin repository)

In this plugin directory, after composer install:

That runs PHPUnit with --testsuite unit (Tests/Unit).

CI (GitHub Actions)

Pull requests use the shared mautic-ci-runner workflow: PHP CS Fixer, PHPStan, Rector, Twig lint, unit tests, and functional tests (MySQL/MariaDB matrix) against supported Mautic 5.x and PHP versions.

Functional tests (local / full Mautic)

Functional tests extend Mautic\CoreBundle\Test\MauticMysqlTestCase and need a complete Mautic tree with MySQL. In DDEV, from the project root:

If you use DDEV, from the host:

Functional tests also expect DB client tools (mysqldump / mysql) behaviour compatible with MauticMysqlTestCase; running inside DDEV avoids many host-only mismatches.

Troubleshooting

Credits

Developed by Leuchtfeuer Digital Marketing GmbH.

Author

Leuchtfeuer Digital Marketing GmbH

All versions of mautic-segmentcrud-bundle with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
mautic/core-lib Version ^7.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 leuchtfeuer/mautic-segmentcrud-bundle contains the following files

Loading the files please wait ...