I use a custom theme 1000px wide with a left and a right sidebar. This leaves the main content area with around say 540px. This is apparently not wide enough to display all options for this module. Please take a look in the attached screenshot of the mapping settings page to see what I mean. The 'remove' links next to each mapping are not available, so I cannot modify the default mappings.
Can you please take this under consideration and make it so that the settings for each section either wrap bellow (if there is not enough space) or permanently place it underneath the sections. If this is not an option, where should people with the same issue like me 'hack' the module's code and which lines should be changed to have it placed at the bottom?
Thank you in advance.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | verical_config_tabs.png | 32.84 KB | klonos |
| not enough space.png | 25.81 KB | klonos |
Comments
Comment #1
klonosComment #2
alex_b commentedYou also reported "Description field cut off": http://drupal.org/files/issues/description%20field%20cut-off.jpg
Comment #3
klonosYes, I know...
I won't ask for a time estimate or anything or bother you with this again soon, but do you see a fix in the near future? I am asking because all this switching themes back and forth to have things done is a real pain in my neck.
Comment #4
klonos... did I mention that I am prepared to beta-test any quick hack you might come up with? :)
Comment #5
alex_b commentedSorry - I'm not planning on acting on this at all atm. I would welcome a patch though : )
In the meantime, have you considered using an admin theme?
Comment #6
klonosFair enough... I respect other peoples spare time.
Yes, now that I have your answer, I will do that. The only thing is that using a different theme would require me to double check every single change I make to the site. That will slow building a lot, but what can I do. Thanx anyways.
If I hack my way around it, I'll surely post back what I did in order to help others facing the same issue. Please keep this issue open though. I'd like to know that this is in your to-do list and one day it'll eventually get fixed.
Comment #7
klonoswell, I've changed the related css settings in the ../feeds_ui/feeds_ui.css like so:
This moved all configuration sections underneath their respective configuration settings. All I did is I removed (actually I've commended them out) almost all css styles of the left sidebar (configuration options) and all styles of the configuration section (respective settings for each left sidebar option). Next I've set the width of the left sidebar to be the same as the width of my main content area. This made the config section wrap underneath the options.
Now I see the light! Next step is to try and convert options section to a tab-like style or something, so I don't have to scroll down to find the settings for each option.
This is an ugly css hack that works only for my theme. At least I point people with the same issue to the right file and the right point within it. You guys might need to modify the width setting to mach that of your theme's main content area.
At this point I need to ask you alex:
1. Is there a specific reason why you've chosen to code the config interface this way? I mean all (at least most of them) other modules I use have a common concept where there is either collapsible sections for each option/section (the way the Drupal modules admin page is) or there are horizontal tabs.
2. Would you consider a UI rebuild in order to spare people from facing this issue in the future? Ok, I've managed to find a temporary workaround, but this needs to be applied each time the module is updated to a newer version (or perhaps people need to override this in their themes). Remember that modules are here to help people with little or no coding experience get things done. This is the other way right now. Plus I believe there are a lot of users that will have a narrow theme on heir site.
As a side note here, I've seen that in D7 the default way that configuration pages present their option sections is done the way you are trying to do it (see attached image). So there will be an easy transition to that when D7 is here, no need to be doing it now in D6 I think.
But hey, this is your module, so it's also your decision. If you think this all issue is really trivial and it won't effect lots of users, then feel free to even go ahead and change it from a 'bug report' to a 'support request' and mark it as 'fixed'.
Other than that, thank you (yet once again) for all your effort and time spent on bringing this fine module to us.
Comment #8
alex_b commentedI will consider rebuilding this UI for D7, but I'm doubtful that vertical tabs can be used out of the box: Feeds' admin UI doesn't load the entire administration at once and stacks them with CSS visibility but rather loads every tab separately with a full page load.
I'm going to postpone this issue for now but will make sure that if ever I get a chance to rework the UI, I'll take care for space concerns.
Thanks for the detailed reports.
Comment #9
klonosNo problem alex. I'm glad to help in any way I can. Thanx for considering this.
As for the vertical tabs in D7... be it an out-of-the-box solution or not, I still think we'll be facing the same issue with narrow, fixed width themes. The reason I mentioned it is that I was wondering why the current UI doesn't follow the default D6 pattern other modules seem to be using. Anyways...
We'll talk again once other more important issues are solved and once there is time for this one. In the meantime, if I come up with more hacks, I'll be posting it back here to help others. Thank you for not 'closing' this issue.
Comment #10
alex_b commentedWell, simple fieldsets aren't cutting it. Try to think about it, it's not possible to come up with a clear UI with depending options only using only fieldsets. Or what other existing patterns are you thinking of?
I would have loved to use existing patterns. Missing powerful UI patterns in Drupal are a major deficiency IMO.
Comment #11
klonosHey alex... I know your hands are full (I watch the issue queue) with more important things, but I'd like you to know that I came across this Region Visibility module.
Perhaps if you find the time you can add a note on your module's page saying something like:
I know this is only a workaround, since all you do is hide some regions and to some people this might not be desirable, but I think this will help a lot of people till you have the time for that UI rewrite.
Thank you.
Comment #12
klonos...still watching the queue, I see you must still be busy with other things.
...still, nobody else having this issue :(
This is an update regarding the use of the Region Visibility module I mentioned in my previous post. I had no luck with it, as it only hides region contents and not the divs in the .tpl.php files.
...still stuck with my workaround in post #7 :(
Comment #13
malcomio commentedThe workaround I've used is to use ThemeKey to use the admin theme.
The following rules work for me:
drupal:path = import
drupal:path = import/%
Maybe there are historical reasons for it, but it would make more sense to me if the path for the importer was at admin/content/import or similar
Comment #14
twistor commented