Skip to content

Post-email bug. #11015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
techibert opened this issue May 29, 2014 · 9 comments
Closed

Post-email bug. #11015

techibert opened this issue May 29, 2014 · 9 comments

Comments

@techibert
Copy link

After I send an email the web debugger toolbar always display an error.

Screenshot #1: Output after I send e-mail
123

Screenshot #2: Here is my code that I added to DemoController:index
234

Here is my e-mail: valdezalbertm@gmail.com
Just sent me acknowledgement e-mail that you read my e-mail.
And in case you sent me if the bug is already fixed.

Thank you.
Albert

@jakzal
Copy link
Contributor

jakzal commented May 29, 2014

Could you inspect your web server logs and Symfony logs, and paste the actual error message please?

@tucksaun
Copy link
Contributor

Since Symfony 2.4, the profiler persisting the data used by the WDT is the very last thing done by Symfony (after sending emails).
Before #10773 you would just not have see nothing displayed (no WDT either).

The alert you see means that the profiler has not been able to find the token requested in the 2500ms allowed, and emails can take a lot of time to be sent.
However if you click OK in the alert, you should be redirected to the profiler and figure out what precisely is slow.

@jakzal
Copy link
Contributor

jakzal commented Jun 1, 2014

@revelator123 any news?

@fabpot
Copy link
Member

fabpot commented Dec 24, 2014

Closing as there is no feedback from the reporter. Feel free to reopen with more information.

@fabpot fabpot closed this as completed Dec 24, 2014
@numediaweb
Copy link

This same issue is still present on Symfony 3.1

@xabbuh
Copy link
Member

xabbuh commented Aug 2, 2016

@numediaweb Please open a new issue providing the necessary information to reproduce your issue.

@safwan74
Copy link

safwan74 commented Sep 3, 2016

I also have the same issue

@xabbuh
Copy link
Member

xabbuh commented Sep 3, 2016

@safwan74 Please open a new issue providing the necessary information to reproduce your issue.

@safwan74
Copy link

safwan74 commented Sep 4, 2016

Hello xabbuh, I came to realise that it wasn't symfony issue, the problem is fixed by increasing both the max_execution_time and memory_limit in the php.ini file. I no longer see the problem with my current settings. My code had required more memory. I hope this help others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants