Issue Details (XML | Word | Printable)

Key: SCAFF-212
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Christian Nesemann
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Confluence Extension: Scaffolding Plugin

{label-options} doesn't work together with 'blank'-option of {list-data}

Created: 16/Apr/08 12:08 PM   Updated: 29/Aug/08 04:55 AM
Component/s: None
Affects Version/s: 2.7-dr9
Fix Version/s: 3.0.0

Time Tracking:
Not Specified

Issue Links:
Relates
 


 Description  « Hide
Just noticed that {label-options?:...} doesn't work together with the |blank=true option of {list-data}. So if the "blank"-label is choosed, always the first label in the list will be set instead of none.

That's really confusing for users if you have more than one label-selection field and they want to choose only a label in the first selection field. At this time they have to choose the same label twice.

(we have long lists, so we can't move to a checklist, because it gets unclear)



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
David Peterson added a comment - 16/Apr/08 01:46 PM
I'm a little unclear on exactly how you're using it. You have multiple {list-data} fields with the same name to allow multiple labels to be selected? If so, you should try just naming them with different names. Alternately, use the 'multiple' option so that you can Ctrl+Click to select more than one label.

Could you provide the wiki markup you're using so I can replicate your issue? Thanks.


David Peterson added a comment - 16/Apr/08 01:56 PM
Ok, I've done a little testing, and I'm not sure if this is the same bug you're having, but I have found out that once you have selected a value with a {list-data}, it will ignore you setting it back to 'blank'. This is a general bug with {list-data}, not specifically with {label-options} however, so I'm not sure it's the same issue.

David Peterson added a comment - 16/Apr/08 02:11 PM
Not sure that this issue is exactly what I described above, so I've created SCAFF-213 to ensure it gets resolved next round also.

Christian Nesemann added a comment - 17/Apr/08 07:49 AM
Hi,

yes you are right. The result is the same.

That's the test-markup.

{list-data:ldTEST2|blank=true}
{label-options:ONE,TWO,THREE,FOUR}{list-data}

You can choose between ONE to FOUR but not reset the list to the blank value. If set to the blank value always the first label is set.
Too bad there is no workaround like with {list-option} cause you can't set a (" ") label.

Btw. might you add a component {label-options} to the issues, so that i can vote (create an issue) there for a removing label feature. Haven't found any request for it.

Christian


David Peterson added a comment - 17/Apr/08 08:01 AM
Ok, so it is the same issue. You might be able to have a workaround in the interim by using a blank {list-option} at the start of the list. Eg:
{list-data:ldTEST2|blank=true}
{list-option}{list-option}
{label-options:ONE,TWO,THREE,FOUR}
{list-data}

I'm not 100% certain it will work, but it's worth a try.

With regards to the other request, go ahead and just create the issue with the details - don't worry about assigning it to the correct module. There are several macros missing from the module list now - it's too hard to keep up...


Christian Nesemann added a comment - 17/Apr/08 03:13 PM
Hi,

thanks for the idea. Works great. Haven't thought of merging those two options.

Will now create an issue for the other bug.

Thanks again! Great job you are doing here.


David Peterson added a comment - 29/Aug/08 04:55 AM
This has been fixed for 3.0.0