Low Reorder - Custom Statuses
There doesn't seem to be a way to display custom statuses in the low_reorder:entries tag. I've selected the status I want to display, and the entries show up to be reordered in the admin panel, but when I loop over them in the code they do not show up. Is it possible for low reorder to display custom statuses?
What I need:
{exp:channel:entries channel="projects" status="new|open"}
{title}
{/exp:channel:entries}
Example:
{exp:low_reorder:entries set="1"}
{title}
{/exp:low_reorder:entries}
Thank you for your help,
Jay
Replies
JayCasteel 24 May 2012 21:53
Okay, this is resolved. Apparently you can't add a custom status after the set is already created. I created a new set and included the custom status from the get go and it works perfectly.
Maybe this should be noted somewhere or looked into as a bug.
Thanks,
J
Low 25 May 2012 07:46
Hi Jay,
You weren't able to change the status-selection of a Set after it was created? That should not happen, no. Can you confirm that is what happened in your case?
aarmitage 13 Dec 2012 14:10
I've just had this problem and had to recreate the order set to get this to work. We added new status, and the original order set didn't recognise it.
paul.bellamy 11 Oct 2018 12:25
I'm experiencing this issue now (6 years later? can that be right?) - I created a set, forgot to add a custom status, then went back to add that status as well as 'open' but I can still only see the open entries in the list. I saved & cleared cache but still only open entries can be seen. If I re-create the set I'll lose all of the work that's gone into it...
Low 11 Oct 2018 12:38
The Low Reorder Entries tag extends the native channel:entries tag which has filters set by default, including status="open". This will also filter existing entries in a LR set.
You can use force_set_params="yes" to forcibly apply the LR filter params, or add the custom status to the tag, eg status="open|new"
paul.bellamy 11 Oct 2018 12:42
Sorry - my bad; I was talking about the CP, not the front end. I've set up a new set and it's working now. I forgot that this was talking about the tag while I was reading the OPs issue! Still not sure why my set list wouldn't pick up the other status after I updated it though, but to all intents and purposes I've resolved it by starting again with that list.