Hello,

I think I just found a small bug in EE (version 1.4.2) with entry status workflow

If you do this
<http://expressionengine.com/knowledge_base/article/how_do_i_set_up_an_entry_status_workflow/>

I think that there is a bug occuring

To trigger it:

a. We created a status group containing Open / Close / To be reviewed
b. Created a user group called submitters.
c. Submitters only have access to the “to be reviewed” status
d. Created status group had be assigned to a weblog
e. Created 2 accounts (admin / submitter)
f. Submitter, member of submitters group, creates a post with status to be reviewed (the only status available to him)
g. Login with an admin account (publishing rights) > change the status to “open” > it’s online
h. With admin account, set it back to “to be published” > not online anymore
i. With admin account, change the status back to “published” > it doesn’t show up online and it’s now impossible to make that post visible in the front office although it is still in the database. We changed status using only the EDIT form.

Can someone replicate the bug or is this related to my EE settings ???

In step (a) you describe three statuses, the two default and one custom.  Steps (h) and (i) appear to be describing two additional statuses.  Are these different statuses, or are you just referring to Open and Closed by different terminology?  As for the front end display, only “Open” status are displayed by weblog entries tags by default.  You must use the status parameter to include other statuses.

Hello there,

Thanks for the quick reaction. You guys never sleep ;o). After further testing, I think we were too quick to post about this bug.

<blush>I think the problem was caused by wrong server localization parameters</blush> which caused the date to be set in the future when updating a post (didin’t have the show future entries parameter). Looks ok now.

My developper is away right now, but we will come back to you if anything abnormal happens again.

PS: thanks for this great tool !