Support » Plugin: Avatar Privacy » WP User Manager compatibility not working and default avatar keeps changing

  • Resolved seanking2919

    (@seanking2919)


    Hi guys,

    So apparently as of this morning, the default avatar was changed and I didn’t even notice it. And then the WP User Manager compatibility stopped working.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author pepe

    (@pputzer)

    @seanking2919, did you update WP User Manager? Because the only change in Avatar Privacy 2.2.1 was Windows compatibility.

    If neither plugin was updated, please check what else has changed on your installation – maybe there’s something in the error logs?

    seanking2919

    (@seanking2919)

    Where would I find the error logs?

    seanking2919

    (@seanking2919)

    Well there’s nothing in the official error log that I know of. :/

    Plugin Author pepe

    (@pputzer)

    I meant your PHP error logs. Where they are (or whether they are even enabled) depends on your hosting.

    Plugin Author pepe

    (@pputzer)

    @seanking2919 Did you change anything before you noticed the strange behavior? What was the default avatar changed into? Does Avatar Privacy work otherwise (i.e. is it activated)? Did you maybe trigger the fatal error recovery mode (new in WordPress 5.2)?

    seanking2919

    (@seanking2919)

    I’m thinking this might be a sudden issue with WP User Manager’s end. Tried doing a fresh reinstall of Avatar Privacy and the cross-compatibility was still not working. Will keep you updated.

    seanking2919

    (@seanking2919)

    Did a fresh reinstall of WP User Manager and it didn’t work either. Not sure what it is that’s causing the WP User Manager cross-compatibility to not work.

    Plugin Author pepe

    (@pputzer)

    Are you sure Avatar Privacy is still activated and that Recovery Mode has not been triggered?

    Plugin Author pepe

    (@pputzer)

    @seanking2919 Do you have a link to the page in question, BTW?

    seanking2919

    (@seanking2919)

    Alright. So, the sites use ClassicPress. If you’ve never heard of it, it’s basically a fork of WordPress pre-version 5.0 without Gutenberg. If you want to see the issue about cross-compatibility for yourself, please contact me at sean.king@sandiamesa.com and I’ll get you setup with a temporary login.

    Plugin Author pepe

    (@pputzer)

    Hi @seanking2919! Can you confirm that the issue has been solved by fixing the server’s SSL certificate? That’s what gleaned from your mail.

    Yes. So apparently, the issue was not anything to do with the plugins themselves. If you use Query Monitor and you find an OpenSSL error, that usually means the certificate on the server needs to be verified by OpenSSL. If it’s self-signed, you’re gonna need to make an exemption. See this tutorial on how to do it for OpenSSL: https://www.madboa.com/geek/openssl/#how-do-i-get-openssl-to-recognize-verify-a-certificate

    Plugin Author pepe

    (@pputzer)

    Thanks!

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.