Hi All,

I’m having a problem where an entry’s status is automatically set to “closed” if it’s edited by a site member.  The default entry status is set to open but when a member of a different group edits the entry the status automatically changes.  Is this a setting somewhere? 

I’m running 1.6.0 Build:  20070918

Thanks in advance for the help.

****UPDATE****
It appears that when I log in as a user that is a member of a custom group the “open” status option does not exist.  Any idea why the option would not show?
**************

Thanks,
Shawn

I’ve encountered the same problem with users in custom groups being unable to open entries. The status menu only shows “Closed.” I’ve had to migrate these users into the SuperAdmin group just so that they can post open entries—naturally, I’d love to get this solved rather than allow all members to be SuperAdmins!!

Hi, guys.

What is happening is that your users aren’t listed as being included in the publish page multi-author list.
“Include user in PUBLISH page multi-author list?”

You can set that variable manually.

EE Docs: My Account

However, I do recommend you upgrading to 1.6.1.

From the change log:

Added Member Group preference to allow all users in the group to appear in the PUBLISH page multi-author list

Modified entry author validation so that the Multi-Author List is only checked when the user is is attempting to change the author.

Sue,

Thank you for the response.  I’ve tried changing the setting as you suggested by that doesn’t seem to work.  See the attached screen shots… 

I’d prefer not upgrade this one site right now unless it’s absolutely necessary.  However, if upgrading is the only way to fix the issue then I will do so.

Thanks again,
Shawn

One other thing to check… that your weblogs all have a status group assigned to them.

Why is it always something so simple?  You rock!

Thanks,
Shawn

I remembered part of the fix, but I didn’t remember until later about checking for the missing status group.

For some reason the status group was not assigned to the weblog. I can only assume that this somehow happened when it was updated to 1.6. All is well now, thanks!

Yikes, ran into that problem too.  Setting a status group to the weblog did fix the problem.

Glad you were able to implement the fix.