Hi @tzem10,

Thank you for buying our theme. We hope it will meet all your expectations! 🙂

We’ve addressed this very issue in another topic. To find out how you can resolve it, please click on the following link:

Customizer gets 500 error after editing Hero

In this topic, the user solved this issue by raising the memory limit by adding those two lines of code in the wp-config.php :

define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '256M' );

In case this doesn’t solve your issue, please activate logging on your website. Just turn WP_DEBUG to true, by pasting 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

Thank you.

Hi @tzem10,

Thank you for your feedback. Can you confirm me you raised your memory limit like I suggested you in my previous topic?

If it didn’t solve your issue, thanks to the code snippet that you’ve recently added to your wp-config.php file, we should be able to read the error.

Could you share the content of your debug.log file with us please? You can post the content of this file as plain text in your next reply and mark it as private to keep this between us.

After having reviewed your next reply, we’ll be able to tell you if the issue is caused by our product or any type misconfiguration on your server.

If we’re not able to help, we’ll recommend you to transfer the error logs to your server hosting support.

Thank you.

Hi tzem10,

Thank you for notifying of this warning. It just means some plugin codebase need to be updated.

Could you confirm that you’re still facing this 500 error and your Customizer still doesn’t work? If you’re looking for ways to hide this from your page, 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: 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 @tzem10,

Thank you for your precious feedback. We think we found from where this issue is coming from. It should be solved with the next update of Grimlock for BuddyPress.

We’ll be back to you as soon as the update is available.

Thank you for your patience.

Best,

Hi @tzem10,

Unfortunately, our development team is reduced due to vacations. Be sure that the next version is under development and should be released soon. However, no date can be disclosed.

We apologize for this inconvenience and thank you for your understanding.

Sincerely,