Hi,

I've installed this really promising module on a fresh D6 install, but cannot get a way to change (ie 'approve') created contents. Furthermore, the "admin/user/permissions" page only shows "content moderation view moderation history" for enabled content type (no "change state" lines) - thus this should not be an issue as I'm testing thing as admin user for now.

I must be missing some point... any idea ?

Comments

eugenmayer’s picture

Did you activate content_modration for any content type?

cyxair’s picture

"Moderate revisions" is checked as well as "Create new revision" and "published" for tested content types. Should be enough to activate content_moderation, right ?

Additionally, I get an "access denied" when using the "eye button" in the content_moderation block (path is like "node/4/revisions/6/view").

[EDIT] the "access denied" occurs only on initial node creation (I can access to revision when I have more than one version of the node).

eugenmayer’s picture

When you activate the checkbox, this should be fine. Then you should have new permissions for all the default state changes.

cyxair’s picture

The checkbox is checked, the block is showing pending revisions on the nodes.
It seems that all the "change states" stuff is missing, although states and transitions tables exists in the database...

span’s picture

I've run into this problem after making new states and each state has a permission connected to a content type that it is activated for. Make sure you have your permissions set straight, I didn't.

cyxair’s picture

Thanks for your replies, but I precisely don't have any "change state" lines on the permission page...
Plus, logged in as the website admin user, I guess I shouldn't be impacted by permission settings.
Is there any particular core/contributed modules that should be activated for content_moderation to work ?

eugenmayer’s picture

Actually it does seem that you have setup everything right.

I guess you might need to install devel and use a dsm at the hook_perm to see, whether its called at all. If yes, check the node-type which are used to generate the matrix for the permissions.

Dont hasitate, we get this done :)

eugenmayer’s picture

Category: support » bug
Status: Active » Fixed

Well this actually was a bug in the installation script. To get rid of it, remove AND uninstall content_moderation and install the new version again (for now github http://github.com/EugenMayer/content_moderation )

Thanks for the report

Will be released in 1.5

eugenmayer’s picture

Title: Can't see the 'change state" button » No permissions for states visible / no states changeable / Can't see the 'change state" button
loophole080’s picture

just to confirm this worked great - thanks, lovely little module, very smooth functionality!

cyxair’s picture

Works fine with the last github version, thanks for the update !

eugenmayer’s picture

Thanks for testing guys

twistedindustries’s picture

Hello, I have went to GitHub and grabbed the patched version but now I just get notices from drupal saying the the module isn't supported and I also don't get any permissions. Please Help!

twistedindustries’s picture

Status: Fixed » Needs work
loophole080’s picture

applied 6.x-1.4 and still all working great :-) updates page reporting correctly @ #13

eugenmayer’s picture

Status: Needs work » Fixed

i guess thats a local issue

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

grasmash’s picture

I've was having this exact problem in 6.x-1.4. The issue was that the default transition were set to change none->none, review->review, etc. After adding real transitions like none->review, the permission options showed up correctly.

Out of curiosity, is there a point to have those recursive default transitions?

grasmash’s picture

Status: Closed (fixed) » Needs review
eugenmayer’s picture

Well iam really ahve a lack of time to take care about this issues. Anybody is willing to help out?

eugenmayer’s picture

Status: Needs review » Fixed

Actually this was only a side effect and was not intended. Iam this should not be affecting any new installation or upgrades

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.