elao / errornotifierbundle Goto Github PK

Hello, is it possible to change the subject of a mail ?

There have been some changes to the way errors are handled in Symfony 2.6
symfony/symfony#10921
There is a new ErrorHandler interface - I was wondering whether that would be a better place to handle the errors? I haven't upgraded to 2.6 yet so I'm not too sure how it works.

I saw we can now ignore errors by a given class.. But 404s errors are all raised by Symfony\Component\HttpKernel\Exception\NotFoundHttpException.
Though there are many of them that I don't care, for example No route found for "GET /apple-touch-icon-precomposed.png" (f*ckin Apple). Would it be possible to ignore them, matching a regex for example ?
Thanks !

after last commit fb06809 we receive:

#php app/console cache:clear
PHP Warning:  ini_set(): A session is active ... /NativeFileSessionHandler.php on line 56

This seems to be caused by the 'console.command' kernel listener.

On a project recently we were getting times when we wouldn't be notified of errors. After digging into it a bit more it appears if the templating service has an error, then this bundle won't be notified of the error.

I believe the issue is that the constructor takes in the the templating engine. In our situation (FOS User bundle is installed) when the DB is down twig also fails. This is due to Twig's security extension which in turn creates the UserManager in FOSUserBundle (https://github.com/FriendsOfSymfony/FOSUserBundle/blob/v1.3.7/Doctrine/UserManager.php#L40). Calling getRepository has Doctrine try to get some meta information about the repository. This then triggers an exception as the DB is down/rejecting connections.

As this has occurred as the templating service itself is created, the ErrorNotifierBundle is never able to get it's error hooks OR to handle the kernel exception/console exception events.

I know this is a very specific use case, and on a version of FOS that is a little older, however it does highlight that this bundle has a hard dependency on the Templating which isn't completely necessary to send an error alert like the mailer dependency.

What do you think about making the templating library optional. This way if an error occurs in creation of the templating service the bundle still can handle the error. I'm not sure the best way to remove this dependency as injecting a reference to the container is generally frowned upon, however I think in this case it may be warranted. Just going with the assumption that is how it is handled we could then do the following on https://github.com/Elao/ErrorNotifierBundle/blob/master/Listener/Notifier.php#L333 . Instead of just trying it without a Try/Catch wrap that in it's own try catch and call from the container the templating service. If if fails, send out an email with just the error message and perhaps a miniaturized stack trace?

Since Sf 3.4:

ArrayNodeDefinition::requiresAtLeastOneElement() should be used instead.

See symfony/symfony@2269f70 for reference :)

Hello,

Can you add the comptability for symfony 5.x ?

Problem 1
- Installation request for elao/error-notifier-bundle ^1.1 -> satisfiable by elao/error-notifier-bundle[v1.1.0].
- elao/error-notifier-bundle v1.1.0 requires symfony/framework-bundle ~2.3|~3.0|~4.0 -> no matching package found.

it works well on dev environment but it does not send any thing when I'm on prod environment.
I have followed all installation and configuration steps and it still not working on production environment.

my current symfony version is 2.3.20

I was wondering, is there a way to use Elao ErrorNotifierBundle to manually send an email ?
Like throwing an exception without really throwing it, just send an email, with a simple call to the service.
That would be pretty useful when there is a minor problem but instead of writing it in a log file to be notified by email.

The following code will be caught by the ErrorNotifierBundle:

throw new \Exception("Error Processing Request", 1);

But the following code will just produce a blank page:

$a = null;
$a->test();

Hi
Is there a way to catch fatal errors like the old sfErrorNotifierPlugin? I assumed they were being handled by this plugin but I've recently missed one on one of my sites.

The Twig_Filter_Method class is deprecated since version 1.12 and will be removed in 2.0. Use Twig_SimpleFilter instead

Dans le fichier DumpyTwigFilter.php ligne 54,55,56

thank's

