500 (Internal Server Error), cannot load parts of my website through cornerstone

[c_economides]

This is a new thread, created at the request of the support staff.
Here is a link to the other thread where I first posted about this issue:

https://theme.co/apex/forum/t/replicating-https-theme-co-x-header-look-with-pro-theme/

To quote myself in regard with the issue:

Hello,

I am having trouble accessing the Pro module to work on my site, I keep getting this error:

"The preview could not load. This is most often related to a plugin conflict or aggressive page cacheing. Checking the developer console for errors could indicate what went wrong.

Origin URL: https://ultimatecell.bg

Preview URL: https://ultimatecell.bg/"

Can you please take a look at it and let me know what’s wrong?
It worked fine a couple of days ago when I last worked on it. I have seen the same error here and there, but it always went away after I reloaded the page a couple of times, not this time though.

Thank you.

[mldarshana]

Hi There,

I have switched to your parent Pro theme, then re-installed Pro theme and when testing, I was able to load your Pro editor. Could you please try testing on your end as well and see if that helps.

In case if you’re getting further errors, try enabling WordPress debug_mode. Please check this https://codex.wordpress.org/Debugging_in_WordPress and enable your site’s WP_DEBUG and WP_DEBUG_LOG. Then test the loading your pages again (to retrigger the error) and download the debug.log file from /wp-content/ folder of your site through FTP. Then please provide the log file’s content in your reply here.

Thanks!

[c_economides]

“The caldera forms” page has always loaded fine.
We all get the error when trying to load either the “Home” page or the “main menu” header in cornerstone.

I will follow your instructions and provide the log later today.

Thank you.

[rad]

Hi @c.economides,

Yes, please let us know. And some instructions on how to reproduce the issue so we could trigger the error too. If debug.log isn’t generated, then maybe you can also request an error log from your hosting usually named error_log file.

Thanks!

[c_economides]

I have added the followin in wp-config, but i havent managed to generate a log file:

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);

after contacting my hosting provider, this is what he managed to provide me with:

PLease check below logs

[28-Aug-2018 21:55:04 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/oakcidsx/public_html/wp-content/themes/pro/cornerstone/includes/views/elements/tabs.php on line 40
[28-Aug-2018 21:55:04 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/oakcidsx/public_html/wp-content/themes/pro/cornerstone/includes/views/elements/tabs.php on line 73
[28-Aug-2018 21:55:54 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/oakcidsx/public_html/wp-content/themes/pro/cornerstone/includes/views/elements/tabs.php on line 40
[28-Aug-2018 21:55:54 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/oakcidsx/public_html/wp-content/themes/pro/cornerstone/includes/views/elements/tabs.php on line 73

[paul.r]

Hi,

It looks like some characters in your tabs are causing the issue.

Try to enable skeleton mode then remove your tabs and check if cornerstone will load.

This is so we can narrow down what is causing the issue.

Make sure to backup your content before doing this.

Thanks

[c_economides]

Hello,

I have removed all tabs as instructed. I still get the error when loading either ‘Main menu’ header or the ‘Home’ page.

I have to say this is starting to become really frustrating.

[rad]

Hi @c.economides,

They are just warnings, and it should be fatal error if it’s due to internal server error. There is no issue with the tabs, may I know your latest admin and FTP login credentials in a secure note?

I like to trigger it and check the logs. And how do you trigger the internal server error?

Thanks!

[c_economides]

It triggers when trying to load either ‘Main menu’ header or the ‘Home’ page in the editor.

Ftp credentials are in the secure note.

[christian]

Hey @c.economides,

I’m sorry but I could not replicate the issues you’ve mentioned. There’s no internal server error and your pages load up fine in the Content Builder. The Header builder also works fine and I’ve also activate Caldera Forms and added the shortcode in your Caldera Form Preview test page.

Would you mind giving us a screen recording so we could see exactly what is happening on your end. You can use https://www.useloom.com/ for that.

Thanks.

[c_economides]

Very interesting thing happened. As you noticed, the error disappeared on it’s own. I can confirm that I didn’t do anything that fixed it. It just went away on its own.
Since then the editor has worked as expected, without any issues. Until today, when it appeared out of the blue and to the best of my knowledge not as a consequence of something I did on the site, since I wasn’t actively developing it before it happened.
Fortunately, I made a backup using updraftplus yesterday, while everything was working normally. So after the error appeared again today, I deleted my entire wp site and restored the backup. Well, guess what the error is still there.
This leads me to believe that the error is server related and has nothing to do with pro theme, plugins or anything else related to the wp site. The hosting provider denies this, saying that they see no php or mysql errors when the error appeared again.
Can you please run my current site in a sandbox (I have included the wp-admin credentials in a secure note) as you did before to confirm the ‘Home’ page in Content loads without any errors in cornerstone? I would do it myself, but I lack the technical knowledge to do it.

Thank you.

[c_economides]

i played around with xampp and my current wp site in a sandbox.
but this is the error i get when i try to load it locally:

Fatal error: Uncaught Error: Call to a member function get_element_names() on boolean in C:\xampp\htdocs\wordpress\wp-content\themes\pro\cornerstone\includes\classes\elements\class-element-front-end.php:28 Stack trace: #0 C:\xampp\htdocs\wordpress\wp-includes\class-wp-hook.php(286): Cornerstone_Element_Front_End->register_shortcodes(’’) #1 C:\xampp\htdocs\wordpress\wp-includes\class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #2 C:\xampp\htdocs\wordpress\wp-includes\plugin.php(453): WP_Hook->do_action(Array) #3 C:\xampp\htdocs\wordpress\wp-settings.php(471): do_action(‘wp_loaded’) #4 C:\xampp\htdocs\wordpress\wp-config.php(89): require_once(‘C:\xampp\htdocs…’) #5 C:\xampp\htdocs\wordpress\wp-load.php(37): require_once(‘C:\xampp\htdocs…’) #6 C:\xampp\htdocs\wordpress\wp-blog-header.php(13): require_once(‘C:\xampp\htdocs…’) #7 C:\xampp\htdocs\wordpress\index.php(17): require(‘C:\xampp\htdocs…’) #8 {main} thrown in C:\xampp\htdocs\wordpress\wp-content\themes\pro\cornerstone\includes\classes\elements\class-element-front-end.php on line 28

any ideas?

[rad]

Hi @c.economides,

Looks like your installation is incomplete, please delete your current cornerstone and re-install it again. That’s a core function and it shouldn’t be missing.

Thanks!