What does it do? 

This TYPO3 extension adds content planning capabilities to the TYPO3 backend: assign a status to pages (and other records), assign responsible editors and leave comments with todos — all directly in the page tree, record list and file list.

Ideal for content migrations, editorial workflows or any process where you need to track who is working on what.

Features 

Status

Colorful, customizable status labels for pages and records. Change status via page tree, module header, record list or edit form. Bulk update multiple records at once or via console command.

Assignee

Assign responsible editors to records. Quick actions: "Assign to me" / "Unassign" shortcuts. Optional auto-assignment on status change.

Comments

Discuss records directly in the backend. Todos and resolution tracking within comments. Threaded replies and shareable links.

Dashboard

Ready-to-use dashboard preset with dedicated widgets. Overview, status, updates, assignee, todo, comments widgets. Configurable widget with custom filters (TYPO3 v14+).

Extensibility

Extend additional database records with status behavior. Built-in support for content elements and files/folders.

Screencast 

Support 

There are several ways to get support for this extension:

• GitHub: https://github.com/xima-media/xima-typo3-content-planner/issues

License 

This extension is licensed under GNU General Public License 2.0 (or later).

Requirements 

• PHP 8.2 - 8.5
• TYPO3 13.4 LTS & 14.0+

Install 

Require the extension via Composer (recommended):

composer require xima/xima-typo3-content-planner

Or download it from the TYPO3 extension repository.

Setup 

After the installation, update the database schema and setup the extension:

vendor/bin/typo3 database:updateschema
vendor/bin/typo3 extension:setup --extension=xima_typo3_content_planner

Default Status 

By default, there are four different statuses available:

• Pending: The page is not yet ready for editing.
• In progress: The page is currently being edited.
• Needs review: The page is ready for review.
• Completed: The page is ready to be published.

Custom Status 

Statuses are managed as records on the root page (pid 0).

You can add a new status, edit an existing status, change the status order or delete a status.

Features 

Assignee 

Comments 

Basic Permissions 

Via the "Access Rights" tab add one of the following permissions within the Custom module options:

View Only (tx_ximatypo3contentplanner:view-only)

Enables Content Planner visibility (status indicators, comments panel) without any action permissions. Use this in combination with granular permissions.

Full Access (tx_ximatypo3contentplanner:content-status)

Grants visibility and all Content Planner permissions at once. This is useful for power users who should have unrestricted access to all features.

Granular Permissions 

In addition to the basic permissions, you can configure granular permissions to control specific actions. These require either View Only or Full Access as a prerequisite for visibility.

Read-Only Fields in Record Editing 

When editing records (e.g. page properties), the Content Planner fields are automatically set to read-only if the user lacks the corresponding permission:

• Status field: read-only without Change Status permission
• Assignee field: read-only without any assignment permission (Assign Self or Assign Others)
• Comments field: read-only without Create Comments permission (or missing tables_modify for the comment table)

This ensures that users with View Only access can see the current status, assignee, and comments, but cannot modify them directly in the record form.

Per-Group Restrictions 

In addition to the custom module options, you can restrict which statuses and tables a user group can work with:

Migration from Previous Versions 

If you upgrade from a version without granular permissions, existing user groups with the Content Status permission will continue to work as before - the permission now grants full access.

To use granular permissions:

1. Use View Only for read-only access or Full Access for unrestricted access
2. Add the desired fine-grained permissions for each user group
3. Optionally restrict allowed statuses and tables per group

Additional Required Permissions 

Don't forget to also add the following permissions as well:

• "Tables (listing)" (tables_select) and "Tables (modify)" (tables_modify) permissions for the Content Planner Comment [tx_ximatypo3contentplanner_comment] table
• All desired dashboard widgets in the "Dashboard widgets" (availableWidgets) permission.

Page Tree 

In the page tree, you can change the status of a page via the context menu.

Module Header 

In the module header of the modules web_layout, web_list, record_edit and file_list, you can change the status of a page via the status dropdown.

Edit Form 

In the edit form of a record, you can change the status in the "Content Planner" tab.

Record List 

In the record list, you can change the status of a record via the dropdown.

Update multiple records 

