---
title: Bundled Texts
url: "https://b13.com/products/vg-wort-pro-for-typo3/documentation/bundled-texts"
date: 2026-09-19
modified: 2026-09-19
lastUpdated: 2026-09-19
---

# Bundled Texts

![Black icon featuring a stylized letter "A" with sparkles, set against a light blue and green abstract background.](https://b13.com/fileadmin/_processed_/c/d/csm_sharing-ext-VGWortPro-S_9821f76de1.webp)

 Documentation
===============

 TYPO3 Extension “VG Wort Pro”
 Version 0.10.0 (2026-09-19)

  A manual, a handbook or a long article often lives on several pages. VG Wort treats that as **one** text: one pixel, one extract covering every part, one webrange listing all URLs in reading order.

  Bei einem langen Text, der sich über viele Unterseiten erstreckt, erhält jede Textseite die gleiche Zählmarken.

   When a bundle is right, and when it is not
--------------------------------------------

Use it for **one continuous text** that happens to be split across pages.

Do not use it for separate articles that share a topic. Those are separate texts and each needs its own pixel—and the reverse is the expensive half: if several genuinely separate texts share one pixel, none of them can be reported correctly.

   Creating one
--------------

1. Open the page properties of the **entry page**—the canonical URL of the text.
2. Under **VG Wort**, add the remaining pages to Further pages of this text. The **Adopt subpages** button beside the field fills it with the direct subpages in page-tree order—the usual shape of a manual—and leaves out the ones that cannot be part of the text. It only fills the field: nothing is written until you save, and the list stays editable.
3. Drag them into reading order. The list order is the reading order; there is no separate sort field.

The entry page keeps the pixel. Member pages have none of their own—they render the entry page’s pixel, which is what VG Wort requires.

  ![The VG Wort tab in the entry page’s properties: its counting pixel, its authors, and the three further pages that form one text with it, in reading order.](https://b13.com/fileadmin/_processed_/a/d/csm_Documentation-Images-page-properties-bundle_b5216c466e.webp)

  ###  What disqualifies a page

A page is refused as a member if it has its own pixel, is excluded via `tx_vgwort_ignore`, has a page type that cannot be registered ([which ones](https://b13.com/products/vg-wort-pro-for-typo3/documentation/configuration#c12683)), or already belongs to another text. The reason is shown when saving, and the **Adopt subpages** button applies the same rules before it offers anything.

   What counts
-------------

- The **minimum of 1,800 characters applies to the whole text**, not to each part. Two chapters of 900 characters each are fine.
- The second threshold at **10,000 characters** is measured over the whole text as well.
- The extract is the net text of every part, merged in reading order with a paragraph break between parts.

   Pages that must not carry a pixel
-----------------------------------

VG Wort is explicit that a pixel may only sit on pages with reportable text:

  Dürfen Zählmarken auch auf Seiten ohne meldefähigen Text eingebaut werden, die aber zum Text gehören? Nein!

  A page holding only images, adverts or quotations, and a teaser page linking to the full text, must stay out of the bundle. **Embedding a pixel there gets the pixel deactivated and the report rejected**—the most expensive mistake this feature can produce, because the pixel is then retired for good.

   After the report has been sent
--------------------------------

**Report a bundle only once the text is complete.** A sent report cannot be corrected:

  Einmal versandte Meldungen können nicht mehr korrigiert werden. Man kann nur einen neuen Webbereich ergänzen, falls der Text auf eine andere URL umzieht.

  Adding a chapter later is therefore not reportable. The module will show you that the text changed after it was prepared—a page added, removed, reordered, or an extract edited by hand—but none of it can be transmitted. If something is genuinely wrong, write to <metis.support@vgwort.de> and ask for the report to be rejected so it can be sent again correctly.

`addWebrange` remains available for what it is meant for: a reported text moving to a different URL.

   Limits checked before anything is sent
----------------------------------------

Because a rejected report can only be cleared up through support, these are checked first:

|  |  |
|---|---|
| URL length | 250 characters |
| Webranges per report | 100 |
| URLs per report | 1,000 |
| Extract, base64 encoded | 15 MB |

   Not supported
---------------

- Combining pages that were already reported individually into one bundle. VG Wort does not allow changes to sent reports; existing individual reports stay as they are.
- Texts without a page as their anchor, such as PDFs or downloads.
- Workspaces. MM relations in workspaces are a topic of their own.

 Bundled Texts