PHPackages                             exploring/status - 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. exploring/status

ActiveLibrary[Utility & Helpers](/categories/utility)

exploring/status
================

Operation status announcer

2.0(2y ago)0248MITPHPPHP >=7.1

Since Jun 14Pushed 2y ago1 watchersCompare

[ Source](https://github.com/jperovic/exploring-status)[ Packagist](https://packagist.org/packages/exploring/status)[ RSS](/packages/exploring-status/feed)WikiDiscussions master Synced 3w ago

READMEChangelog (8)Dependencies (5)Versions (11)Used By (0)

ExploringStatusBundle
=====================

[](#exploringstatusbundle)

This bundle aims to help with setting controller's operation status by elimination cumbersome checking of session flash bag.

Installation (via composer)
---------------------------

[](#installation-via-composer)

To install StatusBundle with Composer just add the following to your composer.json file:

```
{
    // ...
    require: {
        "exploring/status": "dev-master"
    }
}

```

Please replace the `dev-master` with some concrete release tag, for example, 1.\*

Then run:

```
php composer.phar update

```

And register the bundle within `AppKernel.php`

```
$bundles = array(
    ....
    new \Exploring\StatusBundle\ExploringStatusBundle(),
);
```

You are ready to roll.

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

[](#configuration)

The bundle configuration is minimalistic. In order for it to work you just need:

```
exploring_status: ~
```

Operation status can be stored either in `session` (default) or `apc`. In order to use `apc` mode, depending of your php version, you might need to install it first.

This can be configured by specifying `engine` config entry:

```
exploring_status:
    engine: apc
```

Setting the operation status:
-----------------------------

[](#setting-the-operation-status)

```
$manager = $this->get('exploring_status.manager');

$manager->success('Yey, you did it!');

$manager->warning('Ok, everything went ok, but there is something fishy going on here.');

$manager->error('Couldn\'t do it :(');
```

Retrieving the operation status:
--------------------------------

[](#retrieving-the-operation-status)

You can do it from within controller or from `Twig` directly.

**PHP:**

```
$manager = $this->get('exploring_status.manager');

// Get first status, if exists
// This returns object of `StatusObject` type
$status = $manager->first();

// Get all status messages
// This returns `array` of `StatusObject` objects
$all = $manager->all();
```

**Twig:**

```
{# This prints first status message directly #}
{{ ExploringStatus_First() }}

{# This prints all status messages directly #}
{{ ExploringStatus_All() }}
```

Twig templates can be overridden easily. Please see [the official documentation](http://symfony.com/doc/current/cookbook/bundles/inheritance.html#overriding-resources-templates-routing-etc) for how-to.

Message groups:
---------------

[](#message-groups)

Status messages can be grouped. In fact, when you set the status message goes to `Default` group by default.

```
$manager = $this->get('exploring_status.manager');

// This message will go into `happiness` group
$manager->success('Yey, you did it!', 'happiness');

// This one goes into `Default`
$manager->warning('Ok, everything went ok, but there is something fishy going on here.');

// This one goes into `Fatal`
$manager->error('Couldn\'t do it :(', 'Fatal');
```

As for retrieving same rule applies as defined above - you only need to pass group name as argument.

**PHP:**

```
// Get first status from group `happiness`
// This returns object of `StatusObject` type
$status = $manager->first('happiness');

// Get all status messages from group `Fatal`
// This returns `array` of `StatusObject` objects
$all = $manager->all('Fatal');
```

**Twig:**

```
{# This prints first status message directly #}
{{ ExploringStatus_First('happiness') }}

{# This prints all status messages directly #}
{{ ExploringStatus_All('Fatal') }}
```

###  Health Score

29

—

LowBetter than 57% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity13

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity64

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 ~384 days

Recently: every ~5 days

Total

10

Last Release

944d ago

Major Versions

1.8 → 2.02023-12-02

PHP version history (2 changes)1.0PHP >=5.3.3

2.0PHP >=7.1

### Community

Maintainers

![](https://www.gravatar.com/avatar/6410e1381689a1204c909d14aa4b6843f5c4a8649a7d12b82856cf3b1bc7a2ed?d=identicon)[jperovic](/maintainers/jperovic)

---

Top Contributors

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

### Embed Badge

![Health badge](/badges/exploring-status/health.svg)

```
[![Health](https://phpackages.com/badges/exploring-status/health.svg)](https://phpackages.com/packages/exploring-status)
```

###  Alternatives

[easycorp/easyadmin-bundle

Admin generator for Symfony applications

4.3k17.9M388](/packages/easycorp-easyadmin-bundle)

PHPackages © 2026

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