New in version 1.3.0

Feature: #50 - Add table header bulk status update action

Within the record list, you can also change the status of multiple records at once.

Select the records you want to change the status of (or "Check all") and use the status dropdown in the table header.

Tip

Otherwise use the console command to update multiple records at once.

Selection 

By clicking the assignee field in the header bar, a selection dialog will open. This dialog allows you to select a user as assignee for the record. The dialog will show all users with admin rights and the necessary permission.

Shortcuts 

Use the shortcuts beneath the select field for "Assign to me" and "Unassign" to quickly change the assignee.

Edit Form 

The assignee can be selected in the edit form of the record in the "Content Planner" tab.

Create new comment 

Show comments 

Edit comments 

Use the context menu to edit, resolve or delete a comment.

An edited comment is marked with a label.

ToDos 

Use the ToDo list within the editor to track the progress of your comments.

The ToDo count is automatically updated when you add or remove a ToDo item in the comment.

Use the ToDo widget to keep track of your ToDo tasks.

Resolution 

In addition to the ToDos in the comments, there is also the option of marking entire comments as completed, in order to keep the comment list clear and organized.

A comment can be marked as completed via the context menu.

Threaded Replies 

Comments support single-level threaded replies. Each root comment can have replies that are displayed as an indented, collapsible section below it.

Creating replies 

Use the Reply action in the comment's dropdown menu or click the reply button at the bottom of the reply list. A reply is created the same way as a regular comment — through the FormEngine modal.

Replies to replies are automatically flattened to a single level (all replies belong to the root comment).

Collapsible section 

Replies are collapsed by default. A toggle shows the reply count and the time of the most recent reply (e.g., "3 replies · last 5 minutes ago"). Click the toggle to expand or collapse the reply list.

The default expand/collapse behavior can be changed globally via the "Expand replies" / "Collapse replies" button in the comment modal's action menu. This preference is persisted per user. See repliesExpanded in user settings.

Share link 

Comments and the entire comment modal can be shared with other backend users via a direct link. The link navigates the recipient to the record, automatically opens the comment modal and, if a specific comment was shared, scrolls to it and briefly highlights it.

Use the context menu of a comment to copy the share link to the clipboard. To share a link to the entire comment modal, use the action menu in the filter bar.

Enable Filelist Support 

Filelist support is enabled by default. You can disable it in the extension configuration.

Folder Status 

Folders can have a status assigned. The status is displayed in the folder tree and in the filelist header when viewing the folder contents.

The folder status header shows:

• Current status with color indicator
• Assignee selection
• Quick actions for comments

File Status 

Individual files (via sys_file_metadata) can also have a status assigned. The status dropdown appears in the file row actions.

Supported Views 

The Content Planner integration works in the following filelist views:

• List View: Full support with status dropdowns and color indicators
• Tiles View: Status color indicators on tiles

Create 

To create a new dashboard, click on the "Add dashboard" (+) button near the dashboard tabs in the dashboard module.

Otherwise you can add the widgets manually to an existing dashboard.

Widgets 

The dashboard provides a set of helpful widgets to get an overview of the current status of the content planner records.

Overview

Bar chart showing the distribution of records by status.

Recent Updates

Update stream showing the latest changes to the content planner records.

Current Assignee

Short list with all records assigned to the current user.

ToDo

Display all records with open todos in the comments.

Recent Comments

Shows the latest comments on the content planner records.

Status

Filterable list of all records with the current status.

Content Planner (Configurable)

A fully customizable widget that combines the functionality of multiple widgets. Available in TYPO3 v14+ only. See Configurable Widget for details.

Configurable Widget 

The Content Planner (Configurable) widget is a powerful, customizable widget. It allows you to create multiple instances with different configurations, each tailored to your specific needs.

Settings 

The widget can be configured through the widget settings dialog:

Setting:	Description:
Custom Title	Set a custom title for the widget. If left empty, an automatic title based on the selected mode will be used.
Display Mode	Choose what kind of records to display: All Status Records: Shows all records with any content planner status Assigned Records: Shows records filtered by assignee Records with open TODOs: Shows only records that have open tasks in their comments
Status Filter	Filter records by a specific status. Select "All statuses" to show records with any status.
Assignee Filter	Filter records by assignee: All assignees: No assignee filter Current User: Shows only records assigned to the logged-in user Specific user: Select a specific backend user
Record Type Filter	Filter records by table type (e.g., pages, news, etc.). Select "All record types" to show all registered tables.

