PHPackages                             castiron/typo3-plugin-rollbar - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Logging & Monitoring](/categories/logging)
4. /
5. castiron/typo3-plugin-rollbar

ActiveTypo3-cms-extension[Logging & Monitoring](/categories/logging)

castiron/typo3-plugin-rollbar
=============================

A Rollbar integration for TYPO3 (https://rollbar.com)

2.2.1(8y ago)114GPL-2.0+PHP

Since Jan 26Pushed 6y ago10 watchersCompare

[ Source](https://github.com/castiron/typo3-plugin-rollbar)[ Packagist](https://packagist.org/packages/castiron/typo3-plugin-rollbar)[ Docs](https://github.com/castiron/typo3-plugin-rollbar)[ RSS](/packages/castiron-typo3-plugin-rollbar/feed)WikiDiscussions master Synced today

READMEChangelogDependenciesVersions (7)Used By (0)

Rollbar integration for TYPO3
=============================

[](#rollbar-integration-for-typo3)

This is more or less the Rollbar library with autoload and config conventions.

### A note on composer mode

[](#a-note-on-composer-mode)

To make this plugin compatible with TYPO3 installations in both "[Composer mode](https://wiki.typo3.org/Composer#TYPO3_7LTS_and_later)" and legacy non-Composer mode, we cannot "require" Rollbar automatically in `composer.json` (sorry!). That's because, even in non-composer mode, TYPO3 (v6, for example) will throw an error that `rollbar/rollbar` is not present in the system, because (apparently) TYPO3 reads the `composer.json` file and tries to understand dependencies based on it, regardless of which mode you're using.

So: If you include this plugin via Composer (using Composer mode), you will need to manually include the dependency `rollbar/rollbar` along with it -- it will be suggested but not auto-installed as a dependency.

### A note on autoloading (non-Composer mode)

[](#a-note-on-autoloading-non-composer-mode)

We don't include the Rollbar library with this extension. If you're including this plugin the old-school way (through the extension manager, or via a Git submodule), you won't have the Rollbar library or its internal dependencies on hand. You must autoload them with Composer. One way to do this is like so:

1. Add composer.json to your project root, adding `rollbar/rollbar` as a dependency
2. `composer install`
3. Include the composer `vendor/autoload.php` in the project by `require_once`ing it from the top of the file `typo3conf/AdditionalConfiguration.php`.
4. If you're using a deployment system (like Capistrano) or other automated deployment approach, you'll need to be sure and add a `composer install` step to your deployments 😉

### Quick start

[](#quick-start)

The config can be specified like

```
/**
 * Rollbar config
 */
$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['rollbar'] = array(
    'rollbar_enabled' => true, // You can use this to turn it off/on
    'rollbar_config' => array(
        'access_token' => '[my-server-side-access-token]',
        'environment' => 'my-environment-name', // This is arbitrary and will scope your reporting in Rollbar
    ),
    /**
     * These are defaults
     */
//    'set_exception_handler' => false,
//    'set_error_handler' => false,
//    'report_fatal_errors' => true,
);

/**
 * Initialize Error Handling. Do this after the rollbar config. The error handling must get
 * instantiated early on, which is why we don't use helper methods from ExtensionManagementUtility, etc.
 */
require_once(PATH_site . 'typo3conf/ext/rollbar/Classes/Utility/Initializer.php');
\CIC\Rollbar\Utility\Initializer::initErrorHandling();

```

Put that in your `typo3conf/AdditionalConfiguration.php`. In general, stuff you put in there is passed directly to `Rollbar::init()`, so you can use [any of the options supported by Rollbar::init()](https://rollbar.com/docs/notifier/rollbar-php/#configuration-reference)

NB: The "root" config value (for path mapping with your SCM repo) will be automatically assigned to `PATH_site` for you, unless you override it by specifying a value yourself.

If you're using the default `set_exception_handler=false` and `set_error_handler=false`:

- You'll still get any fatal errors automatically
- You can manually catch/report exceptions like so:

```
try {
    // ... do a lil dance
} catch (\Exception $e) {
    /**
    * Send the exception to Rollbar
    */
    \CIC\Rollbar\Utility\RollbarUtility::reportError($e);

    /**
    * Or you could do one of these:
    *
    * \CIC\Rollbar\Utility\RollbarUtility::reportWarning($e);
    * \CIC\Rollbar\Utility\RollbarUtility::reportNotice($e);
    */
}

```

#### TYPO3 Content Object Renderer exceptions

[](#typo3-content-object-renderer-exceptions)

Sometimes the TYPO3 core `ContentObjectRenderer` throws exceptions, which, in production, is amazing because your user, on the frontend, will see something like,

> Oops, an error occurred! Code: 201705082151141a71f8db

And no other exception will be thrown, nor logged. 😓

To remedy this you've got to add a little typoscript to your site. Under the "Includes" tab on your main typoscript template, add the `Rollbar Content Exception Handling` typoscript.

Best of luck to you in all your endeavors.

###  Health Score

29

—

LowBetter than 57% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity7

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity67

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~87 days

Total

5

Last Release

2978d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/334526?v=4)[Gabe Blair](/maintainers/gblair)[@gblair](https://github.com/gblair)

---

Top Contributors

[![lthurston](https://avatars.githubusercontent.com/u/202726?v=4)](https://github.com/lthurston "lthurston (1 commits)")

---

Tags

TYPO3 CMS

### Embed Badge

![Health badge](/badges/castiron-typo3-plugin-rollbar/health.svg)

```
[![Health](https://phpackages.com/badges/castiron-typo3-plugin-rollbar/health.svg)](https://phpackages.com/packages/castiron-typo3-plugin-rollbar)
```

###  Alternatives

[psr/log

Common interface for logging libraries

10.4k1.2B10.9k](/packages/psr-log)[open-telemetry/api

API for OpenTelemetry PHP.

1938.5M262](/packages/open-telemetry-api)[open-telemetry/sdk

SDK for OpenTelemetry PHP.

2326.5M315](/packages/open-telemetry-sdk)[aoe/scheduler_timeline

Logs information about scheduler task execution and displays them in a graphical timeline

126.5k](/packages/aoe-scheduler-timeline)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)