I have a Request Error on my account page, or store backend, or collections pages

[Scott]

There's a tricky little bug that's causing some issues. There's a few separate bug reports in the tech forum about this same issue and it's making it difficult for me to collect data for our engineers to review. So I'm going to create one discussion here for us to use moving forward to ensure we're not missing anyone's comments.

What we know is this:

• When you log into your account and visit a page then you'll see a Request Error. We know there's been issues on a few pages so far, including your member page, store backend (Products tab), collections list page (Collection tab), and collection pages themselves.
• This seems to clear up on its own after a bit of time (it could be one hour, or 24 hours). I don't know if every issue is clearing up on its own, however. This much is just an observation that I've made based on reading posts and investigating reports.

Apologies for the issues that we're experiencing here. We hope to have this resolved very soon.

[Scott]

Also, wanted to note that this could cause some strange issues when you're viewing your collection list page (this is the Collection tab in your member page or store page). You'll be viewing your listing of collections, and when you try to go to the next page nothing will happen. If you go to the next page again then it'll work. What's happening is that we're not loading a page that would result in a Request Error. So, unfortunately, one page of your collections will not be available while the issue is impacting the page. If you try to view the page by updating the page parameter in the URL you will get a Request Error page.

[Steve-Garner]

Yes I getting a request error at this link https://www.zazzle.com/mbr/238358451889520737. I also reported in the report a bug section of the postings with further details.

[Steve-Garner]

The Request error has now been corrected and all is back to Normal Optimization. Thanks again to whatever support I was given.

[MillionAyres]

Thanks for addressing this, Scott! I'm happy to help provide any feedback or information that I can on the issue if it helps. 

[MillionAyres]

@Scott - If it helps at all...

I just checked and I'm still getting the error when I try to access the Collections page by clicking on "View all collections" from my store page. However, if I click on individual collections, they will open. 
This is the URL I'm getting an error when I try to access it: https://www.zazzle.com/store/madebymillionayres/collections

I am also able to access the "Likes" tab again, which was giving an error yesterday.

Another thing I noticed, which may be user error on my part, is that when I'm logged out of my account, only 1 of the collections is showing on my store's collection page. There are 3 collections total and I see them all when logged in.

Thanks for your help!

[mairinstudio]

Hi Scott, I receive a Request Error page when trying to reach my Mairin Studio store https://www.zazzle.com/store/artofmairin  . When I open my member profile page, I can see only two from my three stores. The store Mairin Studio is not visible. The same Request Error page loading when I am trying to access to "My Stores" page via dropdown menu of my account https://www.zazzle.com/mbr/238559159459885733/stores 

[mairinstudio]

It works now. Thank you

[nmani1985]

Trying to access my store https://www.zazzle.com/store/NiranjanaManiArt still results in a request error. However, searching for the store on the search bar brings up my products. 

[Jadendreamer13]

Today, I’m getting a Request Error when I publish a new product. I was having to log out of my account to clear the error, but now even that isn’t working. At this moment I can’t access my account or store.

[Scott]

We have a fix for your issue. When we update the website tonight it should be included. I'll update this thread when that happens.

[MarinaM]

This happened to me also. I thought I had mistakenly deleted my store. But all the products are still there. I have the store showing in my profile but when I click on the link I get the Request Error. I also have no way of even opening another store on my profile. There is no button there. I am new to Zazzle and have put so much work into my new store. Absolutely gutted that is has disappeared. It has been gone  for about 6 hours so far: https://www.zazzle.co.uk/store/celestecelebrations

[Jadendreamer13]

I can see and access my store on my iPhone, but not on my laptop.

[siyam]

Hi today I have posted a product and now I can't access to my store when I click on my store this shows

"up An unexpected error occurred while processing your request. Please try again later. If you got to this page after manually entering the URL into the Address field of your browser, please make sure that it is spelled correctly. "

I can see my product when i go to my account (not store setting) and click on "view your products" then i can see my products 

[Scott]

We updated the site with some additional fixes that should help with this.

If you continue to experience this issue in the future please let us know.

[magnolion]

Hi Scott,

II have a similar problem on the front page, in the shop view, a 404 error page appears on the product page. Here: https://www.zazzle.co.uk/store/magnolion/products

[Scott]

This is expected when the store has no products in it.

To be more specific, this happens when there are no publicly-visible products in the store. So you may have opened a new store and then published some new products, but those products will need to run through a process called "indexing" before they're visible publicly. Right now the indexer is a little bit behind schedule, but it should be caught up in the next day or two. Once that happens your store should be working as expected.

[magnolion]

OK, thank you, there are currently 61 products uploaded and also a collection. Then we hope everything will be fine within 1-2 days.

[AqquaRelli]

Hi, it won't let me check out and says request error: 

[Scott]

This issue has been resolved. Very sorry about the inconvenience.

I'm closing this discussion to new replies since it's about a bug that impacted the site last year.