Deprecated

This module has been deprecated as part of Zikula 4 slimming diet.

Content module for the Zikula Application Framework

Documentation

1. Introduction
2. Requirements
3. Installation
4. Upgrading
5. How to link pages
6. Integration with menu module
7. Implementing custom content types
8. Changelog
9. TODO
10. Questions, bugs and contributing

Introduction

Content is a hierarchical page editing module for Zikula 3. With it you can insert and edit various content items, such as HTML texts, videos, maps and much more. Also content of other modules and blocks can be shown inside a Content page.

Each page can arrange arbitrary content elements using Bootstrap grids.

It also features additional functionality, like translating content and tracking changes between different versions.

Requirements

The main branch of this module is intended for being used with Zikula 3.1. For Zikula 3.0.x and 2.0.x look at releases.

Installation

The Content module is installed like this:

1. Download the latest release.
2. Copy the content of extensions/ into the extensions/ directory of your Zikula installation. Afterwards you should a folder named extensions/Zikula/ContentModule/.
3. Initialize and activate ZikulaContentModule in the extensions administration.

Upgrading

How to link pages

When you statically refer to pages in some templates you will see one problem: linking to the details of a page requires the slug which may be different per language and could be changed later which will break your link. For this a Twig function is provided to get the slug from the page id. For example:

<a href="https://github.com/zikula-modules/Content/blob/main/{{ path('zikulacontentmodule_page_display', {slug: zikulacontentmodule_getSlug(2)}) }}" title="Test page">Test page</a>

Integration with menu module

Content offers a dedicated menu block. But it can also be combined with menus from the menu module which is provided by Zikula core. You can add nodes with a placeholder title like ContentPages_123 whereby 123 is the ID of a certain page. When displaying the menu this placeholder will be replaced by the corresponding pages sub tree. Note that only those pages are shown which are currently active, have the "in menu" flag enabled and visible to the current user.

By default there are unlimited levels added to a menu. You can limit this by adding an extras option to the menu entry with value {"levels":2} where 2 is the desired amount of levels.

Implementing custom content types

In content each page consists of several content items. Each content item uses a certain content type. Interestingly, other modules can provide additional content types, so for example a calendar module can offer a content type for displaying a list of events for a specific category or the details of a single event. For each content type a corresponding class needs to be implemented which cares about displaying, editing and translating the managed data.

• A content type class names should be suffixed by Type and located in the ModuleRoot/ContentType/ directory. This is not mandatory but a recommended convention.
• Content type classes must implement Zikula\ExtensionsModule\ModuleInterface\Content\ContentTypeInterface.
• Content type classes may extend Zikula\ExtensionsModule\ModuleInterface\Content\AbstractContentType for convenience.
• Content type classes must define a Symfony form type class to allow editing of their data fields if this is needed. This form type class should extend Zikula\ExtensionsModule\ModuleInterface\Content\Form\Type\AbstractContentFormType for convenience. Otherwise the getEditFormClass method must return null.
• The convention for template files of a content type with name foo is as follows:
  • Display: @AcmeFooModule/ContentType/FooView.html.twig
  • Edit subform: @AcmeFooModule/ContentType/FooEdit.html.twig
  • In the edit sub form template, do not render the form_start(form) or form_end(form) tags.

Changelog

TODO

• The ComputerCodeType needs to be updated for supporting the BBCode and LuMicuLa modules as soon as they have been migrated to Zikula 3. There are @todo markers for that.
• The YouTubeType could be enhanced to fetch additional data from API. It should use the CacheHelper like SlideshareType and VimeoType. There is a @todo marker for that.

Questions, bugs and contributing

If you want to report something or help out with further development of the Content module please refer to the corresponding GitHub project at https://github.com/zikula-modules/Content.