Skip Navigation

[Resolved] Can’t edit template page.

This thread is resolved. Here is a description of the problem and solution.

Problem:

I am trying to edit a template page for a custom content type that was created. When I click the link on the dashboard to get to the edit page, it is either leading to a blank white page, or giving a PHP memory limit fatal error.

Solution:

You can display the post body with a Toolset single field block

Relevant Documentation:

https://toolset.com/block-item/single-field/

This support ticket is created 3 years, 3 months ago. 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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 22 replies, has 3 voices.

Last updated by melodyM 3 years, 3 months ago.

Assisted by: Luo Yang.

Author
Posts
#2274855

According to our support policy, we prefer one ticket one questions:
https://toolset.com/toolset-support-policy/
there are lots of questions in this thread:
https://toolset.com/forums/topic/cant-edit-template-page/#post-2274723

We can handle them one by one, for this issue:
1) Is displaying on the page as :
Attraction Designer<br>Graphic Designer<br>Signage Designer

You can not use HTML code "<br>" as the Separator, but you can use a taxonomy view to display the result as what you want, for example:
1) Create a taxonomy view "Freelance category terms":
hidden link
- Query "Freelancer Categories" terms
- Filter by:
Taxonomy is set by the page where this View is inserted
- In view's loop, display term's title:
[wpv-taxonomy-title]

2) Edit the content template again:
Display above taxonomy view's shortcode:
[wpv-view name="freelance-category-terms"]

And suggest you try with Grid block to format the content template:
https://toolset.com/block-item/grid/

#2274863

Did you do anything with the demo content to make the template work? Much of the theme demo content was gone and I had to reinstall it, but now the template isn't working properly again.

Compare what's present here:

hidden link

with what's showing here:

hidden link

#2274867
#2274869

If you need more assistance for it, in order to setup demo for you, please provide another test site, fill below private message box with login details

#2275275

I almost have it working now. The way you did the taxonomy view works. Thanks for that.

I'm still running into more problems with things not saving. But I'll create a new ticket for that even though it feels like it is still part of the same major issue originally reported here. Things just don't seem to be working as expected at all and I don't think the problem lies with Toolset because all of these things worked fine on the last site I worked on with you.

#2275853

I have tried it in your website by these steps:
1) login into your website
2) Open the content template URL:
hidden link
I get below error message:

HTTP ERROR 500

3) Refresh above URL, I can see the content template and I can save/update the content template without any problem

Are we talking about the same problem?

If it is, the error 500 means there are PHP error in your website, you need to get the latest PHP debug logs from your website
https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/#php-debugging
section "PHP Debugging"

#2276887

I'm thinking the http error 500 that you got and the issue with me having trouble saving is part of the same problem that I'll have to figure out with the debug log.

Consider this ticket resolved, but I may need to start a new one if I see anything further in the debug log leading me to think Toolset is part of the issue.

#2276889

My issue is resolved now. Thank you!