Hi swizzbeatz,

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

To help us getting clues and find a solution to this 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: Debugging in WordPress.

Then, could you activate Grimlock and try again? You’ll face this issue again. However, thanks to the code snippet you will have added to your wp-config.php file, we will be able to read the error. So, 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, a third party plugin or any type misconfiguration on your server. If we’re not able to help, we’ll recommend you to transfer the error logs to the plugin author or to your server hosting support.

Thank you.