Head Tag Item Issue...

[Dan - Glendale Designs]

Might want to put a note up about the Miva Merchant 5.5 update changing the variable for the head tag item on existing page templates. I am getting killed with "what did you do to my site" support tickets here.

[Rick Wilson]

Re: Head Tag Item Issue...

I'll put it up. We're also pulling down the stream today in about 30 mins until tomorrow (to get some breathing room).

[chmatt]

Re: Head Tag Item Issue...

Thank you!

[Dan - Glendale Designs]

Re: Head Tag Item Issue...

Excellent, thanks. I am also wondering, does the update check to see if the page template has been previously updated or not? I just had a client who updated their store and it moved all existing page templates to production 5, breaking the store.

[Rick Wilson]

Re: Head Tag Item Issue...

I am also wondering, does the update check to see if the page template has been previously updated or not? I just had a client who updated their store and it moved all existing page templates to production 5, breaking the store.

There's some confusion internally by what you mean.

When we update the software we do a search and replace when we change something. For example we search for the HTML tag and then replace it with the new Component for Doctype. Therefore every page was changed.

[Dan - Glendale Designs]

Re: Head Tag Item Issue...

Sorry, I did not explain that very well. So to resolve this issue, the update needs to find:

<mvt:item name="head" />

and change it to:

<mvt:item name="head" param="head_tag" />

Then we will just need to make the same change to any module driven page templates for our clients.

[wcw]

Re: Head Tag Item Issue...

Sorry, I did not explain that very well. So to resolve this issue, the update needs to find:

<mvt:item name="head" />

and change it to:

<mvt:item name="head" param="head_tag" />

Then we will just need to make the same change to any module driven page templates for our clients.

That is not correct. If the module driven page template created a page that is listed in the pages list, then the replacements for <mvt:item name="html_profile" /> and <mvt:item name="head" param="head_tag" /> were automatically done by 5.5. If however, the page is simply a template in a module like my Category Manager or Sebenza's Category and Product modules, then those pages are not listed in the pages list. Hence, they need the edit made.

[Dan - Glendale Designs]

Re: Head Tag Item Issue...

That is not correct. If the module driven page template created a page that is listed in the pages list, then the replacements for <mvt:item name="html_profile" /> and <mvt:item name="head" param="head_tag" /> were automatically done by 5.5. If however, the page is simply a template in a module like my Category Manager or Sebenza's Category and Product modules, then those pages are not listed in the pages list. Hence, they need the edit made.

Correct, the change would need to be made on templates such as the ones in your Category Manager or Sebenza's Category and Product Template Managers. That is what I meant by my last line there. However, I just had store where none of the head tag items were changed on the standard page templates by the update and I had to go in an do it manually. Are others not having this issue? Is the update making the appropriate changes? I am just going off of what I have seen so far.

[Dan - Glendale Designs]

Re: Head Tag Item Issue...

I think I may have figured out the issue. The head tag item used on the store in question did not have a space before the closing "/>". If the Miva Merchant 5.5 update is looking for <mvt:item name="head" />, which is technically correct, than it probably did not make the change.