Last modified: 2011-10-07 20:09:38 UTC
Hi Yaron, i would be nice, if its possible to put the search box on the Special:RunQuery Page from the Bottom to the Top of the Page. If you have long result sets it would be more easy to edit the searchterms at the Top of the Page instead of scrolling down to the Bottom. Every other search although have search parameters at the top. --Simon
We would definitely like to see this feature somehow being implemented, as for long reports it is sometimes challenging to change values at the bottom without losing the focus at the top. Thanks,
I just added code to SVN that does this - if you use the latest SVN code, you just need to add the following to LocalSettings.php: $sfgRunQueryFormAtTop = true; Please let me know what you think of it now. Or should the setting be done per form? And/or, should the "form at top" setting be the default option?
We did some testing and it looks very promising but we would rather have a possibility to switch on a form basis as it gives more control over the behaviour. Sometimes it is required that people go through the display before changing selection parameter and in other cases the query acts more like an "list sheet" with values are manipulated at the top. At the bottom of the inputfields their is a <hr style="margin: 15px 0;"> maybe you can warp this into a css class, so it would be possible to make it invisible in certain cases where RunQuery is solely managed by the URL wpRunQuery=true without displaying any inputfields. Anyway thanks for the effort
It would be great if it could be placed (or not) with something like {{{standard input|queryform}}}. Cheers, Dan.
Okay - maybe the better solution, then, is to have a "|query form at top" parameter to the {{{info}}} tag, instead of a LocalSettings setting. A CSS class for the <hr> is also a reasonable idea. Dan - that wouldn't work.
OK.
MWJames - I think I just fixed the issue with the <hr> showing up when it wasn't supposed to - so I don't think a CSS class is necessary any more.
Alright, I just added support for a "query form at top" parameter, as specified above, to the code in SVN. I believe the issue is now solved; I'm setting this bug to "fixed".
