Yahoo! Cross-sell bug

In a recent release, Yahoo! made it possible to show cross-sells right on the product pages. Coupled with their auto-suggest feature (where products are automatically recommended based on past shopping history) this is a great conversion feature. There is, however, a minor bug in the way these on-page cross-sells are implemented. Here is the scoop:

As you may know, you can add the yahoo-generated cross-sells to your item pages by inserting <div id="ys_relatedItems"></div> anywhere in your pages' text or template. The bug occurs - in Internet Explorer only - if this ys_relatedItems div is the last child of its parent. In that case, and again, only in Internet Explorer, no cross-sell items will show up on the page.

In layman's terms, this means that if you have a closing tag after <div id="ys_relatedItems</div>, then this bug will cause your cross-sells not to show. So, for example, if you have a table and inside it the last element is your ys_relatedItems div, then this would trigger the bug.

Yahoo! Engineering is aware of the bug and it will be fixed in the next maintenance release. In the meantime, though, there is a very easy work-around: simply add something after your ys_relatedItems div so that it's not the last child of its parent. An empty div, for example, will do the trick:

<div id="ys_relatedItems"></div><div></div>

Comments

How to create clean and efficient CSS

In a typical workday, I deal with dozens of yahoo stores and very often I have to tweak, fix, or change CSS used by these stores. While some stores have very clean and easy to follow style sheets or CSS definitions, the vast majority of stores I've seen seem to include complete hack jobs, style sheets put together completely haphazardly, or as an afterthought. While working in such a store, the idea came to me to turn my gripes into a post. So the following is my list of dos and don'ts of good CSS or style design. 1. Externalize your style sheets. This means to save your style sheets into one or more css files, and link to them using the <link rel="stylesheet" type="text/css" href="/lib/yourstoreid/yourstyle.css"> notation, or in Editor V3.0, you can use the LINK operator. 2. Combine your style sheets into as few files as possible. Nothing worse than trying to wade through 6, 8, 10 or more different style sheets to find the color of a l...

Adding custom Yahoo Store fields - Catalog Manager vs. Store Editor

In a non-legacy Yahoo Store, there are two ways to add custom fields: through Catalog Manager under "Manage my Tables" and through the Store Editor, under "Types" (the Store Editor's "Types" are essentially the same as Catalog Manager's "Tables".) Whether you add custom fields from Catalog Manager or from the Store Editor does make a difference as each has its advantages as well as disadvantages. Catalog Manager To me the main advantages of using Catalog Manager to add custom fields are: 1) You can add multiple fields quicker 2) You can later change the field's name and even type 3) You can delete the field if you no longer need it. 4) All the fields that are available in Catalog Manager are included in the data.csv file if you download your catalog. 5) All the fields that are available in Catalog Manager are also included in the catalog.xml datafeed file, which is used by the comparison shopping engines, for example. (See the Search ...

What to expect when your redesign goes live

At Y-Times we roll out new designs, redesigns and other major upgrades to Yahoo stores on a fairly regular basis. Some of the main questions our clients ask are how to prepare for a roll-out and what to expect in terms of SEO and conversions when the changes go live? For any functional Yahoo store how well the site ranks and how well it converts are probably the two most important metrics. Since pretty much ANY change you make to any page can potentially alter either or both of these metrics, merchants may understandably feel nervous about far reaching alterations to their sites. However, when those functionality and design changes and additions are done right, there is really very little to fear. First off, what does it mean for a design or redesign to be "done right?" From the technical stand point, search engines look at the underlying structure of your site (the HTML, and increasingly also the CSS and JavaScript code) to try to extract information and meaning from i...

Search This Blog