There are some nodequeues we need exported for product listings views, e.g. "Featured products".
This depends on #373174: Export and import capability for nodequeue .
There are some nodequeues we need exported for product listings views, e.g. "Featured products".
This depends on #373174: Export and import capability for nodequeue .
Comments
Comment #1
Argus commentedDoes this relate to the Broken/missing handler(s) for Relationships in the featured products and featured carousel views?
I would expect a 'featured' field in the product display, so one can choose which product is featured, and which not.
And: how can I fix this manually?
Comment #2
recidive commentedHi, yes, currently the featured product views depends on a nodequeue, but no node queues exist on the feature module.
Your approach would work, but it wouldn't be possible to re-order the products in the view, right?
I'm open to other possibilities, like adding a "Product group" content type with node references to product displays, but this open another bunch of problems we'll need to deal with.
Comment #3
Argus commentedI agree this makes it easier to re-order products. I fixed it by manually adding a nodequeue and use that for the broken links in Views.
Comment #4
recidive commentedTagging.
Comment #5
lowkee commentedsubscribed.
@argus Can you post a step-by-step of what to do to resolve this issue? Or an importable nodequeue? I'm getting this same issue and have no experience with nodequeue
Comment #6
lowkee commentedIt should also be noted, after the nodequeue error happens, the home page goes away completely.
The requested page "/" could not be foundComment #7
recidive commented@lowkee you can create a "featured products" nodequeue, add some nodes to it, and edit the view to make sure the relationship points to your new nodequeue. You may need to enable the nodequeue module first too.
Sorry for the trouble, I'm working on the exportables nodequeue issue, and soon we should be able to export nodequeues as features and fix this problem.