# Re: turn off warning message on nginx **URL:** \ **Category:** NGINX\ **Created:** [February 9, 2011, 7:59pm UTC](https://www.ruby-forum.com/t/re-turn-off-warning-message-on-nginx/202966 "2011-02-09T19:59:27Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\ **Post date:** [February 9, 2011, 7:59pm UTC](https://www.ruby-forum.com/t/re-turn-off-warning-message-on-nginx/202966/1 "2011-02-09T19:59:27Z")
On Feb 9, 2011 1:31 PM, “Michael S.” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I think Jerome was working on a fastcgi\_param method to alter ini > directives from the nginx conf. IIRC. Is it available? If not then it won’t help him now. If so, please enlighten us. > On Feb 9, 2011, at 7:54 AM, Piotr K. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > > On 02/04/2011 05:30 PM, lifeisjustabout wrote: > > > > > Hi, > > > > > > Is there any command that i put in conf file to turnoff warning message > > > of joomla. > > > > > > for instance in apache .htaccess if i add php\_flag display\_errors “0” > > > it > > > doesnt show me error message anymore > > > > > > how can i get rid of this problem > > > > > > thanks in advance > > > > This is php ‘thing’, nginx have nothing to do with it. Exactly. Have you tried a Google search for “turning off PHP warnings”? I’m sure you that you will find what you need without posting here. People will be more likely to try to help you if you’ve already tried to help yourself. ---
**Author:** ![joviyach](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/7bcc69/32.png) [@joviyach](https://www.ruby-forum.com/u/joviyach)\ **Post date:** [February 9, 2011, 8:05pm UTC](https://www.ruby-forum.com/t/re-turn-off-warning-message-on-nginx/202966/2 "2011-02-09T20:05:46Z")
It would be in mail archives somewhere. Either here or on the php-fpm list. No clue on status or if it ever was done or will be done. I’m not in a position to google things right now. For all I know it was just a spitball idea. ---
**Author:** ![joviyach](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/7bcc69/32.png) [@joviyach](https://www.ruby-forum.com/u/joviyach)\ **Post date:** [February 9, 2011, 9:09pm UTC](https://www.ruby-forum.com/t/re-turn-off-warning-message-on-nginx/202966/3 "2011-02-09T21:09:48Z")
2011/2/9 Michael S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > > I think Jerome was working on a fastcgi\_param method to alter ini > > directives from the nginx conf. IIRC. PHP\_VALUE and PHP\_ADMIN\_VALUE are recognized fastcgi\_param keys. You can set only once each key (only the last will be recognized). So you have to concatenate the values: fastcgi\_param PHP\_VALUE [sendmail\_from=removed\_email\_address@domain.invalid](mailto:sendmail_from=removed_email_address@domain.invalid); or fastcgi\_param PHP\_VALUE “[sendmail\_from=removed\_email\_address@domain.invalid](mailto:sendmail_from=removed_email_address@domain.invalid) precision=42”; or fastcgi\_param PHP\_VALUE “[sendmail\_from=removed\_email\_address@domain.invalid](mailto:sendmail_from=removed_email_address@domain.invalid) \n precision=42”; You can try and make feedbacks ! ---
**Author:** ![joviyach](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/7bcc69/32.png) [@joviyach](https://www.ruby-forum.com/u/joviyach)\ **Post date:** [February 9, 2011, 9:12pm UTC](https://www.ruby-forum.com/t/re-turn-off-warning-message-on-nginx/202966/4 "2011-02-09T21:12:56Z")
When was this implemented? What version of fpm would help. ---
**Author:** ![joviyach](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/7bcc69/32.png) [@joviyach](https://www.ruby-forum.com/u/joviyach)\ **Post date:** [February 9, 2011, 9:16pm UTC](https://www.ruby-forum.com/t/re-turn-off-warning-message-on-nginx/202966/5 "2011-02-09T21:16:42Z")
Revision 298383, on Fri Apr 23 16:05:52 2010 UTC. see bug 51595 2011/2/9 Michael S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): ---
**Author:** ![joviyach](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/7bcc69/32.png) [@joviyach](https://www.ruby-forum.com/u/joviyach)\ **Post date:** [February 9, 2011, 9:28pm UTC](https://www.ruby-forum.com/t/re-turn-off-warning-message-on-nginx/202966/6 "2011-02-09T21:28:00Z")
2011/2/9 Jérôme Loyet [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > Revision 298383, on Fri Apr 23 16:05:52 2010 UTC. see bug 51595 Is it in a specific PHP version (5.3.3, 5.3.4, 5.3.5)? Sorry if I’m not savvy parsing through the logs to determine when it got committed. I’d like to blog about this so more people know about it (including myself :)) PHP\_ADMIN\_VALUE technically allows any PHP\_INI\_SYSTEM overrides as well so in theory _any_ ini value can be altered between PHP\_ADMIN\_VALUE and PHP\_VALUE right? (at that point I don’t see the need to differentiate really - why differentiate between admin and user ini values at the webserver level…) Would it be possible to make an array style mechanism like: fastcgi\_param PHP\_INI\_OVERRIDE foo=bar; fastcgi\_param PHP\_INI\_OVERRIDE “open\_basedir=/var/www/htdocs”; fastcgi\_param PHP\_INI\_OVERRIDE “pcre.backtrack\_limit=424242”; (I don’t know if nginx has this capability or not, but could make it a bit easier to configure) $.02 ---
**Author:** ![joviyach](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/7bcc69/32.png) [@joviyach](https://www.ruby-forum.com/u/joviyach)\ **Post date:** [February 9, 2011, 9:36pm UTC](https://www.ruby-forum.com/t/re-turn-off-warning-message-on-nginx/202966/7 "2011-02-09T21:36:46Z")
2011/2/9 Michael S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > 2011/2/9 Jrme L. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): > > > Revision 298383, on Fri Apr 23 16:05:52 2010 UTC. see bug 51595 > > Is it in a specific PHP version (5.3.3, 5.3.4, 5.3.5)? Sorry if I’m > not savvy parsing through the logs to determine when it got committed. > I’d like to blog about this so more people know about it (including > myself :)) since the first PHP FPM official version as it’s been commited in april. CQFD > PHP\_ADMIN\_VALUE technically allows any PHP\_INI\_SYSTEM overrides as > well so in theory _any_ ini value can be altered between > PHP\_ADMIN\_VALUE and PHP\_VALUE right? > > (at that point I don’t see the need to differentiate really - why > differentiate between admin and user ini values at the webserver > level…) for the same reasons they both exist on apache module (SYSTEM → don’t let ini\_set() function to change the value, USER → to let ini\_set() to change the value) > Would it be possible to make an array style mechanism like: > > fastcgi\_param PHP\_INI\_OVERRIDE foo=bar; > fastcgi\_param PHP\_INI\_OVERRIDE “open\_basedir=/var/www/htdocs”; > fastcgi\_param PHP\_INI\_OVERRIDE “pcre.backtrack\_limit=424242”; > > (I don’t know if nginx has this capability or not, but could make it a > bit easier to configure) It’s not possible. It’s a limitation on the fastcgi protocol which admit each keys only once. (or I missed something) ---
**Author:** ![joviyach](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/7bcc69/32.png) [@joviyach](https://www.ruby-forum.com/u/joviyach)\ **Post date:** [February 9, 2011, 9:53pm UTC](https://www.ruby-forum.com/t/re-turn-off-warning-message-on-nginx/202966/8 "2011-02-09T21:53:42Z")
On Feb 9, 2011, at 12:35 PM, Jérôme Loyet [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > for the same reasons they both exist on apache module (SYSTEM → > > > > > don’t let ini\_set() function to change the value, USER → to let > ini\_set() to change the value Ah. So if I define as admin it wont let the user override at all. I thought that was keyed in to the ini level, not the users ability to override it. Thanks. > It’s not possible. It’s a limitation on the fastcgi protocol which > admit each keys only once. (or I missed something) In theory it could be scrubbed though by nginx to fold it into a legit fastcgi param and not require the admin to define it in a funky way. But that requires some nginx magic too 🙂