As you may know, you can easily put HTML tags in your editor fields, such as the caption field, or the message field on the home page, or even in the head-tags variable, etc. I always encourage my clients to feel free to use some minimal formatting they may want to include in these fields, because doing so is relatively easy and really shouldn't require hiring a professional to do so. I always tell them also, to be careful with the HTML they put in those fields, and DO hire a professional if they find the need to add more complex HTML - for example, beyond just bolding words, or emphasizing phrases, etc. However, I keep coming across stores where merchant-edited HTML nearly bring the store to its knees. Yes, that actually can be done! Why? Because web pages - therefore Yahoo Store pages - are made up of HTML tags, so if you throw a wrench in there, expect things to break.... Adding simple formatting is harmless. You can easily bold words, change the appearance of fonts, etc. It b...

I'm helping a friend getting up and running with her brand new Yahoo Store, and we have a ton of high definition, high res product images. Besides the fact that images that are over 3 or 4,000 pixels tall or wide are really not very practical on screen, they are also way over the maximum parameters allowed by the Yahoo Store editor (parameters are: no more than 2,000 pixels in width or height, no more than 2 million pixels total, and no more than 2MB in size). Luckily, I found a freeware image viewer/batch conversion utility called InFanView . This utility allows you to select a batch of files (or directories) and rename them , resize them, crop them, recolor them, pretty much anything you would ever want to do to product images in bulk. If you find yourself in a situation where you have to manipulate your product images in bulk, you should definitely give InFanView a try. Istvan Siposs Y-Times

I get these questions from time to time about upgrading from legacy store to Merchant Solutions, vs upgrading a V2 template set to V3, so apparently this is still a confusing topic. The two are two completely separate issues/topics. First of all, how can you tell if you have a legacy store? This is pretty easy, when you log into your store manager, it will say "Store" next to your store's name in the upper left corner in the blue band. If you have Merchant Solutions, it will say "Merchant Starter", "Merchant Standard" or "Merchant Professional". Upgrading to Merchant Solutions For the most part, this is only a question of money, because there is a different price structure for legacy store vs. the various Merchant Solutions packages. You can see a comparison of the various Merchant Solutions Plans here: http://smallbusiness.yahoo.com/ecommerce/compare-plans So what do you get with Merchant Solutions that you don't have with...

Catalog Manager (for non-legacy Yahoo Stores) provides a nicer, easier to use interface to update your products. You can sort and page through your items, look for items using simple and advanced searches, or edit or delete multiple items at once, tasks that are not very easily done in the store editor. If you ever work in Catalog Manager, you may also have noticed the "Publish" button there. The inline help says, if you publish your catalog, all the changes will be immediately visible on your site. You may be tempted to use this function particularly if your editor usually takes a long time to publish, however, if your store is an editor-based store, publishing the catalog separately from the editor is not for you. Catalog Manager was originally created to allow access to the product catalog for stores that are built on the web hosting account using "store tags". Today, of the thousands of Yahoo stores very few use store tags (and I don't recommend it eithe...

As indicated in Yahoo Small Business's recent blog post of upcoming features , the long-awaited "incremental publish" feature is being rolled out this month. They are going server by server, so some merchants will see the change sooner then others. What is incremental publish? Incremental publish keeps track of what pages you edited and changed since the last time you published the store. Instead of the single "Publish" button, you will now have two buttons, one that says "Publish All", and the other that says "Publish Changes". "Publish All" does the same as the current "Publish" button, it generates and publishes all pages in the store. "Publish Changes", on the other hand, will only publish the pages that changed. This can be a huge potential time saver especially for large stores whose publish takes hours normally.

Although the Yahoo! Floating Cart is considered pretty much bug free by Yahoo (you can look at the official open issues list here http://help.yahoo.com/l/us/yahoo/smallbusiness/store/floatingcart/floatingcart-09.html ) , there are some pretty "interesting" issues still, so since I keep running into them, I decided to post them here along with the work-arounds. The following issues all occur with multi-add forms only. 1) If you have your quantity set up as anything other than a simple text box (for example a drop-down SELECT box), the floating cart will not take the quantity value. It will take vwquantity as a customer-selected option. The workaround: use a text box instead. Nothing else works currently. 2) If you have a script that checks if the shopper made a selection from a drop-down (basically, any kind of an "onsubmit" handler), the floating cart will still receive the item, even if you cancel the submit event. The workaround: put the event handler on the click...

I get this question often. Or variations of it such as "is it safe to expand my site to 1200px now?" According to W3Scools , as of January of this year, about 13% of all internet users are still on 1024x768, which is a high enough proportion to make me play it safe and set the max width at 980px so that these folks can see the site OK. If you go any higher, these people will have to scroll sideways, which is traditionally a major "no-no" (simply because it's annoying.) However, you should check your own stats to see what percentage of YOUR visitors have that resolution, because your demographic segment may very well be different from the average.