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

Pre-Season Checkup

With the holiday shopping season fast approaching it's a good idea to do a general checkup on your store to be sure it's ready for prime time. Below are a few things you would want to check, along with a few add-ons that are not too major in scope, but which are often neglected and give you an edge over your competition. Can you Search and Order? Every time we do anything major in a store we test two things: whether searching and adding to cart/ordering works. You can have nice, flashy pictures, cool animation effects, a very quick loading site, anything, but if the store search is broken or you can't add to the cart or can't check out then an ecommerce site is worth nothing. Can you Order? Chances are if your checkout was completely broken you'd know about it by now, but it doesn't have to be totally broken in order to scare away potential customers. So go ahead, go to your site and first do a search and make sure it works. Then, add one or more products

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

Auto-update Copyright Year

This is one of those minor, recurring questions I'm always asked (each year): to update the copyright year in sites. Whether this is the "right thing" to do or not I don't know, but here is how you can make it automatic: First, go to the Variables page (these instructions are for Yahoo! Stores), and do a search for the word "copyright" or the year that's currently displayed next to your copyright message. If you can't find it there, chances are you have a custom template and the copyright message might be coming from some place else. In that case, you'll have to track it down, but because custom templates can be set up in any which way, unfortunately you'll be on your own. Assuming you found it, replace the year with this JavaScript code: <script>document.write(new Date().getFullYear())</script> Hit Update and you should be all set!