Recently working on a project I was using a third party library and they have a @list($a,$b)...to try to suppress a warning which works fine, except that the error still gets triggered to its handler (http://php.net/manual/en/language.operators.errorcontrol.php).

Since I can't change the third party library, it'd be useful to have something similar to the ignoredClasses but have a ignoredFiles (or something similar to that name) where you could specify specific files to be ignored for warnings/errors. That way you could just ignore a few files that you may not have control over but still listen to 'notices', etc. from other parts of the project.

What do you think? As for the string you could do something like the path to the file relative of the project root. Then on the handlePhpError for example see if the file is one that is ignored.

Hi thanks for a great bundle! I've got a bug in our code that's causing problems for Elao ErrorNotifier. I'm not sure what the underlying PDO issue is, any thoughts on this? Thanks!

[2017-06-13 12:59:35] request.CRITICAL: Uncaught PHP Exception Twig_Error_Runtime: "An exception has been thrown during the rendering of a template ("SQLSTATE[HY000]: General error")." at /vendor/elao/error-notifier-bundle/Resources/views/mail.html.twig line 456 {"exception":"[object] (Twig_Error_Runtime(code: 0): An exception has been thrown during the rendering of a template ("SQLSTATE[HY000]: General error"). at /vendor/elao/error-notifier-bundle/Resources/views/mail.html.twig:456, PDOException(code: HY000): SQLSTATE[HY000]: General error at /vendor/elao/error-notifier-bundle/Twig/DumpyTwigFilter.php:222)"}

I have installed the bundle and it works fine.
But the hosting company run some monitoring scripts on the hosted sites.
I receive three 404 error emails every 5 minutes for the following urls.
/.svn/format
/CVS/Root
/.git/config

I think they want to check that no version control configurations exist in the web root.
they do these checks from 2 or 3 ips.
I think we may need this feature for many other reasons.

[Symfony\Component\Debug\Exception\FatalThrowableError] Type error: Argument 1 passed to Elao\ErrorNotifierBundle\Listener\Notifier::filterRequest() must be an instance of Symfony\Component\HttpFoundation\Request, null given, called in /var/www-aura/releases/606 /vendor/elao/error-notifier-bundle/Listener/Notifier.php on line 335

Exception trace: () at /var/www-aura/releases/606/vendor/elao/error-notifier-bundle/Listener/Notifier.php:373 Elao\ErrorNotifierBundle\Listener\Notifier->filterRequest() at /var/www-aura/releases/606/vendor/elao/error-notifier-bundle/Listener/Notifier.php:335 Elao\ErrorNotifierBundle\Listener\Notifier->createMailAndSend() at /var/www-aura/releases/606/vendor/elao/error-notifier-bundle/Listener/Notifier.php:153 Elao\ErrorNotifierBundle\Listener\Notifier->onConsoleException() at n/a:n/a call_user_func() at /var/www-aura/releases/606/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/Debug/WrappedListener.php:104 Symfony\Component\EventDispatcher\Debug\WrappedListener->__invoke() at n/a:n/a call_user_func() at /var/www-aura/releases/606/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/EventDispatcher.php:212 Symfony\Component\EventDispatcher\EventDispatcher->doDispatch() at /var/www-aura/releases/606/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/EventDispatcher.php:44 Symfony\Component\EventDispatcher\EventDispatcher->dispatch() at /var/www-aura/releases/606/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/Debug/TraceableEventDispatcher.php:146 Symfony\Component\EventDispatcher\Debug\TraceableEventDispatcher->dispatch() at /var/www-aura/releases/606/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:917 Symfony\Component\Console\Application->doRunCommand() at /var/www-aura/releases/606/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:224 Symfony\Component\Console\Application->doRun() at /var/www-aura/releases/606/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php:81 Symfony\Bundle\FrameworkBundle\Console\Application->doRun() at /var/www-aura/releases/606/vendor/jms/job-queue-bundle/JMS/JobQueueBundle/Console/Application.php:45 JMS\JobQueueBundle\Console\Application->doRun() at /var/www-aura/releases/606/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:125 Symfony\Component\Console\Application->run() at /var/www-aura/releases/606/bin/console:28

I added this bundle yesterday. It is only setup for config_prod.yml. When I warmup my cache in prod mode I get the following error:

$: php app/console ca:w --env=prod --no-debug

[Symfony\Component\DependencyInjection\Exception\ServiceCircularReferenceException]
Circular reference detected for service "templating", path: "elao.error_notifier.listener -> templating -> twig".

Here is my config for the bundle:
to: ''
from: ''
handle404: true # default : false
handleHTTPcodes: ~
mailer: swiftmailer.mailer.errors
repeatTimeout: 3600
handlePHPWarnings: false # catch warnings and email them
handlePHPErrors: true # catch fatal erros and email them
handleSilentErrors: false # don't catch error on method with an @
ignoredClasses: ~
ignoredPhpErrors: ~
ignoredIPs: ~

I am on Symfony 2.6.*.

Here is the the log:
jt@mbp (master *) ~/Sites/inra23: composer update elao/error-notifier-bundle
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- symfony/framework-bundle 2.0.7 requires symfony/translator 2.0.7 -> no matching package found.
- Installation request for elao/error-notifier-bundle dev-master -> satisfiable by elao/error-notifier-bundle[dev-master].
- Conclusion: remove symfony/symfony v2.3.0
- elao/error-notifier-bundle dev-master requires symfony/framework-bundle >=2.0,<2.3-dev -> satisfiable by symfony/symfony[2.0.7, v2.0.10, v2.0.11, v2.0.12, v2.0.13, v2.0.14, v2.0.15, v2.0.16, v2.0.17, v2.0.18, v2.0.19, v2.0.20, v2.0.21, v2.0.22, v2.0.23, v2.0.9, v2.1.0, v2.1.1, v2.1.10, v2.1.11, v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.1.6, v2.1.7, v2.1.8, v2.1.9, v2.2.0, v2.2.1, v2.2.2], symfony/framework-bundle[2.0.7, v2.0.10, v2.0.12, v2.0.13, v2.0.14, v2.0.15, v2.0.16, v2.0.17, v2.0.18, v2.0.19, v2.0.20, v2.0.21, v2.0.22, v2.0.23, v2.0.9, v2.1.0, v2.1.1, v2.1.10, v2.1.11, v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.1.6, v2.1.7, v2.1.8, v2.1.9, v2.2.0, v2.2.1, v2.2.2].
- Can only install one of: symfony/symfony[v2.3.0, 2.0.7].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.10].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.11].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.12].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.13].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.14].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.15].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.16].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.17].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.18].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.19].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.20].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.21].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.22].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.23].
- Can only install one of: symfony/symfony[v2.3.0, v2.0.9].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.0].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.1].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.10].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.11].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.2].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.3].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.4].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.5].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.6].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.7].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.8].
- Can only install one of: symfony/symfony[v2.3.0, v2.1.9].
- Can only install one of: symfony/symfony[v2.3.0, v2.2.0].
- Can only install one of: symfony/symfony[v2.3.0, v2.2.1].
- Can only install one of: symfony/symfony[v2.3.0, v2.2.2].
- don't install symfony/framework-bundle v2.2.0|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.2.1|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.2.2|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.0|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.1|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.10|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.11|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.2|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.3|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.4|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.5|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.6|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.7|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.8|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.1.9|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.10|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.12|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.13|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.14|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.15|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.16|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.17|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.18|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.19|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.20|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.21|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.22|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.23|don't install symfony/symfony v2.3.0
- don't install symfony/framework-bundle v2.0.9|don't install symfony/symfony v2.3.0
- Installation request for symfony/symfony == 2.3.0.0 -> satisfiable by symfony/symfony[v2.3.0].

Potential causes:

• A typo in the package name
• The package is not available in a stable-enough version according to your minimum-stability setting
  see https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion for more details.

Read http://getcomposer.org/doc/articles/troubleshooting.md for further common problems.
jt@mbp (master *) ~/Sites/inra23:

Here is my composer.json:
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.3.",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.2.",
"twig/extensions": "1.0.",
"symfony/assetic-bundle": "2.3.",
"symfony/swiftmailer-bundle": "2.3.",
"symfony/monolog-bundle": "2.3.",
"sensio/distribution-bundle": "2.3.",
"sensio/framework-extra-bundle": "2.3.",
"sensio/generator-bundle": "2.3.",
"incenteev/composer-parameter-handler": "~2.0",
"doctrine/mongodb-odm": "1.0.@dev",
"doctrine/mongodb-odm-bundle": "3.0.@dev",
"doctrine/data-fixtures": "1.0.@dev",
"doctrine/doctrine-fixtures-bundle": "dev-master",
"knplabs/knp-paginator-bundle": "dev-master",
"stfalcon/tinymce-bundle": "dev-master",
"liip/imagine-bundle": "dev-master",
"knplabs/knp-menu": "2.0.*@dev",
"knplabs/knp-menu-bundle":"dev-master",
"cedriclombardot/admingenerator-generator-bundle": "dev-master",
"cedriclombardot/admingenerator-activeadmintheme-bundle": "dev-master",
"cedriclombardot/admingenerator-oldtheme-bundle": "dev-master",
"friendsofsymfony/user-bundle": "~2.0@dev",
"elao/error-notifier-bundle" : "dev-master"

Hi - any plans to add Symfony 4.X+ support to this?

The email.html.twig template incorrectly iterates through previous exceptions.

The problem is in this line: https://github.com/Elao/ErrorNotifierBundle/blob/master/Resources/views/mail.html.twig#L346

