PHPackages                             basilicom-pimcore-plugin/participation - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. basilicom-pimcore-plugin/participation

ActivePimcore-plugin[Framework](/categories/framework)

basilicom-pimcore-plugin/participation
======================================

Framework to help building raffles and subscriptions

1.0.1(10y ago)01341[3 issues](https://github.com/basilicom/pimcore-plugin-participation/issues)BSD-3-ClausePHPPHP >=5.4.0

Since Dec 10Pushed 9y ago3 watchersCompare

[ Source](https://github.com/basilicom/pimcore-plugin-participation)[ Packagist](https://packagist.org/packages/basilicom-pimcore-plugin/participation)[ Docs](http://basilicom.de/en/pimcore)[ RSS](/packages/basilicom-pimcore-plugin-participation/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (2)Dependencies (2)Versions (3)Used By (0)

Participation Pimcore Plugin
============================

[](#participation-pimcore-plugin)

Developer info: [Pimcore at basilicom](http://basilicom.de/en/pimcore)

Synopsis
--------

[](#synopsis)

This Pimcore  plugin simplifies building a site with participations, e.g. raffles.

Method of Operation
-------------------

[](#method-of-operation)

A user visiting the `/participation-demo-simple` page/url gets a form (with a captcha). Upon completing the captcha, filling out the form and submitting it, a new `Participation`object (key is constructed using `time()` and a random value) is added to the `/participation` object folder and an email `/participation-confirmation` is send to the user. If the User clicks on the confirmation link in the received email, his `Participation` object is retrieved by looking up the confirmation code and setting the objects `isConfirmed` property to `true`. Notes are created the the objects in order to document the individual steps.

The users IP is recorded during object creation / confirmation. Prior to sending the email, the `participation` object is updated with an extra normalized domain part of the users email address. These properties can later be used for additional/optional fraud detection/prevention.

Motivation
----------

[](#motivation)

Implementing raffles with participations is a recurring tedious task - prone to making many errors. This plugin tries to use as much "Best Practices" and standard Pimcore features as possible to simplify future implementations.

Installation
------------

[](#installation)

Add "basilicom-pimcore-plugin/participation" as a requirement to the composer.json in the toplevel directory of your Pimcore installation.

Example:

```
{
    "require": {
        "basilicom-pimcore-plugin/participation": "~1.0"
    }
}

```

Installing the plugin via the Pimcore Extension Manager performs the following steps:

- an object class `Participation` is created
- an object folder `/participation` is created
- a predefined email document type `Participation Confirmation` is created
- a sample email document `/participation-confirmation` is created
- a demo document `/participation-demo-simple` is created
- a static route `participationConfirmationCheck` is created for `@/confirm/(.*)@`

Press the "Configure" button of the Participation plugin from within the Extension Manager and set the config file properties.

*Hint:* Set `demoEnabled` to `1` if you want to test the `/participation-demo-simple`.

You need to apply for / configure a Google Recaptcha widget integration and configure `sitekey` and `secret` in the plugin configuration file.

Refer to  for info on Google Recaptcha.

Customization
-------------

[](#customization)

The `Participation` object class can be modified as long as the `email` field and the fields of the *Meta* section are kept.

You can change the static route `participationConfirmationCheck` as long as you keep the name and the `code` parameter intact.

Change the target folder for storing the Participations by altering the `objectFolderPath`configuration option.

Change the email document used by altering the `emailDocumentPath` configuration option.

Provide custom participation confirmation success/failure pages by changing the configuration options `confirmationSuccessUrl` and `confirmationFailureUrl`.

For further customization, extend the *Manager* class and (optionally) one or more of the *Confirmation* and *ReCaptcha* classes or implement the corresponding interfaces. You need to register your new *Manager* class by specifying the full class name in the plugin configuration file.

API Reference
-------------

[](#api-reference)

The following interfaces are provided:

- `\Participation\ManagerInterface`
- `\Participation\ConfirmationInterface`
- `\Participation\CaptchaInterface`

Tests
-----

[](#tests)

- none

Todo
----

[](#todo)

- Add an Ajax-based form demo.
- Add re-usable AreaBricks
- Implement the possibility to use multiple/different participations in one pimcore installation
- Implement IP-based throtteling (via leaky bucket)
- Implement email-domain-based throtteling (via leaky bucket)
- Add Application Log logging

Contributors
------------

[](#contributors)

- Susanna Huhtanen
- Christoph Luehr

License
-------

[](#license)

- BSD-3-Clause

###  Health Score

28

—

LowBetter than 52% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity11

Limited adoption so far

Community11

Small or concentrated contributor base

Maturity59

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 66.7% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~117 days

Total

2

Last Release

3737d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/5c0d06c93d4cfac61be4239ec123ca75a189a5275d4e1782755d85029e67b6bc?d=identicon)[christophluehr](/maintainers/christophluehr)

---

Top Contributors

[![mixahead](https://avatars.githubusercontent.com/u/1044092?v=4)](https://github.com/mixahead "mixahead (6 commits)")[![christophluehr](https://avatars.githubusercontent.com/u/1352356?v=4)](https://github.com/christophluehr "christophluehr (3 commits)")

---

Tags

Participationpimcoreraffle

### Embed Badge

![Health badge](/badges/basilicom-pimcore-plugin-participation/health.svg)

```
[![Health](https://phpackages.com/badges/basilicom-pimcore-plugin-participation/health.svg)](https://phpackages.com/packages/basilicom-pimcore-plugin-participation)
```

###  Alternatives

[prestashop/prestashop

PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers.

9.1k16.8k](/packages/prestashop-prestashop)[coreshop/core-shop

CoreShop - Pimcore eCommerce

290202.1k11](/packages/coreshop-core-shop)[impresscms/impresscms

ImpressCMS is an open source content management system with a focus on security and speed

291.1k](/packages/impresscms-impresscms)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)