PHPackages                             cylancer/eventplanner - 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. [Utility &amp; Helpers](/categories/utility)
4. /
5. cylancer/eventplanner

ActiveTypo3-cms-extension[Utility &amp; Helpers](/categories/utility)

cylancer/eventplanner
=====================

A small event planner for frontend user.

4.0.1(1y ago)24GPL-2.0-or-laterPHP

Since Dec 4Pushed 1y agoCompare

[ Source](https://github.com/docmcfly/eventplanner)[ Packagist](https://packagist.org/packages/cylancer/eventplanner)[ RSS](/packages/cylancer-eventplanner/feed)WikiDiscussions master Synced yesterday

READMEChangelog (10)Dependencies (1)Versions (13)Used By (0)

Typo3 Extension :: eventplanner
===============================

[](#typo3-extension--eventplanner)

With this small event planner the frontend users can register for certain parts of an event. For example, you can coordinate who will help at the grill and who will help at the bar.

Change log
----------

[](#change-log)

- 4.0.1 :: UPD :: Update (cleaning) TCA configuration
- 4.0.0 :: UPD :: Upgrade to TYPO3 13
- 3.0.0 :: UPD :: Upgrade to TYPO3 12
- 2.2.4 :: FIX :: Remove useless evaluation class
- 2.2.3 :: FIX :: Small fixes: backend validations / missing title added / unnecessary outputs removed
- 2.2.2 :: FIX :: Small validate fix.
- 2.2.1 :: FIX :: Small UI fixes.
- 2.2.0 :: ADD :: You can do hidden votes. You can limit the vote per user.
- 2.1.1 :: RMV :: Remove the redundant event name: it is better you use the headline for the front end.
- 2.1.0 :: FIX :: Fix the plugin configuration / registration
- 2.0.8 :: FIX :: Change the max members translation.
- 2.0.7 :: FIX :: Make maximal members field visible.

Limitations
-----------

[](#limitations)

- This extension is only usable for logged in frontend user. (The admin have to pay that the frontend plugin is only available for logged in users.)

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

[](#installation)

You can install the extension via the extensions module or via composer.json.

[![Add the plugin typoscript to the static template](./Documentation/images/screen-insertStaticTemplate.png "Add the plugin typoscript to the static template")](./Documentation/images/screen-insertStaticTemplate.png)

In the second step you have to add the plugin to the TypoScript. To do this, you need to add the TypoScript of the plugin via the static template.

Configuration
-------------

[](#configuration)

Using
-----

[](#using)

### Create pages and folder

[](#create-pages-and-folder)

I always do it this way: I create a page and a folder under it. The folder contains the data. The page the appropriate frontend plugin.

[![My favorited folder structure. ](./Documentation/images/screen-folderStructure.png "My favorited folder structure.")](./Documentation/images/screen-folderStructure.png)

### Create the data container

[](#create-the-data-container)

In the data folder you create a data record of type "Event plan". (List module &gt; select the data folder &gt; press plus button)

[![Create the event plan data record. ](./Documentation/images/screen-createEventPlan.png "Create the event plan data record.")](./Documentation/images/screen-createEventPlan.png)

Fill the data record.

[![Fill the event plan data record. ](./Documentation/images/screen-fillEventPlan.png "Fill the event plan data record.")](./Documentation/images/screen-fillEventPlan.png)

### Add the frontend plugin

[](#add-the-frontend-plugin)

Add the plugin on your event page.

[![Pick the frontend plugin. ](./Documentation/images/screen-pickFrontendPlugin.png "Pick the frontend plugin.")](./Documentation/images/screen-pickFrontendPlugin.png)

Select on the "Plugin" sheet the new event plan.

[![Select the event plan data record. ](./Documentation/images/screen-selectEventPlan.png "Select the event plan data record.")](./Documentation/images/screen-selectEventPlan.png)

###  Health Score

31

—

LowBetter than 66% of packages

Maintenance47

Moderate activity, may be stable

Popularity6

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity54

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% 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 ~91 days

Recently: every ~141 days

Total

11

Last Release

397d ago

Major Versions

2.2.4 → 3.0.02024-05-21

3.0.0 → 4.0.02025-05-18

### Community

Maintainers

![](https://www.gravatar.com/avatar/e80d990786107e860444861a172251e6e67ac84d1c9717179755018a912df534?d=identicon)[docmcfly](/maintainers/docmcfly)

---

Top Contributors

[![docmcfly](https://avatars.githubusercontent.com/u/7195547?v=4)](https://github.com/docmcfly "docmcfly (14 commits)")

### Embed Badge

![Health badge](/badges/cylancer-eventplanner/health.svg)

```
[![Health](https://phpackages.com/badges/cylancer-eventplanner/health.svg)](https://phpackages.com/packages/cylancer-eventplanner)
```

###  Alternatives

[friendsoftypo3/content-blocks

TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML

103519.9k53](/packages/friendsoftypo3-content-blocks)[wazum/sluggi

TYPO3 extension for URL slug management with inline editing, auto-sync, locking, access control, and redirects

40529.5k](/packages/wazum-sluggi)[typo3/cms-scheduler

TYPO3 CMS Scheduler - Schedule tasks to run once or periodically at a specific time.

169.3M231](/packages/typo3-cms-scheduler)[typo3/cms-lowlevel

TYPO3 CMS Lowlevel - Technical analysis of the system. This includes raw database search, checking relations, counting pages and records etc.

178.2M316](/packages/typo3-cms-lowlevel)[typo3/cms-redirects

TYPO3 CMS Redirects - Create manual redirects, list existing redirects and automatically createredirects on slug changes.

167.4M80](/packages/typo3-cms-redirects)[typo3/cms-form

TYPO3 CMS Form - Flexible TYPO3 frontend form framework that comes with a backend editor interface.

147.6M265](/packages/typo3-cms-form)

PHPackages © 2026

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