ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

When Member logged in to backend, publishing content forces status to closed.

February 20, 2012 5:24pm

Subscribe [2]
  • #1 / Feb 20, 2012 5:24pm

    doubleclick

    43 posts

    Hi there, we are having a permissions issue with EE (v2.2.2 - Build: date 20110801). When someone logs in as a “Member” (screenshots of permissions assigned are attached) and goes to Content>Publish>PageName, the page comes up no problem. You can fill it in and hit submit, also no problem. But once you do, the “status” for that entry defaults to “closed” (as opposed to “open” when an SuperAdmin does it). This is the same for editing content. We have tried looking through the permissions options/rights (members/member group/edit group) but cannot figure out what, if anything, we are doing wrong to allow this content edit/publish to facilitate a default status to open like an admin super user can. Any ideas? Is this a known bug? Any thoughts/ideas are welcome. Thanks!
    P2P

  • #2 / Feb 21, 2012 12:04pm

    Design by Front

    106 posts

    Hey there!

    I’ve seen this before, it sounds like the channel doesn’t have a specific Status Group assigned to it. Have a look at your channel at Admin > Channel Administration > Group Assignments.

    Is “Status Groups” set to “none”? If so, that’ll be the issue. Make sure that a status group is assigned which contains an “open” and “closed” status that your Members group has access too.

    Hope this helps 😊
    Chuck

  • #3 / Feb 21, 2012 6:46pm

    Sean C. Smith

    3818 posts

    Hi P2P,

    I believe Chuck’s answer is correct. Could you try that out and then let me know the results. I would also recommend upgrading to 2.4, if possible, as there have been many fixes and improvements since 2.2.2.

    Sean

  • #4 / Feb 21, 2012 9:30pm

    doubleclick

    43 posts

    Chuck, thanks for the tip. This seems to have worked! Question though - why would a Super Admin not have this issue? Was this a known bug Sean?

  • #5 / Feb 22, 2012 8:24am

    Design by Front

    106 posts

    No worries 😊

    I suspect that super admins can always post as “open” because they are free from the constraints of permissions, even - as in this case - if no status group is assigned to a channel.

    It does however feel like a bug to me, there should at least be a warning when setting up a channel that a status group hasn’t been assigned (after all, what use is there in having no status group?). It’s caught me out a few times and for a first time victim (like you 😉) it’s in no way obvious how to fix the problem

  • #6 / Feb 22, 2012 9:59am

    doubleclick

    43 posts

    Completely agree….Sean, can you confirm the logic of this status/permissions issue and whether or not this is/was a bug that perhaps has been resolved in your recommended upgrade above? Also, if this is out of the box behaviour and has not to date been fixed, any recommended workarounds here (hacks/add-ons from 3rd parties) to instigate such a warning message as EE is built? Thanks for your help!

  • #7 / Feb 24, 2012 1:43pm

    Robin Sowell

    13255 posts

    Morning folks!  Glad it looks like you got this one figured out.  It’s actually intended behavior- and ‘Design by Front’ is correct in his surmise about superadmins.  It’s documented in the docs on statuses:

    If you do not assign a status group to a channel, only Super Admins will be able to post entries with an ‘open’ status.

    That said- you are not the first to run into an issue with it.  So while it’s not a bug, I’ll be sure to drop a note about it with our UI guy.  James is taking a hard look at how we can improve the user experience.

    And if you do run into more issues/questions, just let us know.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases