Themosaurus

Hi @webadviceguy,

Thank you for bringing this solution to our attention. You’re the best! We’ll add it to our to do list in order to fix this issue in our plugin. 🙂

Best,

Hi,

Thank you for bringing this to our attention.

I suggest that you activate error logging on your website. Please keep WP_DEBUG to true and just paste the following code lines in your wp-config.php file, just before the line that says That’s all, stop editing! Happy blogging.:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

More on this in the following topic: https://codex.wordpress.org/Debugging_in_WordPress

You will still be able to consult the warnings and errors triggered by your website but these won’t appear on your pages anymore.

Regards,

Hi @drivezone,

Thank you for bringing this issue to our attention.

These messages are PHP warnings, not errors. Unlike errors, warnings won’t break your website. They’re just messages aimed at developers to improve their code.

In most case, hiding these messages will solve this issue. I suggest that you activate error logging on your website. Please keep WP_DEBUG to true and just paste the following code lines in your wp-config.php file, just before the line that says That’s all, stop editing! Happy blogging.:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

More on this in the following topic: https://codex.wordpress.org/Debugging_in_WordPress

You will still be able to consult the warnings and errors triggered by your website but these won’t appear on your pages anymore.

Regards,

• This reply was modified 11 months, 3 weeks ago by Themosaurus.

Hi,

Just letting you know that the latest update (v1.2.8) should fix the PHP 8.2 deprecated errors that were reported 🙂

Best regards,

Hi @m4rc07,

No worries, this is a PHP warning, not an error. Unlike errors, warnings won’t break your website. They’re just messages aimed at developers to improve their code.

To hide this message, I suggest that you activate error logging on your website. Please keep WP_DEBUG to true and just paste the following code lines in your wp-config.php file, just before the line that says ‘That’s all, stop editing! Happy blogging.’:

// Enable WP_DEBUG mode<br>define( 'WP_DEBUG', true );<br><br>// Enable Debug logging to the /wp-content/debug.log file<br>define( 'WP_DEBUG_LOG', true );<br><br>// Disable display of errors and warnings <br>define( 'WP_DEBUG_DISPLAY', false );<br>@ini_set( 'display_errors', 0 );

More on this in the following topic: Debugging in WordPress

You will still be able to consult the warnings and errors triggered by your website but these won’t appear on your pages anymore.

Regards,

• This reply was modified 1 year, 4 months ago by Themosaurus.

Hi Goelsuryansh,

Thanks for reaching out!

I understand you’re trying to assign a role when a user gets verified, and I can see how that would be useful. However, since this involves specific customization and hooks, it’s important to note that this falls outside the scope of the support we provide.

While I can’t provide the exact hook you’re looking for, I suggest exploring the source code for potential actions or filters related to the verification process. Once you locate the appropriate hook, your current function setup for assigning roles should work.

For deeper customization, you might consider working with a developer to help integrate this more smoothly into your site.

I hope this points you in the right direction!

Best regards,

Hi Martin,

For the moment, we do not plan the integration of the compatibility with BuddyBoss plugin as we have a lot to work on. However, if other users mark their interest, we will consider it. 🙂

Best,

Hi,

Thanks for reporting this issue. These “Deprecated” notices are due to your server running on PHP 8.2+. Our plugin hasn’t been tested with that version of PHP and might not be fully compatible with it.

We will be updating the plugin at some point for PHP 8.2 compatibility but in the meantime the easiest solution for you is to swap to PHP 8.1 on your server. At this point I believe there are still many plugins which aren’t fully compatible with PHP 8.2 so it would generally be safer to use PHP 8.1 for now.

Please note that the “Deprecated” messages are only notices and not fatal errors. Therefore these are not responsible for things like crashing the wp-admin.

• This reply was modified 1 year, 8 months ago by Themosaurus.