seanking2919

Hi @pfefferle,

I use PHP version 7.3.13

Alright. So, some update: I was able to resolve that error from the debug log by changing this code in line 474:

$trusted_sites = get_user_meta( $user->ID, 'openid_trusted_sites', true );

To this:

$trusted_sites = (array) get_user_meta( $user->ID, 'openid_trusted_sites', true );

That being said, I still get the “Could not verify assertion with provider” error, even after installing the recommended GMP module for PHP.

• This reply was modified 4 years, 10 months ago by seanking2919.

I just found this when turning on debug logs:

[07-Jan-2020 17:42:40 UTC] PHP Warning: Illegal string offset ‘c13bae18d148980b423ca9117739711d’ in /var/www/html/wp-content/plugins/openid/server.php on line 477
[07-Jan-2020 17:42:40 UTC] PHP Notice: Array to string conversion in /var/www/html/wp-content/plugins/openid/server.php on line 477

Here’s the debug code given:

Fatal error: Uncaught Error: Call to undefined function register_block_type() in /var/www/html/wp-content/plugins/avatar-privacy/includes/avatar-privacy/components/class-block-editor.php:99
Stack trace:
#0 /var/www/html/wp-includes/class-wp-hook.php(286): Avatar_Privacy\Components\Block_Editor->register_blocks(”)
#1 /var/www/html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#2 /var/www/html/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
#3 /var/www/html/wp-settings.php(456): do_action(‘init’)
#4 /var/www/html/wp-config.php(118): require_once(‘/var/www/html/w…’)
#5 /var/www/html/wp-load.php(37): require_once(‘/var/www/html/w…’)
#6 /var/www/html/wp-admin/admin.php(31): require_once(‘/var/www/html/w…’)
#7 /var/www/html/wp-admin/index.php(10): require_once(‘/var/www/html/w…’)
#8 {main}
thrown in /var/www/html/wp-content/plugins/avatar-privacy/includes/avatar-privacy/components/class-block-editor.php on line 99

Yeah, I used 2.2.1 before 2.2.2

Hi guys,

Since it seems that the person behind this plugin has abandoned the project for the most part and not done an update in over a year, I decided to take it into my own hands to fix this. And I actually was easily able to. Here’s how to fix the textdomain error:

1. Login using FTP or SFTP and go to the directory where the files for the plugin are: wherever_your_wordpress_installation_is/wp-content/plugins/custom-background-changer

2. Open the custom-background-changer.php file in an editor like Notepad++

3. Find all the spots in the code that say $textdomain and replace all of them with ‘custom_background_changer’.

4. Delete the line stating $textdomain = ‘custom_background_changer’;

5. Save changes to the file.

And it should be no longer giving textdomain errors and hopefully, still working just fine.

• This reply was modified 5 years, 5 months ago by seanking2919.
• This reply was modified 5 years, 5 months ago by seanking2919.

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

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 [email protected] and I’ll get you setup with a temporary login.

• This reply was modified 5 years, 5 months ago by 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.

Ok. I got it fixed apparently. Never mind.

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.

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

Where would I find the error logs?

Alright. Sounds good. I’m thinking I’ll try out that “integrated” variant you say you have a proof-of-concept for.

Ok. So before I give my preferred solution. I want to show what the main issue is. The main issue behind this from what I see is that the avatar upload sections are totally separate. Avatar Privacy Section: https://files.catbox.moe/49nr71.PNG and WP User Manager section for avatar upload: https://files.catbox.moe/seej24.PNG

With that issue being said, I think disabling Avatar Privacy’s built-in avatar uploads would be the best solution IMO. If you recommend otherwise, let me know.