PHPackages                             ncuesta/nc-tracker-plugin - 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. [Utility & Helpers](/categories/utility)
4. /
5. ncuesta/nc-tracker-plugin

ActiveSymfony1-plugin[Utility & Helpers](/categories/utility)

ncuesta/nc-tracker-plugin
=========================

Actions tracking plugin for symfony 1.4

08PHP

Since Dec 27Pushed 12y ago1 watchersCompare

[ Source](https://github.com/ncuesta/ncTrackerPlugin)[ Packagist](https://packagist.org/packages/ncuesta/nc-tracker-plugin)[ RSS](/packages/ncuesta-nc-tracker-plugin/feed)WikiDiscussions master Synced 2w ago

READMEChangelogDependenciesVersions (1)Used By (0)

ncTrackerPlugin
===============

[](#nctrackerplugin)

This plugin provides a tracking mechanism for actions performed or visited on the application.

Configuration
-------------

[](#configuration)

All you need to do to have user actions tracked is add a filter to your `filters.yml` configuration file:

```
    security:  ~

    # Add this filter after the security key
    nc_tracker:
      class: ncTrackerFilter

```

By default, all actions will be tracked, but this can be easily customized by adding some configuration parameters in the application's `app.yml` file:

```
    all:
      nc_tracker_plugin:
        track_non_secure: true  # Whether non-secure actions will be tracked
        track_errors:     true  # Whether 404 errors should be tracked
        track_ajax:       true  # Whether XMLHTTPRequests should be tracked
        register_routes:  true  # Whether routes for admin module should be
                                #   automatically registered.

```

Preventing specific actions from being tracked
----------------------------------------------

[](#preventing-specific-actions-from-being-tracked)

Aside from the plugin's configuration, you can specifically state which actions should or should not be tracked. The way to do this is by adding a `isTrackable`method to your actions class that returns `true` if the action should be tracked or `false` if it shouldn't.

```
    public function isTrackable()
    {
      return false;
    }

```

If such method does not exist, the configuration of the plugin will determine whether the action is trackable or not.

For your convenience, an actions abstract class is included in the plugin for those modules that shouldn't be tracked: `ncIncognitoActions`. Just extend that class in your actions class and no action for that module will be tracked.

```
    class my_moduleActions extends ncIncognitoActions
    {
      // The actions for this module won't be tracked
    }

```

Further customization
---------------------

[](#further-customization)

Enable the `nc_tracker_entry` module for your application in your `settings.yml`file.

```
    enabled_modules: [default, nc_tracker_entry]

```

If you need it, you may secure the module by creating a `nc_tracker_entry`directory in your application's `modules` directory (not creating the whole module) and creating inside of it some files so that the whole structure matches the following structure:

```
    %SF_ROOT_DIR%/
      app/
        my_application/
          modules/
            nc_tracker_entry/       # The (incomplete) module
              config/               # Its config folder
                security.yml        # The security configuration file

```

Module / Action names translation
---------------------------------

[](#module--action-names-translation)

You may want translate the name of your modules and actions to make them more user-friendly. Lucky for you, this can be easily done! Just create an i18n catalogue named `modules` to translate the module names, and/or another one named `actions` to translate your actions.

###  Health Score

20

—

LowBetter than 13% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity4

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity41

Maturing project, gaining track record

 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.

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/95592?v=4)[Nahuel Cuesta Luengo](/maintainers/ncuesta)[@ncuesta](https://github.com/ncuesta)

---

Top Contributors

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

### Embed Badge

![Health badge](/badges/ncuesta-nc-tracker-plugin/health.svg)

```
[![Health](https://phpackages.com/badges/ncuesta-nc-tracker-plugin/health.svg)](https://phpackages.com/packages/ncuesta-nc-tracker-plugin)
```

PHPackages © 2026

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