Skip to main content

Reserved page in Yahoo! Store

A client of mine asked me to figure out why her order status page - which contained only a simple HTML form - didn't work on her published site. It was a strange phenomenon, the page she created worked perfectly fine in the editor, but on the published site, all it showed was the word OK. This was really strange, as I couldn't see anything wrong with the HTML itself.

Then, I thought, since the form used an outside service to return order status, maybe that service did something to the page. So I took the form out (leaving that order status page basically blank, with only the store header, navigation, and footer on it) and republished. Same thing! Only OK on the published site... Then I looked at the source of that page, and in the source there was nothing else except for OK. Now that was really strange, because in Yahoo! Store you cannot even create a page that does not at least have a regular web page layout like this:

<html>
<head>
<title>No Name>/title>
</head>
<body>
</body>
</html>

Since this page had none of that, I had a thought and plugged in the same URL but within another Yahoo! Store, my own: http://www.ytimes.info/status.html

Voila! Same result, that page only showed OK - but I didn't even have a status.html page... So I went back to my client's site, recreated the order status page as order-status.html, published, and all of a sudden everything worked great.

Out of curiosity, I tried a few other Yahoo! Stores to see if they also had a status.html page, and as I expected, they all did - and with the same OK and nothing else on it. So I contacted Yahoo! and confirmed:

status.html is a reserved page in every Yahoo! Store used for server monitoring.

So my first conclusion was: don't create a page whose ID (url) is status, it won't work on your published site.

But better yet, you can turn this into a useful feature: create a status.html page in your store, but use it for internal communication for your company. You can put notes there for your staff, instructions, etc. Whatever you put there will only be visible in the editor, not on the published site.

Comments

Popular posts from this blog

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...