Viewing 12 replies - 1 through 12 (of 12 total)
  • I’ll get on it right away and report back here! Thanks for letting me know.

    Thread Starter JJNW

    (@jjnw)

    Thanks!

    WordPress just did a minor update! It went from 3.8.3 to 3.8.4

    Just saying, if that helps, because that’s when I noticed the error.

    Thread Starter JJNW

    (@jjnw)

    And also, noticed after update… I get

    PHP Warning: json_encode() [function.json-encode]: Invalid UTF-8 sequence in argument in /home/user/public_web/website/wp-includes/update.php on line 255

    Just saying.

    Please contact me via http://jonradio.com/contact-us/ so that I can send you a fixed beta version as soon as it is ready. Both so you can test it for me, but also so I can bundle the fix into the next version of the plugin rather than doing a new version immediately.

    Thank you again.

    Thread Starter JJNW

    (@jjnw)

    Thanks. I just emailed you. I hope the new beta doesn’t upset the current working version.

    I’ll be sure to send you a version with just the change required for this. It would also be safe to run the current version with WP_DEBUG set to FALSE in wp-config.php so that the Warning does not display.

    Thread Starter JJNW

    (@jjnw)

    Wait, is there a way to supress warnings in error log?

    I am using this, but this is for development.

    Could you please clarify the full command of WP_DEBUG, because this is what I have currently in wp-config.php file:

    /**
     * For developers: WordPress debugging mode.
     *
     * Change this to true to enable the display of notices during development.
     * It is strongly recommended that plugin and theme developers use WP_DEBUG
     * in their development environments.
     */
    define('WP_DEBUG', false);

    Sorry, I completely misunderstood you. I thought you were seeing that Warning displayed on your web site.

    I was referring to WP_DEBUG ability to show or suppress messages displayed in Admin and your public WordPress site. I’m not sure, but I don’t believe it alters logging behaviour.

    That clarification (logging versus display) will also help me with my testing.

    Thread Starter JJNW

    (@jjnw)

    Oh yes, its a logging error, in the root of the site titled error_log.

    That is where I am seeing these warnings — like 10 of them of the same.

    Now I am curious on how to shut off error_log writes.

    Hmmmm, or even warnings…. mmmmm.

    I’ve never dug into PHP Error Reporting, and possible WordPress interactions with it, so I’m no help. But here is where I would start reading: http://php.net/manual/en/function.error-reporting.php

    Until you pointed it out, I had not been monitoring the error log like I should be when testing my plugins.

    Thanks for that.

    Thread Starter JJNW

    (@jjnw)

    For sure! Thanks for your plugin and the help. I don’t believe I will worry about the error at this moment. After emptying my root error_log, I haven’t seen anymore errors or warnings. I will let the website run for a few days and see if it comes back. Might have been a glitch only during minor update, that I know turne off from automatically doing.

    Thread Starter JJNW

    (@jjnw)

    Your latest version FIXED the problem!

    THANKS!

    And the upgrade went super smooth without a problem!

    THANKS!

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Does anyone knows what this means regarding line 125?’ is closed to new replies.