WordPress 4.8.2
Pro theme 1.2.0
Cornerstone, “Content failed to save” error.
I noticed this after updating to Pro theme v1.2.0
–deleted–
WordPress 4.8.2
Pro theme 1.2.0
Cornerstone, “Content failed to save” error.
I noticed this after updating to Pro theme v1.2.0
–deleted–
Hey There,
Would you mind providing us with login credentials so we can take a closer look? Please provide following information:
Set it as Secure Note
I’m uncomfortable providing admin access.
I feel better doing screen-share.
Google Hangouts works for me.
I have not used the FTP in years, I will have to gather, the credentials and FTP link, etc.
This just happened again in another page!
On existing Classic Custom Header, by switching the heading Level, from H3 to H2
On the first error, I was adding a Classic Text & also editing an existing Classic Text.
This error occurs when saving.
Note that I start replicating the Marine page, and I was able to successfully save changes along the way.
–deleted–
I’m not getting much response to the previous post.
NOTE: After updating to Pro 1.2.1, the problem persists.
Additionally, I have restored to earliest versions known to work, and the problem persists.
I have created a duplicate of this page and is ready, I’m just not sure if there is potential issues if I delete the existing broken page, and publish the new one using identical Permalink, Slug.
By the way, using the same Permalink, Slug is important.
I’m sorry you’re still having issues. Without at least being able to login to see what’s going on, regretfully there isn’t much more I can assist with aside from some general pointers:
I completely replace a page and problem disappeared only from that particular page.
However, we are seeing this in other pages.
Apparently there is another person that fixed this same problem by updating to PHP 5, how do I update.
How do I enable WP_DEBUG?
ALEXANDER! You, as a support member, should be more knowledgeable to help your clients. I wasted days for something that was so simple to fix.
I called Godaddy support, and they show me were to update the PHP Programing Language.
I was running PHP 5.4, my only option was to update to PHP 5.6.
This apparently fixed the issue.
Glad to hear you got it worked out. If we had gotten the WP_DEBUG working, it would have revealed the error creating that issue. X, Pro, and Cornerstone are fully PHP 5.4 compatible, so that’s not something we would normally check. Perhaps you updated something else around the same time.
Hello, can you please help to remove our URL from this post, as these threads are not something we need our clients to find in the search result when looking for us.
I became aware of this issue, and recently I make sure to delete links before these threads close.
–deleted–