Active
Project:
Content Complete
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 Oct 2010 at 18:10 UTC
Updated:
13 Dec 2010 at 13:29 UTC
How is the weigth at the moment. Order of fields or alphabetic order or .... ?
When showing the block there is always the same message what field to fill in the next.
Would be very cool if one could influence this somehow.
Maybe in modules settings page something like random, weight, alphabetic, default
OR
within every field a special form where one can define the sequence.
So the effect would be e.g. with random with every page refresh one if not filled out values is shown and not always the same unfilled field.
Comments
Comment #1
baff commentedPS: e.g. if a user is not willing to fill out a special field he will never bypass this field. Imagine something like sports in content profile. If one is not interested in sports .... the block will always show sports to fill out next.
Maybe another approach would be to have some kind of "ignore" button, so one is not reminded of sports anymore, but the next one in order e.g. litrature will be shown in the block.
Even better maybe a "later" button, so if one is not interested at the moment in filling out sports, then after clicking, sports will be the last field to be shown in the "to fill block" and the next (literature) is shown. This would be a circular approach.
Or maybe "ignore" button AND "later" button together ...
Comment #2
pvhee commentedHi baff,
thanks for the suggestions. Right now the order indeed is alphabetic (but alphabetic on the machine name of the field, not the human-readable name). It would indeed be very useful to have:
1) administrator defines the sequence of the fields that need to be completed
2) user can "skip" a field and go on to the next field (without that the node completion increases)
I am not accepting any more changes for the Drupal 6 release and instead all new features should be developed for the Drupal 7 port of this module (after which it can be back-ported to Drupal 6). I will move this issue to the Drupal 7 queue when the branch is created (this is work in progress).
Comment #3
baff commentedThanks for your answer!
Comment #4
yannickoosubscribe
Comment #5
YK85 commentedsubscribing