Skip to main content

Replacing files in the "Files" area

Legacy stores have a "Files" button in the Yahoo! Store editor. This can be used to upload files to the store, things like pdf files, images, videos, whatever. It used to be that there was a separate "Files" library for the editor and for the published site - just like there is an editor version of your store and a published version. Well, apparently, there were some internal changes recently, and either this is not the case, or there is something with how Yahoo! Store resolves references to the file library.

The issue: if you have a file (say, image.gif) in the file library, and your store has been published, back in the editor if you upload a new version of this existing file with the same name and try to reference it (as /lib/yourstoreid/image.gif, for example), you will see the old, published version, no matter how hard you try. The only solution at this point is to upload the new file and republish the site. After that, you'll see the new version.

Obviously, this makes it pretty hard to test things, especially because we often store JavaScript files or other images in the file library, so now the only way to tweak these files is to either use a different name each time (very tedious!) or to publish your site each time you make a change. Well, I have clients whose store takes over 8 hours to publish, so this latter solution may not be too great in their case. But, it seems we are stuck with this until the next maintenance release.

Comments

This issue has been fixed.

Popular posts from this blog

CPR for a Yahoo Store on Google's Supplemental Index

Recently a client of mine came to me and said that most of his store pages disappeared from Google, and he did not do anything to make this happen. I was a bit skeptical, so I went to Google, did a search on his store, and sure enough, there were only two pages indexed, his home page and his site map (ind.html) page. The rest were in the supplemental results, which means that Google thought the rest of the pages were not much different than these two pages. When I looked at the supplemental results, the little excerpts under each link were exactly the same, and I also noticed that what Google showed under each result was actually text from the ALT tags of the header image. I looked at some of these pages in my client's store, and they were actually different. This was a bit puzzling, but then I thought perhaps Google saw that the header and left navigation was the same throughout the site (which is pretty normal), but that the text that made each page different was too far down ins

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

Smaller is Better

You often hear the phrase "bigger is better". Sometimes it's true but not when it comes to JavaScript or CSS code in your Yahoo! Store pages. If you include JavaScript code or CSS either as linked files (the preferred method) or embedded inside your pages (obviously not preferred), making these files as small as possible should be your goal. Why? This is no rocket science: smaller files mean faster page loads = happy customers. Ok, so what bloats JavaScript code? In general, white space (tabs, carriage returns, non-used spaces), comments, and the actual code, such as variable and function names. You have control over all of these, however, if you don't use white spaces, carriage returns or comments, it will be immensely difficult to understand and modify your code. And not just for others, you too. There are many commercial JavaScript compression tools around, but I've been using this handy and free utility: http://www.andrewkesper.com/jscrush/ This little utilit