Under Construction

xBlog is under construction. If you like to get news about the progress, please subscribe to my newsletter at

• https://die-netzmacher.de/newsletter/

Please take a look into the sections What does it not do? and the to-do-list.

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Single Filter

Sample with a single filter.

Here: News with the category "TYPO3 xBlog" are displayed.

Multiple Filters

Depending on the foreign table, xBlog displays the possible values for the comparison.

Sample with multiple filters.

Here: Records are displayed

• whose date is current (deactivated)
• and the place is Passau
• or whose category is politics or sponsorship

Current Version

The current version supports:

• list views with

  • datesheets
  • filters
  • images

• single views with

  • datesheet
  • images
  • media
• mini views
• pagings
• RSS feeds
• simple search form
• slider
• session management
• tag cloud

The bridge

The core of xBlog is the bridge.

For example: a list view is publishing usually the elements:

• a title
• a subtitle
• a short (sometimes)

An administrator allocates to each element fields like

• subtitle: margin_subtitle // teaser_subtitle // subtitle // my_extension_subtitle

This means:

xBlog is looking for a value from a field margin_subtitle and if it is empty, xBlog looks for a value from a field teaser_subtitle, and if it is empty, it takes the next for rendering. And so on.

This concept enables a ready-to-use configuration for most of use cases.

Precondition

The static templates of the xBlog must included.

If it isn't, please contact your TYPO3 administrator.

Table of Contents

Tab [Bridge]

You can use upto four related tables out of the box:

• Category
• Group
• Section
• Tag

The xBlog will display the data in the frontend.

Setup

You can configure these properties by the Constant Editor:

• firstResult: first record (0 is the first). Like first part of SQL LIMIT
• maxResults: amount of records. Like second part of SQL LIMIT
• andWhere: Clause for the an andWhere statement. Example: my_news.date > UNIX_TIMESTAMP(NOW())
• orderBy: ORDER BY clause. BEWARE OF THE SYNTAX: field1|ASC||field2|DESC||field3|ASC

Constant Editor

• categories [XBLOG - MAIN - DATAPROCESSOR - * ]

What does it do?

The xBlog plugin Form enables you, to create a form by a web interface.

Tables

You can use any main table and its related tables.

Type of fields --------------

• Button: magnifier, reset or send
• Checkbox
• Placeholder: only for layout
• Radiobuttons
• Search Word: full text search
• Select
• Select (Period): month, year, decennium
• Select (Scope)

Period

Type "Select (Period)" delivers three modes. See below.

Condition: Field must be a timestamp.

Scope

Condition: Field must be an integer.

Visitors of your website can filter scopes (areas) like range of prices (squaremeters, kilowatts and so on).

Example:

• ... - 10.000 EUR
• 10.000 - 20.000 EUR
• 20.000 - 30.000 EUR
• 30.000 - 40.000 EUR
• 40.000 EUR - ...

Screenshots

• Backend
• Frontend

Conditions

• Administrators > Setup > Constant Editor > Slider

Workflow

Conditions

• Administrators > Setup > Constant Editor > Slider

Workflow

Screenshots

Please refer to Screenshots

Tables

You can filter the main table and related tables.

Assistent

There are the four assistent modes:

• Suggestion (foreign tables only): the easiest way
• Default: similar to suggestions but a little bit more design freedom
• Ready-to-use statements. Currently

* >= NOW()

• <= NOW()

• SQL-Professional: best design freedom, but you need to know a bit about SQL

Combining filters

You can combine filters unlimited.

Maybe you will have unexpected results. In this case please refer to the section * Known Bugs > Filter.

Setup

You enable frontend editing in the xBlog plugin:

Tab [Advanced]:

• [X] Publish: Logged-on users can publish their own content

Tab [Publish]

• Page with the edit form: select the publish plugin
• Storage folder of the records: select a folder

Requirements

A page with a publish plugin and a powermail plugin must be set up. Please refer to the manual of Publish.

Size

There are three modes for sizing images:

• System (default): width and height will taken from TypoScript constants. See Administrator > Setup > Constant Editor > Images.
• Record: width and height will taken from the record (from croping or from width and height). Available in single view only.
• Plugin: width and height will taken from the plugin