content-planner:bulk-update 

A command to update multiple records based on a given configuration.

vendor/bin/typo3 content-planner:bulk-update

typo3/sysext/core/bin/typo3 content-planner:bulk-update

The following command arguments are available:

The following command options are available:

PrepareStatusSelectionEvent 

This event is dispatched before the status selection is rendered. You can use it to modify the available status options.

<?php
namespace MyVendor\MyExtension\EventListener;

use Xima\XimaTypo3ContentPlanner\Event\PrepareStatusSelectionEvent;

final class ModifyStatusSelectionListener
{
    public function __invoke(PrepareStatusSelectionEvent $event): void
    {
        $table = $event->getTable();
        $uid = $event->getUid();
        $selectionEntries = $event->getSelectionEntriesToAdd();

        // Remove a specific status from selection
        unset($selectionEntries['3']);

        $event->setSelectionEntriesToAdd($selectionEntries);
    }
}

MyVendor\MyExtension\EventListener\ModifyStatusSelectionListener:
  tags:
    - name: event.listener
      identifier: 'my-extension/modify-status-selection'

StatusChangeEvent 

This event is dispatched after the status of a record has been changed. You can use it to trigger additional actions like notifications or workflow transitions.

Note that $newStatus may be null when a status is cleared from a record.

<?php
namespace MyVendor\MyExtension\EventListener;

use Xima\XimaTypo3ContentPlanner\Event\StatusChangeEvent;

final class StatusChangeListener
{
    public function __invoke(StatusChangeEvent $event): void
    {
        $table = $event->getTable();
        $uid = $event->getUid();
        $newStatus = $event->getNewStatus();
        $previousStatus = $event->getPreviousStatus();

        // Example: Send notification when status changes to a specific status (uid 3)
        if ($newStatus?->getUid() === 3) {
            // Trigger notification logic
        }
    }
}

MyVendor\MyExtension\EventListener\StatusChangeListener:
  tags:
    - name: event.listener
      identifier: 'my-extension/status-change'

CommentCreatedEvent 

This event is dispatched after a new comment has been saved to the database. This includes both root comments and replies. Use it for notifications, activity logging, or integration with external systems.

The table property refers to the record being commented on (e.g. pages), not the comment table itself.

<?php
namespace MyVendor\MyExtension\EventListener;

use Xima\XimaTypo3ContentPlanner\Event\CommentCreatedEvent;

final class CommentNotificationListener
{
    public function __invoke(CommentCreatedEvent $event): void
    {
        $table = $event->getTable();           // e.g. 'pages'
        $recordUid = $event->getRecordUid();   // UID of the commented record
        $commentUid = $event->getCommentUid(); // UID of the new comment
        $authorUid = $event->getAuthorUid();   // UID of the backend user

        // Example: Send Slack notification
    }
}

MyVendor\MyExtension\EventListener\CommentNotificationListener:
  tags:
    - name: event.listener
      identifier: 'my-extension/comment-notification'

CommentResolvedEvent 

This event is dispatched when a comment is marked as resolved. It is not dispatched when a comment is reopened (unresolved).

<?php
namespace MyVendor\MyExtension\EventListener;

use Xima\XimaTypo3ContentPlanner\Event\CommentResolvedEvent;

final class CommentResolvedListener
{
    public function __invoke(CommentResolvedEvent $event): void
    {
        $table = $event->getTable();               // e.g. 'pages'
        $recordUid = $event->getRecordUid();       // UID of the commented record
        $commentUid = $event->getCommentUid();     // UID of the resolved comment
        $resolvedByUid = $event->getResolvedByUid(); // UID of the resolving user

        // Example: Log resolution for audit trail
    }
}

MyVendor\MyExtension\EventListener\CommentResolvedListener:
  tags:
    - name: event.listener
      identifier: 'my-extension/comment-resolved'