Title And Dynamic Content - Problem With Title Browser - Question | JoomShaper

Title And Dynamic Content - Problem With Title Browser

S-D CONSULTING

S-D CONSULTING

SP Page Builder 1 week ago

Good morning, I always compliment myself when I find products like Page Builder, which are so well-built.

It's understandable that bugs can exist, or at least I think so.

I created a website for an international conference, with speakers.

I managed to create linked collections that allow me to correlate topics, speakers, multiple topics, and much more.

I obviously used dynamic pages, including slugs.

I discovered, I think, a small bug. From an SEO perspective, especially regarding the use of the browser title, it's advisable to never use the title field in collections, unless you specifically want to use it for a field that is then the page title. I encountered the problem with /speaker/:slug.

I created a collection for the speakers (which was then linked to a Topic collection, divided into lectures and workshops). I didn't understand why the title in the browser, when I opened the page dedicated to a speaker, was composed of "Dr. - title of website," where "title of website" is the Site Name in Joomla Global configuration.

I didn't understand why; I would have preferred the speaker's name instead. Browsing the settings, I found that the SEO page offered the dynamics for composing the OpenGraph, and I discovered this next to Open Graph Title:

Available variables: {{Title}}{{Alias}}{{Location}}{{Status}}{{Type}}{{Price}}{{Overview}} (Here I'm using Revstat as an example)

I realized that the system retrieves the "title" by default, and if there's a field called "title" (in my case, Title refers to the speaker's specialty, where they're all doctors), it's found in the browser title.

I had to change the name of that field, so the title remained generically "speaker." It would be helpful at this point to be able to modify the browser title with these dynamic fields, allowing you to decide how to compose it.

Congratulations on the Page Builder product, especially the Dynamic Content section.

0
10 Answers
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 6 days ago #212473

Hello,

Thanks for reaching out to us. Could you please share temporary administrator access to your Joomla backend? You can provide the credentials securely in the hidden content section. Also, please take a full backup of your site before we make any changes.

Once I have access, I’ll investigate further and see what’s causing the issue. Let me know once you’ve shared the details!

Best regards,

0
S-D CONSULTING
S-D CONSULTING
Accepted Answer
6 days ago #212490

Hi, if you need it, I can show you a demo installation of yours that I often use in the members' area to understand how you structure your websites.

But you can do it too; just create a collection and use "Title" as the name of a custom field. Create a slug, and you'll see that if there are no other collections, it takes the first title it finds on the page and writes it to the browser title.

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 6 days ago #212504

Hello,

there is no issues like your mentioned, I have tested it on 3 different browsers.

Screenshots:

  1. Dynamic Content Details page: https://prnt.sc/vhcu78GXO9Ub
  2. https://prnt.sc/uFTWUNAJLq_7

Thanks

0
S-D CONSULTING
S-D CONSULTING
Accepted Answer
6 days ago #212528

Hi, I'm sorry you didn't understand what I was describing. In your screenshots, you show me the Opengraph and meta description; I didn't mention that.

I discovered this, which I believe to be a bug, and it happens when you use the "title" field in a page/:slug.

The system doesn't know how to behave; it writes the field it finds as "title" in the title browser.

As I explained, when I figured out the problem, I simply replaced the name of that custom field with a unique name; otherwise, it mistakes title for title browser.

It's not my problem; I encountered the problem in both Joomla 5 (with all components updated) and Joomla 6.

Unfortunately, as far as SEO is concerned, there's no field that allows you to decide how to compose the title browser.

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 6 days ago #212531

From my end, I’m still seeing an issue. Please check the screenshots:

  1. https://prnt.sc/UHj0qU4D7MGL
  2. https://prnt.sc/9gaFfSqMX_Oq
  3. https://prnt.sc/J047DZKbxlxK
  4. https://prnt.sc/sIiFUhr_PBUg

If I keep the Title field name the same as the Collection name, then on the details page the browser title shows the label instead of the value. However, the site name does not appear in the title in this case.

Could you please review this and confirm whether my issues reproduce to test steps are correct?

Thanks.

0
S-D CONSULTING
S-D CONSULTING
Accepted Answer
6 days ago #212536

I'm sorry, but I don't know how else to explain the bug. Show me the Opengraph.

I'll try to explain better because it's definitely a bug.

I create a collection and call it "Speakers."

The first field is called "Name," where I put the speaker's first and last name. In the second field, I put an image (photo of the speaker). I add other fields that I might need, and finally, I add a field that defines the specialization, and I call it "Title" (it's used to define Dr., Prof., Moderators, etc.).

I noticed this bug because I had left the field named "Title."

When I opened the Speaker page (with the collection), I linked the "name" field and the photo to speakers/:slug.

I simply structured the slug page and saved it.

When I opened the individual speaker's detail page, the browser displayed the following:

Dr. - site name

"Dr." was automatically taken from the field I had left called "title."

Is this a more understandable explanation of the problem as I described it? Because in the SEO settings, I can't tell you which field to use to populate the "browser title" (meta title).

Try that and you'll see the problem.

It would have made sense for me to tell the system to use the "name" field to populate the title before the sitename.

When I figured out the problem, I just had to replace the field name with "specialization", at which point the browser title became generically "speaker" which originated from the previous "collection" page

0
S-D CONSULTING
S-D CONSULTING
Accepted Answer
6 days ago #212539

I created an example of the REVSTAT installation by running a simulation.

I created the SPONSOR collection.

As you can see from the screenshots, I inserted four fields, and lastly, I wrote a text field generically called title. I then created the sponsors/:slug detail page, and as you can see, the field generically called "title" automatically becomes the browser title.

https://app.screencast.com/42PinZG8Sc4ei

https://app.screencast.com/NyLdYiemnrORp

https://app.screencast.com/kRjUtLkIQC93E

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 5 days ago #212646

Based on your screenshot, this isn’t a bug. When you visit a dynamic content details page, the system checks whether the item has a title. If it does, that title is used as the page title. If no title is found, the page title is taken from the assigned menu item instead.

When you create a collection, we provide default fields such as title and alias. The alias is used for the URL, while the page name is displayed using the value from the title field.

Thanks!

0
S-D CONSULTING
S-D CONSULTING
Accepted Answer
5 days ago #212654

Forgive me, but I disagree with the choice. If you don't call it a bug, I think it is.

But just so you know: you shouldn't use the name "title" for a custom field, otherwise the system automatically assumes that.

In my case, if I want to use a speaker's name in the page title, I'm forced to keep the name "title" for the "name and surname" field.

You'll understand that this is limiting. It doesn't allow me to manage the page title separately from the custom field names.

I suggest adding this feature, because from an SEO perspective it is one of the most important elements.

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 5 days ago #212667

Thanks for your time and explanations.

I’ve already marked this as a bug and informed our development team for further review.

Thanks.

0