Plugin

You find the select box with the three modes here:

• Plugin > Feature: Image Size in list view Size in single view

xBlogMain plugin

• xBlogMain plugin > Plugin > Controlling > Real URL parameter for

The select field "Real URL parameter for" provides these parameters:

• Calendar
• Datesheet
• Default
• Download
• Event
• Job
• Location
• News
• Organiser
• Service
• Staff

Routes

The xBlog delivers a template for using routes. See: administrators-bestpractice-url-routes

Pages

You need two pages:

• a folder for the xBlogSlider plugin.
• a page with the slick slider.

xBlogSlider

Add the plugin [xBlog: Slider] to the folder from above. Adapt it to your needs:

• Origin

  • Table: News
  • Record Storage Page: folder with your news
  • Other fields: adapt it to your needs

• Profile

  • Profile: Default (showUid)
  • Other fields: adapt it to your needs

• Slide

  • Adapt it to your needs

• Feature

  • Adapt it to your needs

• Feature: Image

  • Adapt it to your needs

• Template

  • Layout: "Default". Or if you like a slider with images only and without any text, select: "Margin / Images only"
  • Other fields: adapt it to your needs

• Destination

  • Page with the single view: the page with the news plugin, which displays the single view
  • Page of the single view: the page with the news plugin, which displays the single view
  • Parameters for the third party plugin: &tx_news_pi1[news]=|&tx_news_pi1[controller]=News&tx_news_pi1[action]=detail

More about the xBlogSlider plugin

Please refer to Users > Plugins > Slider

Features

Simplify

TCA

XBLOG - BASE - TYPOLINK - PLUGIN

If you like to link from an xBlog list view to a third party plugin like tt_news, tx_cal, tx_news or tx_myextension, please setup these properties.

xBlog - Base - Fields - Image

Field which will processed automatically

xBlog - Main - Images - default icons

Default icons

xBlog - Main - Images - Size

Default width and height for images in list and single views.

User can select the mode / workflow. See User > Best Practice > Images

xBlog - Image - view

Paths for FLUID-Templates

Fields list

• title: fields for the title
• subtitle: fields for the subtitle
• short: fields for the short

Fields single

• title: fields for the title
• subtitle: fields for the subtitle
• short: fields for the short
• bodytext: fields for the bodytext

HTML Wraps List

