Thread

When it comes to setting the value of a title in the <title></title> pair, I tend to do the following:

Start my exp:weblog:entries tag at the top of the page, before <title>, so then I can do this:

<title>Amaravati Buddhist Monastery | {title}</title>

This is specifically for single pages where the url_title is in the url.

Or you can use Low’s EE Title Plugin

I noticed that there is a similar line of code in the template for the <meta/> tag:

<meta name=“description” content=“Resident Community of {exp:weblog:entries weblog={community_info_weblog}} {title}{/exp:weblog:entries} at Amaravati Buddhist Monastery, a monastery in the Thai Forest tradition of Theravadan Buddhism.”>

how would you rewrite this piece of the template?

thanks

The same way. You’d have the exp:weblog:entries tag before the start of the meta tag stuff. Or there is a third party addon by Leevi Graham for specifying meta tags. But that would be over kill.

Hi
I have tried what you suggested about the <title> and <meta> tags. File attached below with changes highlighted.

The result still looks wrong.

... if you look at the page source (also attached), you’ll see that every entry in the 1st weblog (community_bio) has been output, instead of EE picking up the community_info weblog.

I can’t think of how to fix this template.. why is it not picking up the data in the correct weblog? I’ve checked in the database and can confirm that the community_info weblog does exist with the data from the production environment.

attaching hte page source after the changes have been made to the <title> and <meta> tags

In your weblog preferences, you can turn off trackback auto-discovery which should take care of the extra stuff in your title tag. 

-greg

thanks… will try your suggestion..
is this the preference you are talking about?

I just don’t understand why EE won’t display the entry (title) of one weblog and instead repeats the titles of a different weblog.

Yes, that’s the setting Greg was referring to.

Your sample for the title and meta tags is way off.

The example I was giving was for a *single* entry entry page, not a multiple entry page. You’d need a limit=“1” in there or call out the content using a url_title in segment_3.

Does that help?

I have tried the settings Greg referred to and can confirm that the <rdf..> tags are now missing. That’s helpful, thanks…

But… I am still getting multiple entries displayed from the {community_info} weblog, when it should be returning the single entry/title.

I don’t understand your last comment about limit=“1” in there or call out the content using a url_title in segment_3.

If I attach the template code into this email, could you please re-jig (suggest the correction) to what you are pointing us to do?

thanks

Anywhere you have something like:

{exp:weblog:entries weblog={community_info_weblog} }

you need to ensure you quote the second part of the paramter, ie it should look like:

{exp:weblog:entries weblog="{community_info_weblog}"}

even if a variable has already been assigned in the top of the page?
i.e.

{assign_variable:community_bio_weblog="community_bio"}
{assign_variable:community_info_weblog="community_info"}

and later…

{exp:weblog:entries weblog={community_info_weblog}}
<meta name="description" content="Resident Community of  {title} at Amaravati Buddhist Monastery, a monastery in the Thai Forest tradition of Theravadan Buddhism.">
{/exp:weblog:entries}

if this works, it means we have to update every template after doing the upgrade. We were under the impression that the upgrade was quite a seamless process and the latest release is backward compliant.

Yes.

The quotations around parameters have always been required.  As you can see, it’s documented that way as well, and also in the docs on assigned variables.

It’s been this way for as long as I’ve been using EE, parameters have always needed the quotation marks around them.

Hi
thanks - this has worked on the page I tried… its a step forward. So this means that we have to edit all our templates at some point - before/after upgrade as v1.6.8 doesn’t output the weblog entries without the double quotes.

Ta

Yes, that would be correct. As Lisa said, though, this has most likely nothing got to do with the upgrade, it’s always been that way. Let us know when you’ve had the chance to do this and are ready to revisit the issue.