Center horizontal menu block

For months, the question has been posted in the forums by several users, and yet it remains without a solution. I am now posting the question here as a support request.

Changing the status back to active.

Also, after reviewing the whole list of pending issues, I note that 3 of the 7 pages of user requests have been designated as "won't fix." This is a startling percentage -- nearly half! No other module I've seen has anything close to this proportion of rejected user requests.

I strongly urge you to reconsider your programming policies toward user requested features and support. Nice Menus is among the least friendly and least healthy module support environments on all of Drupal.

If you're overworked and need help from other programmers, ask for it!

I think the astonishingly large proportion of "Won't Fix" responses speaks for itself. If the first response is to punt a problem to the forums instead of probing for more information, then there is an unhealthy user support situation. Imho, a developer should -- at the very least -- direct a support issue to a specific forum thread with a productive discussion that the developer endorses. Currently, there are 4-6 threads about this issue in the forum, none of them particularly productive ... these threads remind me of row boats with only one oar in the water.

Unfortuantely, theming is a critical element of the Nice Menus module; and the css code is fairly extensive. So I don't think it's realistic to punt theming issues. While working on the css code, I read the existing forum threads on the topic and they weren't helpful. After several days of working on the css code and not finding a solution to the simple task of centering the block, I posted my support question here only to have it immediately punted back to the forums.

Based on my experience trying to modify the Nice Menus css file, I believe this css code is not "user friendly." It relies on the Float property, which appears to prevent centering the block -- a common modification that should be easier to implement. This is *not* a problem that can be passed to the forums as it is an inherent problem with the distribution release.

Instead of dismissing the support issue, (again imho) perhaps the bundled css file should be re-written so that add1sun doesn't have to spend so much time helping people with their css problems. It's better to fix the core issue once than putting band-aids on a reoccurring problem. If the core issue is fixed, everyone wins -- the developers get to spend less time supporting the mod, and more users can customize the css file without assistance.

I thank add1sun for her generous gifts of time and knowledge to this project ... particularly since she is doing it for free. I too am working for free, and am working for a non-profit organization; so I completely sympathize with her placing limits on the effort we request of her.

That said, I also feel that marking support and feature requests as "Won't fix" has the effect of burying the issue so other visitors never see it; one actually has to re-set the filter to unhide the posts marked as "Won't fix" ... something that visitors do infrequently. When the issues get hidden, they are dramatically less likely to be solved by a good samaritan. There is no crime in leaving these issues open for several weeks, while perhaps inviting others to offer patches. I think we all know that we're welcome to offer a patch without an invitation, but often that visible invitation directed at a specific problem is the difference between it actually getting done and it not getting done.

I also believe the pending issues area, when viewed without a filter, looks hostile to users because nearly half the issues have been labeled as "Won't fix." This designation suggests, whether intended or not, a level of unresponsiveness and creates a negative impression.

I for one would like to see a sub-community develop around this module, like has around Biblio. It's a good module, that could be great with a little community support.