Can't Add to Collection Because "Featured in a Different Store"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 08:51 PM
I was creating a product for my store Driftwood & Dreams, and when uploading, I chose to add the product to the collection "Tropical Blue Monstera Leaves Pattern Products" https://www.zazzle.com/collections/119318463972782522
This collection is linked to this store. And yet when I try and publish the product, it doesn't let me. The collection section displays an error, saying I can't add the product to that collection because the collection is featured in a different store.
What makes this error strange is that, after I publish my product, I can go to the aforementioned collection page, edit the collection, and manually add that product without issue. It's just the adding from the Upload screen that causes the problem.
I have encounted this error with other uploads and other collections, but not all collections. For example, I can add to the collection "Natural Brown Monstera Leaves Pattern Products" without issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 09:34 PM
I get the same error now and then. I only have one store so I'm pretty sure it's just some sort of bug that they haven't traced down yet.
It's been reported here: Add to Collection Not Working on Product Listing P... - Zazzle
and here: Error Message when adding a Collection while Posti... - Zazzle
Zazzle has yet to weigh in but I'm assuming it's on their bug list somewhere - just hasn't risen to the top yet.
Cat @ ZB Designs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2023 07:10 PM
@Catah I didn't see those other threads, I think because I just searched for the wording in the error, and since your post had the wording in the photo it wasn't searchable. Thanks for linking! It's not great that this error is going untreated as yet, but at least we know it isn't a user error problem *shrug*

