Cornerstone - calling translations incorrectly

Support
#1

Hi, I am still trying to solve a sporadic 502 error and alongside my hosts looking for anything that may be causing CPU spikes.

I am still seeing the below error relating to cornerstone, could this be causing an issue?

Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cornerstone domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. (This message was added in version 6.7.0.)

Is Cornerstone fully compatible with Wordpress 6.8.1?

#2

The text domain warning is something we are fixing in the next point release. It can be safely ignored. I’m not sure it would cause a 502 error though, that sounds like something else. Have a great day.

#3

Thank you for that

#4

You are most welcome, @chrisjdavies

#5

I am getting the same error - and appreciate (and am excited about) the update however I want to add to the post in case it could help others or if I am missing something or some step that you can advise on as it may be slightly a different issue @prakash_s? The error occurred on my end after installing the latest version of WordPress from v 6.6.2 - and it broke the site from loading. I am using X/Pro. For steps that I took during troubleshooting - I tried to deactivate and uninstall cornerstone (WP would not allow deactivation). I downloaded the latest theme version from my subscription and extracted the latest cornerstone plugin and reinstalled (where WordPress allowed me to overwrite the old files to no avail.) As a final step, I regressed the WordPress version back to 6.6.2 (error is gone) but please advise as this is on a client website. Appreciate any guidance! Thanks!

#6

Hey Christina,

Please open a separate thread for your issue as the cause might be different. In your own post, please provide the link to the website with issue and provide WP Admin logins/access in a Secure Note as well so we can check the setup and replicate it on our end to see if there’s a bug.

Thank you.