Skip to content
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

#SFQuery radiobuttons not always all selected #33

Open
ida opened this issue Feb 15, 2014 · 2 comments
Open

#SFQuery radiobuttons not always all selected #33

ida opened this issue Feb 15, 2014 · 2 comments

Comments

@ida
Copy link

ida commented Feb 15, 2014

I have a calendar configured to show possible selectable keywords in the #SFQuery-div and usually all radiobuttons of the possible keywords are checked.

However sometimes one keyword (always the last of the list?) isn't selected, yet any event with the non-selected keyword set, shows up in the calendar anyway.
To make things worse, after checking the non-checked keyword in the query, the event will be shown twice.
If you then check/uncheck everything works as expected again.

I cannot reproduce the problem, so I have no clue why sometimes things work as expected and sometimes not. Any hint welcome.

@schminitz
Copy link

I don't understand of what keywords and radio buttons you are refering. Can you explain the exact steps to reproduce your bug?

@ida
Copy link
Author

ida commented Apr 29, 2014

I'm referring to the option via the properties-tab to make criteria-values selectable for users in the calendar-view, so below the calendar the user gets radio checkboxes to select possible keywords for filtering search-results, like e.g. 'conference', 'lightning talk', etc. Is it more clearer to you, now?

Right now I cannot even quickly set up a testsite with the newest versions, due to #45.

As I wrote, it is not reproducable for me, sometimes works, sometimes not, when changing nothing, only reloading the calendar-view in the browser.
I might come back to this one time, but due to other priorities, we ride along with an ugly workaround for now: A Javascript checking, if the boxes are all selectable by default initially as supposed to be, and if not, correct that by toggling checkboxes, similar as described in: http://stackoverflow.com/questions/19731887/customize-the-search-portlet-in-plone-for-specific-content-types

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants