---
title: "Changelog"
manual: "fixpunkt/fp-social"
version: "main"
permalink: "https://docs.typo3.org/permalink/fixpunkt/fp-social:changelog@main"
source: "Changelog/Index.rst"
modified: "2026-09-17T09:45:28+00:00"
---

# Changelog

## Unreleased

-   Posts that were hidden in the backend module stay hidden. Until now the
    synchronization did not find them again and imported them a second time as
    a visible copy. The same happened on accounts that require approval, where
    every post that had not been approved yet was duplicated on each run. The
    new command `fp_social:removeduplicates` cleans up the copies that were
    already created, see [Scheduler Task](https://docs.typo3.org/permalink/fixpunkt/fp-social:scheduler-task@main).
-   The social server now limits how often its API may be called -- requests to
    the same social media profile and the overall number of requests are each
    capped per API user. Synchronization no longer treats a reached limit as a
    failure: short blocks are waited out and the request is retried, longer ones
    postpone the account to the next run. The new extension setting
    **rateLimitWaitThreshold** decides where that boundary is, see
    [Request limits of the social server](https://docs.typo3.org/permalink/fixpunkt/fp-social:rate-limit@main).
-   Accounts carry a new read-out field **Synchronization postponed
    until**. As long as it lies in the future, the scheduler task skips the
    account. Clear it to try again right away.
-   The deep synchronization in the backend module now pauses and continues on
    its own when a limit is reached instead of stopping with an error.
-   Requests to the social server now use a connect timeout of 10 and a read
    timeout of 30 seconds. Previously a hanging server could block a
    synchronization run indefinitely.
-   Requires `fixpunkt/fp-social-bridge` 1.5 or newer.
-   An answer of the social server that cannot be used is reported with a
    message that names the cause: a mismatching protocol version and an unknown
    response type each state what does not fit and what helps, instead of the
    technical message of `fp_social_bridge`. See [When the answer does not fit](https://docs.typo3.org/permalink/fixpunkt/fp-social:unusable-answer@main).
-   Accounts can now be filled in from the SocialServer: at the top of the
    **Setting** section the button **Configure account
    automatically** offers all channels that are connected to the selected
    credentials, and one click writes channel and label into the record. If the
    chosen channel belongs to another network, the record is saved and the
    network is switched along with it. See [Managing accesses and accounts](https://docs.typo3.org/permalink/fixpunkt/fp-social:access-and-accounts@main).
-   Added support for Instagram accounts that are connected through the direct
    Instagram login instead of a Facebook page.
-   Added compatibility with TYPO3 v14. The extension now supports TYPO3 v12.4,
    v13.4 and v14.4.
-   For TYPO3 v13 and v14 the TypoScript can now be loaded via the site set
    **Social Wall** (`fixpunkt/fp-social`). The static template
    remains available for TYPO3 v12. See [Installation](https://docs.typo3.org/permalink/fixpunkt/fp-social:installation@main).
-   Removed usage of APIs that were deprecated or removed in TYPO3 v14.
-   The plugins now live in an own group **Social Wall** in the content
    element wizard and in the type selector. For TYPO3 v12, where the wizard is
    not generated from the TCA, the entries are provided via page TSconfig.
-   The plugin, palette and tab labels of the content elements are localized
    now, and both plugins have their own icon.