• title: html wrap for the title
• subtitle: html wrap for the subtitle
• short: html wrap for the short
• item: html wrap for an item
• list: html wrap for the whole list
• prompt: html wrap for the prompt (if there isn't any result)

HTML Wraps Single

• title: html wrap for the title
• subtitle: html wrap for the subtitle

View

Paths to the fluid templates

Fields list

• title: fields for the title
• subtitle: fields for the subtitle
• short: fields for the short

HTML Wraps List

• title: html wrap for the title
• subtitle: html wrap for the subtitle
• short: html wrap for the short
• item: html wrap for an item
• list: html wrap for the whole list
• prompt: html wrap for the prompt (if there isn't any result)

View

Paths to the fluid templates

Init

• dontLinkActivePage: Don't link the active page
• Display the paging even if there isn't any page or one page only
• hscText: Enable htmlspecialchars(). Set this to false if you want f.e use images instead of text for links like 'previous' and 'next'
• pagefloat
• tableParams

Wrap

• activeLinkWrap
• browseBoxWrap
• browseLinksWrap
• disabledLinkWrap
• inactiveLinkWrap
• showResultsNumbersWrap
• showResultsWrap

View

Paths to the fluid templates

Conditions

• TypoScript templates are included:

  • xBlog [0.1.0] Base
  • xBlog [1.0.0] Main
  • xBlog [20.0.0] RSS

Constant Editor

Conditions

• The extension Slick Slider (EXT:slick) must be installed.

• TypoScript templates are included:

  • xBlog [0.1.0] Base
  • xBlog [1.0.0] Main
  • xBlog [7.0.0] +Slider

Constant Editor

pages.TSconfig

Please add the code-snippet from below to the page TSconfig of your root pages of your projects, where 124 is the id of the current root page:

TCEFORM.tt_content.pi_flexform.xblog_pi1.ctrl.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi1.ctrl.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi2.ctrl.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi2.ctrl.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi3.ctrl.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi3.ctrl.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi8.ctrl.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi8.ctrl.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi9.table.settings\.flexform\.pi9\.ctrl\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi9.table.settings\.flexform\.pi9\.ctrl\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi11.table.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi11.table.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi12.ctrl.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi12.ctrl.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi13.ctrl.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi13.ctrl.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi14.table.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi14.table.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi16.table.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi16.table.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi17.table.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi17.table.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi18.table.settings\.flexform\.pi\.table\.pidList.config.treeConfig.rootUid = 124
TCEFORM.tt_content.pi_flexform.xblog_pi18.table.settings\.flexform\.pi\.table\.pidSingle.config.treeConfig.rootUid = 124

Automatic Configuration

xBlog has a migration script. This script generates the needed page TSconfig automatically.

See Administrators > Migration > Page TSconfig

What does ist do?

The configuration takes care for a human readable URL for

• the page browser
• the category filter
• the fe_users table
• the tables of the Organiser (EXT:org)

Adaption for your extension

If you like to adapt the configuration to your extension please

• copy EXT:xblog/Configuration/Routes/Default.yaml to EXT:my_ext/Configuration/Routes/Default.yaml
• Adapt your file to your needs
• Add to your typo3conf/sites/<my_site>/config.yaml the following line:

imports:
    - { resource: "EXT:my_ext/Configuration/Routes/Default.yaml" }

xblog.enabled

If this property is disabled, this table will not be provided in the Flexforms of the xBlog plugins. Has an effect only, if xBlog is running in the so called user-friendly mode.

Values (boolean)

• 0: disabled
• 1: enabled

Sample

$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['enabled'] = 1;

xblog.plugins.pi17.datefield

The xBlog plugin Mini Calendar (pi17) needs to know which is the date field of a record of a table.

If you want to use your records with the xBlog mini calendar plugin, you need to set the property. See sample below.

Value (string): a datefield

For example:

• a calender record has a start date usually
• a news record has a publishing date usually
• a staff record has a birthday date usually

Sample

$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['plugins']['pi17']['datefield'] = 'datetime'

xblog.default

If a table is the xblog default table, this table will be entered in the xBlog plugin form.

Of course one table only can be the default table.

Value (boolean): 1

Sample

$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['default'] = '1'

Configuration example online

https://gitlab.die-netzmacher.de/typo3/org/-/blob/master/Configuration/TCA/tx_org_news.php

xblog.defaultprompts

The xBlog plugin is set up step by step automatically: the user has to save the plugin twice. The necessary messages are set here.

Sample

$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['defaultprompts'] = [
  '1' => [
    'dependsOn' => [
      'field' => 'settings.flexform.pi.table.table',
      'sheet' => 'table'
    ],
    'prompt'    => 'LLL:EXT:org/Resources/Private/Language/Ext/xblog.xlf:promptTableInitial01'
  ],
  '2' => [
    'dependsOn' => [
      'field' => 'settings.flexform.pi.table.selectOrderField',
      'sheet' => 'table'
    ],
    'prompt'    => 'LLL:EXT:org/Resources/Private/Language/Ext/xblog.xlf:promptTableInitial02'
  ],
]

Configuration example online

https://gitlab.die-netzmacher.de/typo3/org/-/blob/master/Configuration/TCA/tx_org_news.php

xblog.defaults

This is where the default values are set. The field name corresponds to that in the flex form. Unfortunately, it is not possible to define a default value for all fields contained in the flex form. At present, this option is also limited to selection boxes.

Sample

$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['defaults'] = [
  'settings.flexform.pi.bridge.imageField'          => 'image',
  'settings.flexform.pi.bridge.mediaField'          => 'documents',
  'settings.flexform.pi.bridge.category'            => 'tx_org_newscat',
  'settings.flexform.pi.bridge.relatedrecord'       => 'related',
  'settings.flexform.pi.table.selectOrderField'     => 'datetime',
  'settings.flexform.pi.table.selectOrderDirection' => 'DESC',
  'settings.flexform.pi1.list.morebutton'           => 'bottom',
  'settings.flexform.pi1.profile.datetimefield'     => 'datetime',
  'settings.flexform.pi1.profile.showUid'           => 'newsUid',
  'settings.flexform.pi1.tmpl.grid'                 => '8',
  'settings.flexform.pi1.tmpl.marginPosition'       => 'right', 
]

Configuration example online

https://gitlab.die-netzmacher.de/typo3/org/-/blob/master/Configuration/TCA/tx_org_news.php

xblog.showUid

The xBlog controls with the showUid URL parameter and Fluid templates. Usually you select the value for the showUid in the flexform.

But if the table has this TCA property configures, the showUid for this table is determined. A user don't need to decide, what is a proper showUid.

If this property isn't enabled, this table will not be displayed in the flexforms of the xBlog plugins.

Value (string): a defined showUid from the list below.

Sample

$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['showUid'] = 'newsUid';

Defined showUids

boardUid, calUid, downloadUid, eventUid, feuserUid, itemUid, jobUid, locationUid, newsUid, organiserUid, serviceUid, showUid and staffUid

Configuration Array

$TCA = [
  'ctrl' => [
    'extensions' => [
      'xblog' => [
        'enabled' => true,
        'showUid' => 'newsUid',
        'plugins'   => [
          'pi17' => [
            'datefield' => 'datetime',
          ],
          'pi18' => [
            'tagcloudfield' => 'seo_keywords',
          ],
        ],
      ],
    ],
  ],
],

tx_org_news

If you like to extend any table of the TYPO3 database, please use an own file in TCA/Overrides like:

• EXT:your-extension-key/Configuration/TCA/Overrides/tx_org_news.php

$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['enabled'] = 1;
$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['showUid'] = 'newsUid';
$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['plugins']['pi17']['datefield'] = 'datetime'
$GLOBALS['TCA'][tx_org_news]['ctrl']['extensions']['xblog']['plugins']['pi18']['tagcloudfield'] = 'seo_keywords'

Further Information

• Administrators > Setup > Route Enhancer
• Users > Best Practice > Real URL
• Developers > Real URL

Setup

Setup

tx_xblog.templateLayouts {
  1 = A custom layout
  99 = LLL:fileadmin/somelocallang/locallang.xlf:someTranslation
}

<f:if condition="{settings_flexform_pi1_tmpl_externalTemplate} == 1">
  <f:then>
    <!-- your layout with the index 1 //-->
  </f:then>
  <f:else if="{settings_flexform_pi1_tmpl_externalTemplate} == 99">
    <!-- your layout with the index 99 //-->
  </f:else>
  <f:else>
    <!-- default xBlog layout //-->
  </f:else>
</f:if>

pages.TSconfig

This migration script updates the page TSconfig of your root pages:

• it removes configuration, which starts with 'TCEFORM.tt_content.pi_flexform.xblog_pi...'
• it adds up-to-date configuration

Root pages have a world icon in the page tree. They have enabled the property is_siteroot.

vendor/bin/typo3cms migration:migrate \
  --configuration EXT:xblog/Configuration/Migration.php \
  --key update_pages \
  --dryrun 0

Samples

dryrun is true by default.

vendor/bin/typo3cms migration:migrate \
  --configuration EXT:xblog/Configuration/Migration.php \
  --key update_pages \
  --limitToPage 124 \ 
  --recursive 0 \
  --dryrun 0

TCA

Please use for the lables of your tables the field title. If you use another label, you can get unexpected results like empty tags.

TypoScript Registers

The TypoScript of xBlog is using a lot of registers. This enables a dynamic workflow.

For example: content can calculated depending on delivered parameters in an URI and depending of the setup of a plugin.

The core of these registers are:

• xBlogMainList
• xBlogMainSingle
• xBlogMini

They contain all data for the views list, single and mini. Content of these registers will delivered to the fluid templates.

If you like to improve the TypoScript code, it would be a good idea, to use the TypoScript Object Browser and to look for the registers from above in the TypoScript code.

Setup

You can include your own layout, partials and templates by the Constant Editor. See

• Administrators > Setup > Constant Editor > Main > View
• Administrators > Setup > Constant Editor > Mini > View

Directories

Resources/Private/View/
├── 1stPlugin           <- don't touch this level
│   ├── Layouts
│   ├── Partials
│   └── Templates
├── 2ndContent
│   ├── Layouts
│   ├── Partials
│   └── Templates
└── FluidStyledContent
    └── Foundation

Storage

Location of your first partial:

EXT:my_ext/Resources/Private/View/xblog/
└── 1stPlugin
    └── Partials
        └── Externaltemplate
            ├── List
            │   └── 01.html
            └── Single
                └── 01.html

Content

For technical reasons, partials are required for the 1stPlugin. All list partials have the same code, as do all partials for the single view.

<!-- EXT:my_ext/Resources/Private/View/xblog/1stPlugin/Partials/Externaltemplate/List/01.html -->
<f:render partial="Main/List" arguments="{_all}" />

<!-- EXT:my_ext/Resources/Private/View/xblog/1stPlugin/Partials/Externaltemplate/Single/01.html -->
<div id="x{tt_content.uid}" class="{piWrapClass}">
  <f:format.raw>{content}</f:format.raw>
</div>

Storage

Location of your first partial:

EXT:my_ext/Resources/Private/View/xblog/
└── 2ndContent
    └── Partials
        └── Externaltemplate
            ├── List
            │   └── 01.html
            └── Single
                └── 01.html

Content

• You are controlling your content with the partials of the 2ndContent level.
• Partials must called 01, 02, 03, ...

{namespace vh=MyVendor\MyExt\ViewHelpers}
<!-- EXT:my_ext/Resources/Private/View/xblog/1stPlugin/Partials/Externaltemplate/Single/01.html -->
<f:debug title="my-id@jzgasdf32">{data}</f:debug>
<f:debug title="my-id@jgfjgaezf">{_all}</f:debug>
<div class="row">
  <div class="columns small-12 medium-3 col-sm-12 col-md-3">
    <f:render partial="Method/Typolink/Image" arguments="{_all}" />
  </div>
  <div class="columns small-12 medium-9 col-sm-12 col-md-9">
    <h4 class="text-overflow-ellipsis">
      {data.title}
    </h4>
    <div class="row">
      <div class="columns small-12 medium-9 col-sm-12 col-md-9">
        <f:if condition="{data.category}" > 
          <div class="row">
            <div class="columns small-3 col-sm-3">
              Category:
            </div>
            <div class="columns small-9 col-sm-9">
              <f:variable name="category"><vh:getcategory uid="{data.category}"/></f:variable>
              {category.title}
            </div>
          </div>
          ...

{namespace vh=MyVendor\MyExt\ViewHelpers}
<!-- EXT:my_ext/Resources/Private/View/xblog/2ndContent/Partials/Externaltemplate/Single/01.html -->
<f:debug title="my-id@dukieug">{data}</f:debug>
<f:debug title="my-id@kdvhdfa">{_all}</f:debug>
<h2>{data.title}</h2>
<div class="columns small-12 medium-3 col-sm-12 col-md-3">
    <f:render partial="Legresources/ImageSingleView" arguments="{_all}" />
</div>
<div class="columns small-12 medium-9 col-sm-12 col-md-9">
  <div class="row">
    <div class="columns small-12 large-12 col-sm-12 col-lg-12">
      <f:if condition="{data.category}" > 
        <div class="row">
          <div class="columns small-3 col-sm-3">
            Category:
          </div>
          <div class="columns small-9 col-sm-9">
            <f:variable name="category"><vh:getcategory uid="{data.category}"/></f:variable>
            {category.title}
          </div>
        </div>
      </f:if>
      ...

Page TsConfig

With hard coded labels:

tx_xblog.templateLayouts {
  1 = List
  2 = Edit
  3 = Status
  4 = Bookings
}

Or localised (recommended):

tx_xblog.templateLayouts {
  1 = LLL:EXT:my-ext/Resources/Private/Language/tsconfig.xlf:tx_xblog.templateLayouts.1
  2 = LLL:EXT:my-ext/Resources/Private/Language/tsconfig.xlf:tx_xblog.templateLayouts.2
  3 = LLL:EXT:my-ext/Resources/Private/Language/tsconfig.xlf:tx_xblog.templateLayouts.3
  4 = LLL:EXT:my-ext/Resources/Private/Language/tsconfig.xlf:tx_xblog.templateLayouts.4
}

Steps

• Place your field in the fluid template
• Register a field in TypoScript (optional)

Fluid Template

Sample code for the fluid template and a new field bycycle_fitting from an extension like tx_myextension.

<f:format.html>{data.bycycle_fitting}</f:format.html>

<f:format.html>{xBlogFieldBycycleFitting}</f:format.html>

TypoScript

If you like to work with registered fields in your fluid templates, you have to register these fields within TypoScript. See the workflow below.

Registered fields are part of the TypoScript FLUIDTEMPLATE.

Each of the three "core" registers - xBlogMainList, xBlogMainSingle, xBlogMini - has an element renderObj:

renderObj = FLUIDTEMPLATE
renderObj {
  variables {
    registered_field_1 = ...
    registered_field_2 = ...
    ...

See the TypoScript path for xBlogMainSingle below:

plugin.tx_xblog_pi1.settings.views.single.content.30.30.single.20 {
  xBlogMainSingle {
    cObject {
      renderObj {
        variables =

If you don't know, how to find one of the three core registers - xBlogMainList, xBlogMainSingle, xBlogMini -, please refer to

• Developers > Good to know > Core

xBlogFieldBycycleFitting = TEXT
xBlogFieldBycycleFitting {
  field = bycycle_fitting
  wrap = <p class="fittings">|</p>
}

plugin.tx_xblog_pi1.settings.views.single.content.30.30.single.20 {
  xBlogMainSingle {
    cObject {
      renderObj {
        variables {
          xBlogFieldBycycleFitting = TEXT
          xBlogFieldBycycleFitting {
            field = bycycle_fitting
            wrap = <p class="fittings">|</p>
          }
          ...

Developers of third party extensions

If you are a developer of a third party extension and you want to improve your extension for Real URL, you will find a good configuartion sample at the EXT:org. See:

• Organiser > Developers > Best Practice > Real URL

If link doesn' run, pleaser refer to the index of the manual and look for "Real URL":

• Organiser

RemoveShowUidFromSession

Returns true, if a showUid - the id of a single view - should removed from the session.

10 = USER
10 {
  userFunc = Netzmacher\Xblog\Userfunc\ControllingUserfunc->RemoveShowUidFromSession
  showUid = {$plugin.tx_xblog.configuration.params.showUid}
}

Begin

Get the begin value for a select statement within a CONTENT object.

You need to define the pointer only, if you are using another value than 'pointer'.

10 = CONTENT
10 {
  select {
    ...
    begin {
      cObject = COA
      cObject {
        10 = USER
        10 {
          userFunc = Netzmacher\Xblog\Userfunc\PointerUserfunc->Begin
          pointer = mypointer
        }
      }
    }
    ...
  }
}

SetXblogVar

Write any value of an xBlog variable to the session.

  // Sample: 
  // Write the current value of the URL param tx_blog[pointer] into the session for the tx_blog array with the element 123
  // 123 (if uid is 123), mypointer, GP:tx_xblog|pointer 
  //
10 = USER
10 {
  userFunc = Netzmacher\Xblog\Userfunc\SessionUserfunc->SetXblogVar
  uid = TEXT
  uid {
    field = uid
  }
  param = TEXT
  param {
    value = mypointer
  }                
  value = TEXT
  value {
    data = GP:tx_xblog|pointer
    intval = 1
  }
  dontClearCache = 1
}

Get the value from above from the session

  // Sample: 
  // Get the param mypointer from the session from the tx_blog array with the element 123
  // data = session: tx_blog|123|mypointer
  //
data {
  cObject = COA
  cObject {
    10 = TEXT
    10 {
      value = session: tx_xblog|
    }
    20 = TEXT
    20 {
      field = uid
    }
    30 = TEXT
    30 {
      value = |mypointer
    }
  }
}

Filter

Localisation

Must checked, if xBlog supports localisation out-of-the-box.

Plugins

Devlopment of:

• Map plugin

Workarounds

• Solve workaround #i0039

Workspaces

Must checked, if xBlog supports workspaces out-of-the-box.

TCA

Please use for the lables of your tables the field title. If you use another label, you can get unexpected results like empty tags.

xBlog

If the xBlog is the only xBlog plugin, the filter should work without errors. In combination with other xBlogs and especially with the xBlogForm, unexpected results can occur.

xBlogForm

xBlogFrom and xBlog should work reliably as long as there is only one xBlog on the page and no filters are activated for that xBlog.

Table of Contents

Prompt (sample)

There is no entry in the $TCA array for the table "ERROR at settings.register.flexform.pi3.paging.pi3__pi1_table". This means that the function enableFields() is called with an invalid table name as argument.

Cause

Probably you have included xBlog static templates twice.

Solution

Check your TypoScript with the TypoScript Analyser. If xBlog static templates are included twice, please remove one of them.

Error

The selectTree displays only the item "Page".

Error occurs with user access only. Error doesn't occurs with admin access.

Cause

TCA configuration for selectTree is missing.

Check it!

There must be a configuration like in the illustration below:

Solution

Please refer to config.treeConfig.rootUid

Prompt

Oops, an error occurred! ConnectionPool->getConnectionForTable() requires a table name to be provided.

Cause

The cause is likely: An xBlog paging plug-in is not connected to a proper xBlog. Or an xBlog paging plugin is connected to a proper xBlog, but this xBlog is hidden.

Solution

Please check the configuration of your xBlog paging plugin.

11.3

xBlogForm

• all fields of foreign tables are available now, but fields of relations to other tables
• fields of foreign tables have the properties radio buttons, checkboxes and selectboxes now

xBlogTagCloud

• new modus: take tags from related category tables

11.1

• xBlog: improved route enhancer (see Administrators > Setup > Route Enhancer)
• xBlog Main: size for image in single view by plugin
• xBlogForm: filter for scopes
• xBlogForm: filter for periods (see Screenshots > Fontend > Form)
• xBlogSlider: layout "Margin / Images only" (see: Users > Best Practice > Slider > News)

What's new in further versions

0.47

• Short for single view. CSS for dateline in single view

0.46

• Archived News
• Automatic RSS TypoScript template for page with module xblog-rss
• Do not display a record twice on the same page

Caching

0.45.0

Proper caching

• Administrators > Bestpractice > Cache

Flexform default values

0.44.0

Dynamically Flexform default values. Depending on the selected table.

• Administrators > Setup > TCA > Defaults

xBlog Tag Cloud

0.43.0

New plugin.

EXT:copyright

0.42.4

Independency of EXT:copyright. If you are using the EXT:copyright, EXT:xblog will take care about the proper setup automatically.

xBlog Mini Calendar

0.42.0

New plugin.

Simplified Configuration

0.41.0

Simplify xblog plugin: Display tables dependent on TCA.ctrl-section and extension-manager in simplify mode 'user-friendly'.

Sorting Children Records

0.40.1

Children records will be sorted by TCA ctrl sortBy

xBlog Category

0.36.0

New plugin.

Categorie Relations

0.35.1

xBlogMain: relation categories

Related Records

0.35.0

xBlogMain: new relation related records

Display selected record

0.34.1

xBlogMain: New option 'Display the selected record from below, if no other single record should displayed.'

Migration Script page TSconfig

0.33.0

Migration script for page.TSconfig: config.treeConfig.rootUid

Frontend Editing

0.31.0

Frontend-Editing: from TYPO3 10.4 only!

fe_user

0.30.19

xBlog: view for fe_user

Table Layout

0.30.17

xBlogMain: table layout

Quick Shop

0.30.2

Module for quick shop

Single Record

0.25.4

Display a single record

Bootstrap

0.20.19

CSS support for bootstrap.

Compatibility

0.20.8

TYPO3 10.4

SEO

0.20.8

• Integration of rx_shariff.
• Upgrade for Seo Dynamic Tag 5.

xBlogMain

xBlog Teaser

0.20.8

New plugin.

Controlling third party extensions

The xBlog Main plugin and the xBlog Slider plugin can used for the single view of any other extension.

See example at

• Slider with third party extension

Real URL

Support for Real URL

Related tables

You can use upto four related tables out of the box by the xBlogMain plugin. You can configure some features by the Constant Editor. See at

• Users > Plugins > Main > Related Tables

Template Selector

You can offer editors different layouts. They can select the layout in the template selector. See at

• Administrators > Best Practice > Templates > Selector

xBlogSearch

Hand on sword from xBlogSearch to xBlogForm.

Filter

xBlog plugins got the tab filter:

• xBlog Main
• xBlog Mini
• xBlog RSS
• xBlog Slider

Screenshot at

• Screenshots > Backend > Filter

0.8.15

Manual

New sections:

• News (tx_news)
• RSS Feed

RSS Feed

New plugin. Details at Administrators > Setup > Constant Editor > RSS Users

0.8.14

Manual

New sections among others:

• Index

Link to the single view of 3rd party plugins

Link to 3rd party plugins like tt_news, tx_cal, tx_org_cal, tx_org_news, tx_news, tx_quickshop and any other plugin:

• Team with tt_news, tx_*

Plugin xBlog Slider

New plugin xBlog Slider:

• User > Plugins > Slider

0.8.8

Columns and Grids

You can setup columns and grids for list views:

• These columns are possible: 1, 2, 3, 4 and 6.

• These grid layouts for a record are possible:

  • Margin content in left or right column or at the top or bottom
  • These proportions are possible: 25/75, 33/66, 50/50, 66/33, 75/25

Drag in Wizard

New categorie xBlog with nine plugins.

Two of them are disabled.

HTML framework

• Fluid Styled Content is supported
• Foundation framework is supported

Links

Additionally supported:

• link to a page
• link to an external url
• no link

Proper links for items from

• pages (depending on page type)
• tt_content (page id with anchor)

Localisation

German translation

Plugins

New plugins:

• Datesheet
• Image
• Media
• Search

Improved plugins:

• xBlog (list- and single-view)
• xBlog Mini
• xBlog Paging

xBlog Image

Renders the images of a single view

Integration in Depth

New manual section at

• Developers > In Depth > User Functions

Process as Text with Image

xBlogMain plugin has the new tab [Item] with the property "Process as ...".

New property has the options:

• Default

  • Process the record by the fluid template of the xblog
  • Curently there isn't any adequate rendering for images
  • But the xblog default item respects the responsive framework foundation

• Text with pictures (content element). This is Work in progess

  • Process the record by TypoScript property tt_content.textpic
  • If field values of the record has same labels like an element of the tt_content table, you will get a proper image rendering. But header is missing! This is a todo.
  • This process doesn't respect the foundation framework

Session Management

See at

• Introduction > Session Management
• Developers > In Depth > User Functions > Session

User Functions

New user function ControllingUserfunc at

• Developers > In Depth > User Functions > Controlling

Plugin

New property image with setup in list views for

• position
• grid layout

Manual

New sections

• Developers > Best Practise
• Developers > Good to know
• Known Errors

Fluid templates

Improved.

Single view

Improved. But supports less fields by default.

Manual

New sections

• Administrators > Setup > Constant Editor
• Developers > In Depth > User Functions

Controlling

0.4.0

Controlling is proper:

• If an xBlog is exclusive - it handles only data, which are sent to it - it is controlled by the paging element only, which is connected with this xBlog.
• If an xBlog isn't exclusive - it handles all sended data - it is controlled by any paging element.
• Session works proper. Pointer values for each xBlog are managed proper.

typolink

0.4.0

A typolink respects the type field of an item. This enables different links to

• the single view
• an internal page
• an external URL
• to nothing.

Website

0.2.0

• https://typo3-xblog.de/

Main and Mini

0.2.0

If you have select a table you can select order field and order direction now.

Paging

0.1.0

There is a third plugin ready: [xBlog: Paging]

Mini view

There is a second plugin ready: [xBlog: Mini]

Initial Release