{% for position, e in exception.toarray %}
    {# see TwigBundle:Exception:traces.html.twig #}
    <ol class="traces list_exception" id="traces">
        {% for i, trace in exception.trace %}

The last line should be this:

        {% for i, trace in e.trace %}

The existing code iterates through the first exception over and over again, in a loop.

Hello,

I am occupying symfony 3.3 and / or 3.4, in both projects I have the same problem. I'm doing a very simple test, enter to a non-existent URL and I should send the email with the error, but it does not arrive.

Check the mailing and it works correctly (it is configured by default with spool memory).

Enter to "createMailAndSend", which return that the email was sent (sent = 1). Even replace all the content the error for send with a simple "hello" and the message "error", but this finally does not arrive, it is more, in the debug bar of symfony it also indicates me that it was sent, until here, the most logical thing would be to say that there is a problem with the shipment, but if I execute manually sending an error, this if you send it. (Issues 26)

My composer is:

"require": {
        "php": ">=5.5.9",
        "doctrine/doctrine-bundle": "^1.6",
        "doctrine/orm": "^2.5",
        "incenteev/composer-parameter-handler": "^2.0",
        "sensio/distribution-bundle": "^5.0.19",
        "sensio/framework-extra-bundle": "^3.0.2",
        "symfony/monolog-bundle": "^3.1.0",
        "symfony/polyfill-apcu": "^1.0",
        "symfony/swiftmailer-bundle": "^2.3.10",
        "symfony/symfony": "3.3.*",
        "twig/twig": "^1.0||^2.0",
        "elao/error-notifier-bundle": "*",
        "excelwebzone/recaptcha-bundle": "^1.4"
    },

My email sending config is:

swiftmailer:
    transport: 'smtp'
    encryption: "ssl"
    auth_mode:  "login"
    host:       "smtp.gmail.com"
    port:       "465"
    username:   "xxxx"
    password:   "xxxxx"
    spool:  
       type: memory

The configuration of the elao is:

elao_error_notifier:
    from: 'xxxxx'
    to: 'xxxxxxx'
    handle404: true # default :  false
    handlePHPErrors: true # catch fatal erros and email them
    handlePHPWarnings: true # catch warnings and email them
    handleSilentErrors: false # don't catch error on method with an @
    ignoredClasses: ~

Any ideas? in my Symfony 3.2 it works yet. Thanks in advance and excuse my english.

In prod env at some errors all the email body outputs to browser. All backtrace with php-code is visible to user. Yes, in production. Why it may happens?

we must add documentation about #33

Hi,

Since 2.3, FlattenException is deprecated in the http kernel component, and has been moved to the debug component. Until 2.x BC will be maintained, but now the bundle has an indirect dependency to the debug bundle, which is not loaded in prod mode. This causes an error. We added the debug bundle to the prod bundles as a quick fix, but would like refactor this.

Do you have a preferred solution for this problem? I will gladly do the PR...

Thanks!

Hi,
Thank's for this bundle.

When i update switmailer >2.5.3 elao notifier don't work.
And no error with composer.

2.5.4 / 2.5.5 / 2.6.x / 3.0.x

Can you specify or update this bundle ?

Have a good day.

[InvalidArgumentException] Template "ElaoErrorNotifierBundle::mail.html.twig" is not defined.

after changing following line in last commit an Error occurs

- <argument type="service" id="templating" />
+ <argument type="service" id="templating.engine.delegating" />

ErrorException: Catchable Fatal Error: Argument 2 passed to Symfony\Bundle\FrameworkBundle\Templating\DelegatingEngine::__construct() must be an array, string given, called in /var/www/inet-hpm/files/sf2/app/cache/dev/appDevDebugProjectContainer.php on line 385 and defined in /var/www/inet-hpm/files/sf2/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Templating/DelegatingEngine.php line 34

the service is also public = false

    <service id="templating.engine.delegating" class="%templating.engine.delegating.class%" public="false">
        <argument type="service" id="service_container" />
        <argument type="collection" /> <!-- engines -->
    </service>

when i reset to old state all works fine.

Maybe the Notifier class should listen to responses too ?

For now it only catches HttpException and miss other types of exception (PDOException for example)

Hi,

Do you plan composer support for this bundle?

Thanks

When I throw an HttpException, for example throw new HttpException(400, "Invalid parameters");, this bundle doesn't send an email.
Is it normal ? Is there a way to change that ?

Hi,

I came across this bundle via Google search and I wanted to know how is it different than Monologue email generation http://symfony.com/doc/2.7/cookbook/logging/monolog_email.html

Type error: Too few arguments to function Elao\ErrorNotifierBundle\Listener\Notifier::handlePhpError(), 4 passed in /var/www-aura/releases/688/vendor/symfony/symfony/src/Symfony/Component/Routing/Loader/YamlFileLoader.php on line 64 and exactly 5 expected

The Configuration seems to only accept a scalar, should it also take an array?

Hi,

I have this error in my application :
The template "ElaoErrorNotifierBundle::mail.html.twig" contains an error: Unknown "dumpy" filter in "ElaoErrorNotifierBundle::mail.html.twig" at line 402.

Do you know how to fix it ?

"symfony/symfony": "2.8.*",
"elao/error-notifier-bundle": "dev-master",

Thanks.

RuntimeException: No engine is able to work with the template "ElaoErrorNotifierBundle::mail.html.twig".