When adding/editing node families, linear route is forced, later buttons disabled
| Project: | Pageroute |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I have installed CCK, nodefamily, nodeprofile, usernode and pageroute on a test site, with the idea of creating user profiles as multiple nodes - for instance, I have a node type for bio and "about me" stuff, a node type for interests, and a node type for contact information such as e-mail addresses and websites.
I wanted to use pageroute to provide an easy interface for users to edit each portion of their profile. I want them to be able to edit any section, in any order, not force them, for instance, to edit them one after another.
I have the tab buttons feature enabled in my pageroute, but when they first access the pageroute, the first two buttons are enabled, but later buttons are disabled. Nothing I do seems to change this.
I have created pageroutes both with and without the nodefamily association feature from pageroute. I have tried it with and without the states module installed. No matter what, if the pages in the pageroute are for pages with the node family associations, it seems to assume that the forms should be filled out in linear succession.
It does this regardless of whether all nodes in the route are being added for the first time or edited later.
This would be very confusing to my users, and even if I explained a workaround, it will seem like a bug, not a feature, and many users will still be confused despite explanations onscreen.
Is there _any_ way to have a free-form pageroute that can create/edit pages in the nodefamily/nodeprofile set in whatever order a user wishes?
#1
indeed. First I thought I go this way, so that the nodefamily parent node is created for sure.
However, I agree with you that this isn't the way to go. I need to find a good solution for this... Perhaps we better force to create the nodefamily node with the first page.
So, this behavior will apply only if 'Verify that a user goes through each page of the route.' is activated - which depends on the states module.
Are you running the latest -dev snapshot? I thought I had already removed the linear-forcing-feature from nodefamily).
I've you have installed the states module, and you have deactivated it later - re-edit the route again. This makes sure that the option "'Verify that a user goes through each page of the route." is turned off.
#2
Actually, it appears that I am a bit of a twit. : )
The node profile module actually provides the functionality I was looking for - it allows you to include nodes defined as node profiles as tabs in the user account editing page.
The problem I was describing did occur with the version of the module downloadable for the drupal 5.x on the modules page, which was what I downloaded - not the latest dev version, I presume. If it's fixed in dev, I must simply have downloaded an earlier version.
I wouldn't have seen this happen at all if I'd noticed the tab under content type editing for node profile settings.
Apologies. : )
#3
you were right - you can also build this with pageroute.
With the 5.x version you are using the -dev snapshot, but the question is *which* dev snapshot - as they are rebuilt as soon as an update is checked in.
#4
#5
Automatically closed -- issue fixed for two weeks with no activity.