[Gelöst] Legacy content templates can no longer be edited using the legacy interface.
This support ticket is created vor 1 Jahr, 9 Monate. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Heute stehen keine Supporter zur Arbeit im Werkzeugsatz-Forum zur Verfügung. Sie können gern Tickets erstellen, die wir bearbeiten werden, sobald wir online sind. Vielen Dank für Ihr Verständnis.
Thank you for getting in touch.
This sounds like the classic view editor isn't enabled.
If the classic view hasn't been enabled you can enable it by going to Toolset -> Settings and scrolling to Editing Experience. From there I recommend that you select " Show both the legacy and Blocks interface and let me choose which to use for each item I build".
From there you should see the editor preference for the content template appear. You can set your preference here.
I had that set since I am using legacy and current features. It is the first thing I checked. The issue is very odd. Everything is fine if I display the post directory without it being nested on a parent. Once it is on the parent, it no longer displays the post's body. But to make matters worse, it is not all times that drop the body, some still have it.
The last toolset update converted the classic content template to a Block editor implementation. If I attempt to revert it to the legacy editor, it wipes it out.
I found a workaround. I am positive this is a bug. It has to do with the legacy view and the content template. So since the body is not showing on any of the following child posts, only on the first one, I decided to create a custom field to house this content. It works now, but I have to modify all items on the website by moving the body content to the custom post field.
Happy to see that you're able to workaround the issue.
However I would like to see if this is something that is replicable. Can you record a short demonstration video of the issue to see if I can replicate it here locally.
I can, Shane, but this website was developed using Toolset legacy code. I have had to patch as best I could with the new implementations. I will work on making the video since I have a copy of the broken site. Just allow me a bit of time to get to it. Some parts use heavy conditional statements but oddly enough, none that would interfere with displaying the body content of the posts. As I mentioned, in the View loop, the first instance is correct; the following ones drop the body content.
Something else happened to this website. I had a backup, fortunately, but the theme also started behaving erratically, and so being under the impression that something messed up affected Toolset and the theme. I attempted all the usual fixes of reinstalling WordPress, the theme, and troubleshooting the plugins. The backup has the latest version of every component, and it is running correctly. So it must be some database corruption on this particular install.
