---
title: "Troubleshooting"
manual: "Context Reporter"
version: "0.3"
permalink: "https://docs.typo3.org/permalink/priebera/typo3-context-reporter:troubleshooting@0.3"
source: "Troubleshooting/Index.rst"
rendered: "2026-10-02T13:52:47+00:00"
---

# Troubleshooting {#troubleshooting}

## The report button is missing {#troubleshooting-no-button}

-   Reporting can be disabled for users and groups with
    `options.contextReporter.enable = 0` or for everybody with
    [general.enabled](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:confval-setting-general-enabled@0.3).
-   The tile view of the file list has no action buttons. Switch to the list
    view or use the context menu of the file or folder.
-   If your project sets `options.file_list.primaryActions` itself, add
    `contextReporterReport`, see [User TSconfig](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:configuration-tsconfig@0.3).
-   Content elements in the Page module have no report button. Use their
    **⋮** menu.
-   After an update, flush the caches and reload the backend.

## The dialog says the object is not available {#troubleshooting-not-available}

The dialog only accepts objects that the reporter can access. The message
"The selected page, record, file or folder is not available to you." appears
when the page, record, file or folder

-   is outside the web mounts, file mounts or permissions of the reporter,
-   belongs to another workspace than the current workspace of the reporter,
-   is file metadata of a file the reporter cannot access, or
-   has been deleted in the meantime.

Report the problem from the toolbar instead: the report then refers to the
backend view.

## The report shows the default language {#troubleshooting-language}

Pages are reported in the language selected in the Page module, the Preview
module or another module with the page tree, see [Language](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:usage-language@0.3). The
default language is used when

-   several translations are shown side by side,
-   the page is not translated into the selected language (in the current
    workspace),
-   the reporter may not edit the selected language, or
-   the page was reported from a module without page tree.

## The visibility settings do not match the website {#troubleshooting-visibility}

The dialog lists the settings stored in TYPO3 when it opened, see
[Visibility settings](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:usage-visibility@0.3). The website can differ because of cached pages,
a reverse proxy or CDN, the template, extensions or the visitor's login.
Restrictions of parent pages ("Extend to subpages") are only listed for
reporters who may edit that field, and only up to the first parent page they
can access.

## The report has no website address {#troubleshooting-website-address}

The **Website address** findings say why, see
[Website address](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:usage-website-address@0.3): the page belongs to no site, TYPO3 offers no
view for its page type (folders, spacers, or page TSconfig
`TCEMAIN.preview.disableButtonForDokType`), the site has no such language,
or the page is deleted in the reporter's workspace. Records with their own
detail page, e.g. news, get the address of the page they are stored on only.

## The context menu of a file or folder shows an error {#troubleshooting-context-menu}

TYPO3 13.4 and 14.3 fail with "Call to a member function
checkActionPermission() on null" when the context menu of a file or folder
is opened that TYPO3 cannot find any more, for example because it was
deleted, renamed or moved after the file list was loaded. The error comes from
the file list of TYPO3 and also occurs without Context Reporter. Reload the
file list. Context Reporter leaves its **Report a problem** item out
for files and folders it cannot resolve or access.

## A file of the wrong type is not mentioned in the file checks {#troubleshooting-file-types}

The file checks name the file types TYPO3 removes when the record is saved,
see [File checks](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:usage-file-checks@0.3). The type is the extension of the file name, not
the extension stored in the file index. Image fields allow the image file types
of TYPO3 (`$GLOBALS['TYPO3_CONF_VARS']['GFX']['imagefile_ext']`), which
include `pdf`, `ai` and `svg` by default, so a PDF in an image field is
not a problem for TYPO3.

## The permission facts look complete, but the record cannot be edited {#troubleshooting-permissions}

The permission facts are inputs of TYPO3's checks, not its decision, see
[Permission facts](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:usage-permissions@0.3). Workspace rules, hooks and extensions can deny
editing anyway. Use **Switch to user** in the Backend users module to
see the backend as the reporter does.

## The Extension Manager says the extension is not available {#troubleshooting-classic-upload}

In classic mode, the upload of the ZIP file ends with "Extension
context_reporter is not available" when the Extension Manager installs
uploaded extensions automatically. Switch off the automatic installation,
upload the file again and activate the extension, see
[Classic mode](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:installation-classic@0.3).

## Reports do not arrive by email {#troubleshooting-email}

Open **System > Context Reports > Settings > Email** and check the
**Status** panel, see [Email status and test email](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:configuration-email-status@0.3). In most
cases email delivery is switched off, no recipient is saved, or the TYPO3
mail transport is `null`, `mbox`, a spool or a local mail catcher such as
Mailpit in DDEV. Use **Send test email** after every change. The
delivery history of a report shows transport errors without credentials.

## Webhook deliveries fail {#troubleshooting-webhook}

-   Check the **Status** panel on the **Webhook** tab and use
    **Send test webhook**.
-   The endpoint must use HTTPS unless
    [webhook.allowInsecureHttp](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:confval-setting-webhook-allowinsecurehttp@0.3) is enabled, and must answer
    with a `2xx` status code. Redirects are not followed.
-   A missing environment variable is shown as such in the status panel.
-   The delivery history shows the HTTP status code and the beginning of the
    response body.
-   Slow endpoints fail after [webhook.timeout](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:confval-setting-webhook-timeout@0.3) seconds.
-   For the n8n workflow, see [Troubleshooting](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:integration-n8n-troubleshooting@0.3).

## A report with a screenshot cannot be sent {#troubleshooting-screenshot}

-   The screenshot is larger than
    [reporting.maxScreenshotSizeKb](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:confval-setting-reporting-maxscreenshotsizekb@0.3) after compression.
-   PHP rejects the request: `upload_max_filesize` and `post_max_size`
    must be larger than the screenshot limit.
-   The database rejects the query: `max_allowed_packet` of MariaDB or
    MySQL must be larger than the screenshot limit, see
    [Storage](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:privacy-storage@0.3).

## Screen capture is not offered {#troubleshooting-capture}

Screen capture needs a secure context (HTTPS) and a desktop browser with the
Screen Capture API. If the browser does not offer it, or the reporter
declines the picker, upload an image or paste it from the clipboard.

## Copying does not work {#troubleshooting-copy}

Browsers can block clipboard access, especially without HTTPS. TYPO3 then
shows "Could not be copied to clipboard". Use **Download** instead.

## The report history shows a database error {#troubleshooting-database}

The database schema is older than the extension. Run
`vendor/bin/typo3 extension:setup` or
**Admin Tools > Maintenance > Analyze Database Structure**, see
[Updating the extension](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:upgrade-procedure@0.3).

## A setting cannot be changed {#troubleshooting-readonly}

Settings that are set in
`$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['context_reporter']` are
read-only in the module, see [Where settings are stored](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:configuration-storage@0.3).

If the settings page says that settings of a development version take
precedence, `config/system/settings.php` still contains a
`context_reporter` entry below `EXTENSIONS` from a pre-release
installation. Remove that entry and configure the extension in
**System > Context Reports > Settings**.

## Old reports are not removed {#troubleshooting-retention}

The default retention keeps reports forever, and the cleanup only runs when
it is started. Configure [reporting.retentionDays](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:confval-setting-reporting-retentiondays@0.3) and
schedule `vendor/bin/typo3 context-reporter:cleanup`, see
[Retention and cleanup](https://docs.typo3.org/permalink/priebera/typo3-context-reporter:usage-retention@0.3).