Problem after upgrading to 1.3.8

  • Resolved jeffb29

    (@jeffb29)


    11 years, 3 months ago

    I was running version 1.3.7 of your plugin and everything was running fine, however when I upgraded to the newest version I received the following error message on the admin backend (everything still appeared normal on the front end of the website).

    Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in wp-includes/functions.php on line 3495

    I reverted back to version 1.3.7 and everything is working fine again. Does anyone have any insight into this issue? Thanks!

    https://wordpress.org/plugins/floating-social-media-icon/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Acurax Technologies

    (@acurax)

    11 years, 3 months ago

    Thanks for being with us, Thanks for reporting, We have just issued a minor fix release, please try updating now and let us know.

    In earlier versions we had a code error_reporting(0); to hide the php errors and notices, and that was an accident/mistake from our side that we not removed it, In version 1.3.8 we have removed that and so, if there is an error or notice in php, it will display.

    if this code is present, all errors and warnings will get hidden, But that’s not a good practice. We accidentally forgot to remove that code on earlier versions and in this version we fixed our mistake too.

    Plugin Author Acurax Technologies

    (@acurax)

    11 years, 3 months ago

    Hello,

    It also looks like WP_DEBUG is enabled on your wordpress installation.

    Make sure to turn off your debug mode in your wp-config.php file. To do this, edit your wp-config.php in your wordpress root folder. Go to the line that says (around line 81):

    define('WP_DEBUG', true);

    and change it to:

    define('WP_DEBUG', false);

    You should enable this only on your production site.

    Thread Starter jeffb29

    (@jeffb29)

    11 years, 3 months ago

    Thanks for the quick response. The problem turned out to be another plugin that was deprecated. The error was appearing because of the error_reporting situation that you mentioned above. I’ve upgraded to 1.3.8 now and everything is working fine, thanks!

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

The topic ‘Problem after upgrading to 1.3.8’ is closed to new replies.