Price and model in browser header

I turned off the meta support for product price and model but it still shows in the browser meta tag.

Is there something else that I've missed? I've scoured the settings, but cannot find it anywhere other then the one place :lamo:

There is a global setting in the Configuration ... Product Info ... for the model and price in the meta tag title ...

Then, there is the custom setting on the meta tags when set on a per Product basis ...

The custom setting rules per Product ... so if that is on, you need to turn it off ...

Gary bows again :clap: with many many thanks... :thumbsup:

Ajeh, can I ask another tibit of an issue. In my cats I used , <br/> to create a wrap of the text on the tabs.

How can I get it to not show this in the meta tag ?

Have you an URL to one of these Products?

Technically the meta tags should clean that out for you ...

Poopers ... cleans the Products Name and not the Category Name ...

Let me fool a minute with the code ... :oops:

Yes of course... looky here

As you will see from the tabs menu, any one of them all use ,<br/>

I'm also futzing around with SEO(ultimate) ultimate, that it is, ultimate headache so far...lol

Okay ... we call this an unexpected feature ... :smartass:

Some call it a bug ... :cry:

To fix this, edit the file:
/includes/modules/meta_tags.php

Find all of the references to:

PHP Code:

---

$keywords_metatags->fields['categories_name'] 


---

And replace with:

PHP Code:

---

zen_clean_html($keywords_metatags->fields['categories_name']) 


---

And all references to:

PHP Code:

---

$category_metatags->fields['categories_name'] 


---

And replace with:

PHP Code:

---

zen_clean_html($category_metatags->fields['categories_name']) 


---

There are quite a few of them ...

This will be included in the next release ...

Now that makes me the lucky one...lol

:smartass: fixed :thumbsup:

Thanks once again

You are most welcome ... thanks for testing this fix out for us ... :cool:

:thumbsup: :thumbsup: :thumbsup: NP, glad it worked.

Question, does this also affect that of using say & instead of having to use &amp; as well.

As it stands, in order to validate, I needed to add &amp; when using a description of a cat such as Body & Hands when creating the cat. Once created, if you go back to the cat to edit it shows as & in the description and if I do not readd the &amp; gain it fails validation.

If main body text uses & and not &amp; , there are no issues, but menus or cat descriptions have so far resulted as such.

I also noted that the fix works fine, but if using the SEO addon, the SEO picks up still the <br/> converting to show as a br rather then a line-break thus the endresult of the SEO for Body &<br/>Hands ends up as bodybrhands.html and the & is shown as funny chars as well. I managed to use the <br/>=>- to fix it which works, but the & is problematic. So I removed the & from the cats.

I've turned off the SEO due to a fact that I found out after install that it was not supporting 1.3.7 and have yet to update it.

These issues of course were present prior to the SEO install, of which the representation of <br/> is fine, just the & issue is still at hand.

Thanks for the help and np, me guinea tester :smartass:

Not sure what to tell you on the SEO stuff ...

I don't use it myself but I understand dreamscape has a new release out on this ... perhaps he can work through this with you ... :smile:

Aside from the SEO, why do we need to us &amp; rather then & ? What I mean if I name a cat as Bay & Barley for example as a cat description and check validation it fails or gets warnings, thus if I use Bay &amp; Barley then it valdiates, but when I come back to edit the cat again, it does not show > Bay &amp; Barley < but rather shows it as > Bay & Barley < and if I save as it shows after edits, it once again fails validation and I need to enter &amp; then save the cat title.

This has nothing to do with the SEO mod as it was like this prior to having done the install.

So, I was wondering if this is all the same sort of bug we caught earlier.

Currently the cleaning is too good ... :cry:

This will be worked on for a future release to avoid these issues ... otherwise Kim will have my head ... :eek:

Dang, I always come up with the good ones. I'm a nit picker, what can
I say :smartass: but still Love ya :P :lamo: