Issue Bug Closed

#110237Feature Request: Native Support for Dynamic Year Placeholders and Recurring Annual Scheduling in TYPO3 Core Summary

Henry Schlenz 07/20/26, 10:47 updated 11/14/26, 09:19

Description

Many TYPO3 installations manage seasonal campaigns, recurring advertisements, annual events, and other content that follows the same publication cycle every year.

TYPO3 Core currently does not provide native support for dynamic year placeholders or recurring annual publishing periods. As a result, editors have to perform repetitive manual updates every year.

These features should be available directly through the TYPO3 backend user interface and be usable by editors without requiring TypoScript, custom configuration, or administrator intervention.

Feature Request 1: Native Dynamic Year Placeholders

TYPO3 Core should provide built-in dynamic year placeholders that can be used by editors wherever placeholder substitution is supported.

Examples include placeholders representing:

  • Current Year
  • Next Year

The exact syntax should follow TYPO3 Core conventions to avoid conflicts with existing extensions or custom implementations.

These placeholders should be available directly within the editor interface and not require TypoScript or custom development.

Typical use cases include:

  • seasonal advertisements
  • annual events
  • recurring campaigns
  • headlines
  • teasers
  • copyright notices

This enables editorial teams to manage recurring content independently without requiring administrator support.

________________________________

Feature Request 2: Annual Recurring Publishing Periods

Introduce an optional scheduling mode (for example “Annual Repetition”) directly in the publishing settings of records supporting Start Time and End Time.

The option should be configurable through the TYPO3 backend user interface so that editors can manage recurring content themselves.

When enabled, TYPO3 would automatically repeat the configured publication period every year.

Example:

  • Start: 15 September
  • End: 1 January

The content would automatically become visible and expire every year during this period without requiring manual date adjustments.

To preserve backward compatibility, TYPO3 could automatically advance the underlying Start Time and End Time to the corresponding dates of the following year after expiration while keeping the existing scheduling logic unchanged.

Is this possible to implement in future Versions?

Thank you for your support!

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 6

  1. Benni Mack commented <span data-processor="relativetime" data-value="2026-07-21T11:38:52+00:00" > 07/21/26, 11:38 </span>

    Hey Henry,

    thanks for your request. I like it (as I know such use cases) however, it is a bit of a specific use case.

    Feature Request 1: Do you consider this as a variable? like “{currentYear}” or “1.10.{nextYear}” ?

    Feature Request 2: Is this going to be the same page again and again? We used this as a kind of a “templated page” and copy it over for each year (which could be an automation). Is this about “visibility” (start date / end date) or also about content?

  2. Henry Schlenz commented <span data-processor="relativetime" data-value="2026-07-21T16:06:05+00:00" > 07/21/26, 16:06 </span>

    Benni Mack wrote in #note-1:
    > Hey Henry,
    >
    > thanks for your request. I like it (as I know such use cases) however, it is a bit of a specific use case.
    >
    > Feature Request 1: Do you consider this as a variable? like “{currentYear}” or “1.10.{nextYear}” ?
    >
    > Feature Request 2: Is this going to be the same page again and again? We used this as a kind of a “templated page” and copy it over for each year (which could be an automation). Is this about “visibility” (start date / end date) or also about content?

    Hey Benni,

    thanks for your feedback!

    Feature Request 1

    Yes, I was thinking of variables/placeholders similar to {currentYear} and {nextYear} (the exact syntax is not important to me and should follow TYPO3 Core conventions).

    The important part is that these placeholders are available in TYPO3 Core and can be used by editors directly through the backend UI, without requiring TypoScript or custom development.

    Our organization currently uses the ###CURRENTYEAR### placeholder provided by the Bootstrap Package extension. However, we may stop using this extension in the future, so having a native TYPO3 Core solution would be beneficial.

    Feature Request 2

    This request is primarily about visibility, not about generating or duplicating content.

    The content itself stays exactly the same. Only its publication period repeats every year.

    A typical example is a seasonal advertisement or banner that should always be visible from 15 September until 1 January every year. Currently, an editor has to update the Start Time and End Time annually, even though only the year changes.

    An optional “Annual Repetition” mode could automate this while keeping the existing scheduling logic intact.

    The use case is not limited to advertisements. It also applies to recurring announcements, seasonal information, annual notices, and similar content that follows the same publication schedule every year.

    I believe this could be a useful generic scheduling feature for TYPO3 rather than something tailored to a single project.

  3. Benni Mack commented <span data-processor="relativetime" data-value="2026-11-10T15:58:49+00:00" > 11/10/26, 15:58 </span>

    Hi Henry,

    thanks for the details, that makes the use case clear. Here’s how I see the two parts and how I’d build them.

    Why an extension fits better than core, especially for the recurring periods

    - It touches every table. Start/end time is a simple date comparison on every record query, and visibility, caching and workspaces all rely on that. Recurrence inside that logic is out of scope. The realistic version is “move start/end forward by a year after expiry”. That still needs a new field on every table with start/end time, plus a background job.
    - Every project answers the details differently. Which timezone? What if the job didn’t run for two years? Do translations follow the default language or keep their own dates? Does a 29 February date become 28 February or 1 March? Should editors get a notification? Core would have to pick one answer for everybody, and an extension can pick what fits your project.
    - Faster iteration. An extension can support v13 and v14 today and change whenever needed. Core features land only in the next major version, and the API then has to stay stable for years.
    - A path into core. If many projects end up using it, that’s a strong argument to move it into core later. It could become part of a more general “scheduled actions on records” concept, which also covers scheduled publishing in workspaces.

    How to build it: recurring periods

    1. Field: add an opt-in checkbox such as tx_recurring_yearly via Configuration/TCA/Overrides/.php, only for the tables you need (tt_content, pages, maybe news). Put it next to start/end time in the access palette with ExtensionManagementUtility::addFieldsToPalette(…, ‘after:endtime’). Since v13 the database column for simple TCA types like check is created from TCA, so no ext_tables.sql is needed.
    2. Job: write a console command (#[AsCommand]) and run it daily with the scheduler’s “Execute console commands” task. It finds live records (t3ver_wsid = 0) where the flag is set and endtime < now.
    3. Date math: use DateTimeImmutable->modify(‘+1 year’) in the site’s timezone, not + 31536000 seconds (leap years). Move start and end together so periods like 15 Sep–1 Jan stay intact. Loop until endtime > now in case the job missed a year.
    4. Writes: write through DataHandler, not raw SQL. Call Bootstrap::initializeBackendAuthentication() first so it runs as the cli user. You then get history, the reference index and page cache clearing for free. Core already shortens the page cache lifetime to the next start time, so the content appears on time next year.
    5. Translations: decide whether translated records copy start/end time from the default language (allowLanguageSynchronization or l10n_mode) or get their own flag. That’s the most common surprise.
    6. Nice extra: show a small indicator such as “repeats yearly” in the page module or list module so editors understand why the dates keep moving.

    How to build it: year placeholders, if you need them before core has something

    - Listen to AfterCacheableContentIsGeneratedEvent and replace {currentYear} / {nextYear} in the generated page. That covers RTE text, headers and the page title at once, without TypoScript.
    - Listen to ModifyCacheLifetimeForPageEvent and cap the lifetime at the next 1 January 00:00. Otherwise cached pages show last year’s number for up to a day after New Year.
    - Pick a syntax that survives the RTE and doesn’t clash with anything else in your content. Plain {currentYear} passes through CKEditor unchanged.

    For core, the placeholders are the more promising part. I’d rather see them as general “editor variables”, for example also using site settings, than as a year-only special case. Feel free to open a separate feature issue for that, and let’s keep this one for the recurring periods.

    Thanks,
    Benni

  4. Georg Ringer commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2026-11-14T09:19:57+00:00" > 11/14/26, 09:19 </span>

    Hey,

    after reading the issue and the comment by benni, I am closing this for the same reason as #111417.

    This is far easier to implement as extension as it can be done feature by feature and is not bound to the strict release cycle which would mean that after a LTS release is done, no feature is allowed anymore or by for the start no need to think about workspaces.

    it would also be possible to propose this idea to get a community budget by the association but I don’t see this as a feature in the core. I hope this is ok for you and if you got any questions, please reach out to us!