I'm using pageroute and workflow to guide my users through thir node profiles and there is an interface problem I cannot resolve. Please have a look at the attached image:

1 is what every user (including superadmin) sees when he enters the pageroute for the first time. The first thing I don't understand is why the first two buttons on the top are activated and the the two on the right aren't. However the normal user can go through all four node types even the ones with the inactive buttons but only through the forward button. At the end he submits and all data is stored. But if the user returns to the pageroute the two buttons on the right are still inactive.

The superadmin however starts with what you see on image 1 as well but when he fills in the third and the fourth page the relating buttons turn active. (see 2)

I've checked
- the content type settings (all four content types have exactly the same settings)
- the pageroute pages (all four pages have exactly the same settings)
- access control (users have similar rights to all of the four content types)
- workflow: I left workflow set to its standard settings

cheers, xl

CommentFileSizeAuthor
issue_with_pageroute.gif12.75 KBAxel_V

Comments

Axel_V’s picture

Axel_V commented

After hours of fiddling around I found out that this was due to the pageroute worfkflow. After deactivating it, I was fine.

fago’s picture

fago
Primary language German
Location Vienna
commented

yep, that's a feature provided by the experimental workflow module. however it should work for every role. Do you still want to track the bug? Had the workflow transitoins permissions been correctly autoconfigured ?

Axel_V’s picture

Axel_V commented

I've started with the standard settings of the workflow transitions. In order to find the problem I've switched permissions on and off and tried different constellations. No change.

fago’s picture

fago
Primary language German
Location Vienna
commented

you can associate this workflow with the usernode and enable the workflow tab for it. Then go to an usernode of an user for whom it's not working and have a look at the workflow tabs. Were state-changes applied? Have been access violations logged in the log?

You can try to disable the workflow through editing the route and then enable it again.

Axel_V’s picture

Axel_V commented

Didn't have time yet to go through your recommended check. I'm fine without the workflow but I'll be happy to help finding the bug (if it is one then). For the moment one more observation: I've installed my pageroute without the worklfow and pagerout_worklfow modules and everything is fine. Today I've activated this modules again on my testsite just to see what happens. As soon as I do that I'm back to what you see on the image that I've attached to my first post. The other thing is that at this point the tick box "Create a workflow for this route" was unticked. But if I go to the worklfow admin, there is a workflow already and if I tick the box, another workflow appears.
xl

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Postponed

yes, if you uncheck the option the workflow isn't used any more. I don't know if it get's deleted, however if you check it again a new associated workflow will be created.

There will be changes to this, as I'll write a workflow engine for this. So this all should be fixed with a new versoin of pageroute_workflow that's less experimental ;)

Tauran’s picture

Tauran commented
Status: Postponed » Closed (won't fix)