Skip Navigation

[Resolved] Post Title / Heading, Toolset vs Word Press

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

Problem:

The customer asked what is the difference between storing a post title and showing the title using the heading block.

Solution:

Guided that post title is saved in the database as a name of the post, whereas the heading block is a tool to show any heading, including the post title.

Relevant Documentation:

n/a

This support ticket is created 3 years, 2 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/Karachi (GMT+05:00)

Author
Posts
#2250511

Jay

Tell us what you are trying to do?
I wonder what is the difference of using a Toolset heading or the built in WP title of a post?
When writing a post on the back end Word Press doesn't seem to like it if I don't use their built in title. Is there a clearer description of how to best use the title blocks and the difference if I use a toolset custom field or the default WP field. Is search or archives affected?

On the back end I can't save a post unless I fill the Word Press Title, even though I have it disabled. Should I just fill it with the same info I put in my custom title field.

Is there any documentation that you are following?
Dario briefly touches on the subject here. Minute01:00 and 06:31
https://toolset.com/lesson-placement/lesson-placements-1621067-1621091/

What is the link to your site?
hidden link

#2250833

Hi,

Thank you for contacting us and I'd be happy to assist.

1. WordPress Title:

It is something that is related to the database logic, that is how information/data is saved for each post/page.

In the context of WordPress posts and pages, the "title" has the same importance as the "Names" have in human society. It helps in identifying in a meaningful way, what a particular post or page is about and what content the reader/visitor can expect from it.

It won't be wrong to think that the "title" is the most prominent and important piece of information ( after the content itself ) that is stored for a post/page.

The other secondary elements like taxonomies and custom fields come in useful when we need to store some additional information items with the post/pages, but, they don't really are a substitute for a "title".

If the use of "title" is skipped in favor of custom field(s) then the search will be affected because WordPress default search only looks through titles and content/body, but not custom fields.

Note: To extend the default search to also cover custom fields, you'll need to include the third-party plugin "Relevanssi":
https://toolset.com/course-lesson/searching-texts-in-custom-fields-with-toolset-and-relevanssi/

2. Toolset Heading:

The Toolset "Heading" block is something that is related to the presentation layer only.

From the previous point, we established that the we store the most important and defining information in the "title" field. When we need to show that title in a heading format in a template for readers/visitors, we can choose to use the Toolset "Heading" block. This means that the "Heading" block is a tool that can be used to show the WordPress title saved for the current post/page.

Alternatively, if you don't want to show the title as a heading, you can also use the "Single Field" block instead, to show that post/page title as a simple text.

And it is also important to note that the use of the Toolset "Heading" block is not limited to showing the post/page title. It can also be used to show a static text as a heading that is not coming from any dynamic/database value or we can even link it to a different dynamic value, for example, a custom field.

I hope this explanation helps and please let me know if you need any further assistance around this.

regards,
Waqar

#2250877

Jay

My issue is resolved now. Thank you Waqar! It's crystal clear now.