- Loopers not displaying content
- Pages not editable getting following error
@dlukefinch, thanks for writing in. After taking a look at your site, there appear to be a lot of things going on that I’m not sure how they have occurred. For example, take your “Quick Access” page in the backend. When I take a look at your Document Settings in our dev tools, I see the following:
I’m not sure how you got "publich" in as the "general_post_status" of this page, but that could be one issues going on. In fact, I am seeing that the publish status happening on a few different pages.
Additionally, if I seemingly go to any page on the frontend of your site and simply view the original page source (not DevTools), I can see that your pages do not have any type of closing </html> tag. The markup seems to be ceasing at a certain point. I think this is another issue that could be contributing to some of the problems you’ve reported in this cycle. You will need to turn on WP_DEBUG in your wp-config.php file for us to see what might be happening here at this point.
Thanks.
This is somewhat concerning 
I’d ignore that quick access page as its not in use and I have now deleted it (including all other pages that I don’t intend to use).
I have enabled WP_DEBUG and errors are displaying at /wp-content/debug.log
Thanks for your help so far
Hey thanks so much for testing the Beta. I’ve tested your site and I’ve confirmed that something is wrong with your child theme. Going back to original Pro solved the issue. This could be as simple as not closing out the </html> tags. Or some issue before that causing the wordpress “shutdown” action to occur. I already checked your plugins and that was not the cause. Let me know if you need some help or insights. I will probably need SFTP access to see your child theme changes.
Hello @charlie
I’m not entirely sure where I need to add those tags?
Some help would be very much appreciated. I’ve included FTP details in the secure note.
Howdy thanks for helping us test. I believe in your footer.php you will need to change tco_footer > cs_footer . We are discussing a strategy to prevent this happening on release.
Okie dokie. I’ve done that. Is that all?
It looks like your site is all good now in the editor. Thanks for testing! Let us know if you encounter any other issues.
1 Like
Yes, looks like the site is working as expected now. I have noticed a few issues but I think you’re aware of them already. I may start a new thread to flag it up anyway just in case.
1 Like
Sounds good!