Title: bug in wp-settings.php
Last modified: August 18, 2016

---

# bug in wp-settings.php

 *  [mosherabenu](https://wordpress.org/support/users/mosherabenu/)
 * (@mosherabenu)
 * [19 years, 3 months ago](https://wordpress.org/support/topic/bug-in-wp-settingsphp/)
 * Yesterday was everything ok with my weblog, but today I entered on it and there
   is the messages:
 * Strict Standards: Assigning the return value of new by reference is deprecated
   in /opt/apache/htdocs/moshe/www/wp-settings.php on line 232
 * Strict Standards: Assigning the return value of new by reference is deprecated
   in /opt/apache/htdocs/moshe/www/wp-settings.php on line 234
 * Strict Standards: Assigning the return value of new by reference is deprecated
   in /opt/apache/htdocs/moshe/www/wp-settings.php on line 235
 * Strict Standards: Assigning the return value of new by reference is deprecated
   in /opt/apache/htdocs/moshe/www/wp-settings.php on line 252
 * And it repeats also in the configurations after logged in :/
    What can be happening?
   How do I solve that?
 * You can see it: [http://www.moshe.blog.br](http://www.moshe.blog.br)
    thanks!!!

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [Class](https://wordpress.org/support/users/class/)
 * (@class)
 * [19 years, 3 months ago](https://wordpress.org/support/topic/bug-in-wp-settingsphp/#post-518926)
 * It looks like warnings (not errors) from the webserver.
    Maybe contact support
   where you have your site hosted and ask them if they changed something?
 *  [carsong](https://wordpress.org/support/users/carsong/)
 * (@carsong)
 * [19 years, 2 months ago](https://wordpress.org/support/topic/bug-in-wp-settingsphp/#post-519269)
 * > Maybe contact support where you have your site hosted and ask them if they 
   > changed something?
 * They may have changed the php.ini file to report coding standards errors found
   in source code. Or specifically they probably changed the default php installation’s
   php.ini file to:
 *     ```
       error_reporting = E_All
       display_errors = On
       ```
   
 * The `Strict Standards: Assigning the return value of new by reference is deprecated`
   is a coding standards violation in WordPress (meaning this is a defect in WordPress).
 * Deprecated means that the syntax used is eventually being phased out for something
   better.
 * Maybe a WordPress developer can look at the standards violation.
 *  Moderator [Samuel Wood (Otto)](https://wordpress.org/support/users/otto42/)
 * (@otto42)
 * WordPress.org Admin
 * [19 years, 2 months ago](https://wordpress.org/support/topic/bug-in-wp-settingsphp/#post-519270)
 * This is not a standards violation, it’s a difference between versions of PHP.
 * _Strict Standards: Assigning the return value of new by reference is deprecated…_
 * What’s going on here has to do with lines like these:
    `$variable = & new SomeObject();`
 * In PHP4, the ampersand is necessary to get the variable and not a copy of it.
   
   In PHP5, this behavior is the default and the ampersand is not needed, thus generating
   that error message when Strict mode is enabled.
 * Since WordPress is designed to work on PHP4 *and* PHP5, that ampersand is necessary
   to make it work on PHP4.
 * Therefore, you need to disable strict mode. Or, at least, disable reporting of
   E_STRICT.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘bug in wp-settings.php’ is closed to new replies.

## Tags

 * [standards](https://wordpress.org/support/topic-tag/standards/)
 * [Strict](https://wordpress.org/support/topic-tag/strict/)

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 3 replies
 * 4 participants
 * Last reply from: [Samuel Wood (Otto)](https://wordpress.org/support/users/otto42/)
 * Last activity: [19 years, 2 months ago](https://wordpress.org/support/topic/bug-in-wp-settingsphp/#post-519270)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics