Closed (won't fix)
Project:
Location
Version:
6.x-3.0-test3
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Anonymous (not verified)
Created:
2 Oct 2008 at 02:14 UTC
Updated:
16 May 2024 at 00:49 UTC
Comments
Comment #1
gionnibgud commentedI completely agree on this one. This would be a huge UI improvement!
Comment #2
yesct commentedusing the cck location fields in a cck content type, you can do this.
I'll mark this as fixed.
Comment #3
gionnibgud commented@YesCT
Not that I really mind but from my point of view this is a "won't fix".
Pointing out an alternate method it's a good thing and can be really helpful for some users but it does not solve this specific issue. Also, location interface does provide a way to assign a weight but in a D5 fashion which is counter intuitive while working on D6 and have some drawbacks. And this is exactly the point of this issue.
cheers
Comment #4
yesct commentedgood point! I'll mark this to have bdragon check if he agrees that his plan is to not fix. thanks.
Comment #5
bdragon commentedACTUALLY, it already has it in D6 but there's a bug in core js that prevents it from working right.
See #303189: Tabledrag doesn't hide columns when the whole table is initially hidden for the solution.
Comment #6
ankur commentedThis looks to be obsolete in 7.x-3.x/7.x-4.x.
Please re-open and change the version to a 7.x branch if I'm wrong.
Comment #7
ankur commented