New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues in Smart Search "Advanced Search" #5463
Conversation
The first outstanding issue is trivial: just delete the associated code. The second one is more tricky and out of my reach: I think it is more @dgt41 territory... As the second outstanding issue is definitely more important and more difficult to solve, anyone taking it into his hands should feel free to open a new PR and incorporate my fix for the lesser issue into it. I didn't touch the associated JS (not even by deleting the useless code) so that we can start with a clean situation. |
EASY! Wrong target div name!! Commit is on its way... 😄 |
With the latest commit this PR solves also the "outstanding" issues. |
... there is something I still don't like: all select boxes have I don't think this is correct, but it is something that must probably be searched in And also the |
probably not: all the Go for testing!! 👍 |
@smz Right now I am on the move and cannot spare some time for this and next week is kinda holidays… Anyway just seeing what you’ve done here I have to warn you that all this code you removed is probably the same from bootstrap slider and it shouldn’t be removed but fixed. The idea behind this, its that this affects front end and some templates may not use BS so in that case the front end won’t be functional. |
@dgt41 Dimitris, the code I removed wasn't working since the times when someone decided that Anyone not using BS in front-end has the responsibility to set-up his working framework and the needed overrides with associated JS. We cannot throw random (and not working) JS in our views assuming that this may be useful in different scenarios based on who-knows-what framework and views. |
@dgt41 ... and "fixing" that code by adapting it to the correct target ID will in any case break that 0.0001% of (totally hypothetical) sites who are still using a non-BS framework. But even more, if they are still using the old Conclusion: 100% B/C |
Found a new issue and fixed that too: in the "Result Description" dates conditions ("before", "after" and "exact") were not translated. |
I strongly believe JS code belongs to "column 1" in generated HTML
Sorry if this became an "omnibus" PR, but it is a case of serendipity in finding new issues starting from a single tiny one... To recap, for testers, this PR now fixes the following:
|
@smz I see it as a wiser choice to leave the script as is and just add the missing |
@dgt41 I'm afraid you're missing the point: the bloody thing is (and was) already BS. I didn't change anything to make it more "BS dependent". Maybe you don't have the code at hand, but, when you can, give it look and also try to comment out the slider JS: "wow! slider still working... WTF!" (that was my reaction when I did it while trying to fix the "Expand Advanced Search" option into that piece of code...). I wasted hours into the damn JS trying to figure out HOW it could work, and at the end... it simply wasn't! Since 2012. What I would like to do with this PR is to have things working, now, for 3.4.0. I'm not breaking anything and I'm fixing 3 bugs. If you think that in the future we should be less BS dependent, I can agree with you and when we will move all of this to layouts we can make wonders for that, but IMHO this is not the timing. |
@smz if you just add the |
No, Dimitris, because the JS is also handling the cleanup for the unused advanced fields (and hence the URL). To fix it I should modify the script by changing the target and at that point we will have two colliding JS functions (the BS and "ours") handling the slider. If I instead just fix the target only in the "fields cleanup" part of it and leave the slider JS as it is we will have a JS targeting a non-existent slider. What will be the sense in that? |
OK I just stated that this is the wrong way (my opinion). You introduce BS dependency and therefore this cannot be undone before v4.0 |
@dgt41 BTW, I just tried to follow your suggestion and just added the That JS is simply a left-over of the times we had a totally different HTML structure and must be adjusted to the current one. As far as regards the "slider toggling" part of it adjusting is removing. |
Dimitris: I A M N O T I N T R O D U C I N G B S D E P E N D E N C Y |
Historically, BS dependency, here, has been introduced on 2012 August 16, by @kyleledbetter with his commit cd663c0 titled (guess what?) "Bootstrap the site." |
I've tested the patch with the staging, but I see only the suggestions, not the advanced search fields (see attachment) This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5463. |
@stellainformatica Do you have advanced search enabled in the options? I think it's disabled by default. |
Sorry, I forgot to make the Index before testing :P This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5463. |
👍 |
@chrisdavenport We still have this open for com_finder... |
@test OK After patch, it works fine This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5463. |
Thanks for testing, commenting and coding -> RTC This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5463. |
The issue:
When the "Expand Advanced Search" option is selected, the Advanced Search form should be displayed as expanded: this does not happens.
The fix:
Add the
in
class to the advancedSearch <div> when the option is selectedMore issues NOT SOLVED by this PR
data-toggle
)&Search=&t[]=&t[]=&t[]=
)P.S.: The above issues have been solved too