Project

General

Profile

Actions

Feature #104000

open

Epic #103998: Improve handling of custom Content Types

Find a better replacement for lib.contentElement

Added by Benni Mack 2 months ago. Updated about 1 month ago.

Status:
Accepted
Priority:
Should have
Assignee:
-
Category:
Content Rendering
Target version:
-
Start date:
2024-06-07
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

lib.contentElement currently is "kind-of" API but is not "context aware" (am I a regular Content Element, a plugin or a Content Block). We need to come up with a better API (probably a new cObject) to handle rendering of a "Record" / "Content Block".

Actions #1

Updated by Georg Ringer about 1 month ago

  • Status changed from New to Accepted
Actions

Also available in: Atom PDF