Active
Project:
Views (for Drupal 7)
Version:
7.x-3.3
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Aug 2011 at 13:21 UTC
Updated:
5 Aug 2016 at 19:08 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dawehnerCan you give us a view where this problem appears? Therefore please attach an export of the view.
Additional "sometimes" is somehow unsure, as this is a bit fuzzy. Please describe what you did when the bug appeared,
sadly we can't see your actions.
Comment #2
mirkba commentedSorry, the behavoir is a little bit strange. See the attachment for an export of a affected view.
When I open the view to edit and add a filter criteria "Taxonomy term: Term" with "autocomplete" as selection-type, there is no autocomplete-field. When I try it with the dropdown-type, everything is fine. Now clicking on "remove" to cancel the filter-adding with dropdown and starting a new try with the autocomplete-type, I get a autocomplete-field.
In short: I have to try adding a filter with selection-type "dropdown" first to get the autocomplete-type working. Hope my problem is a littel bit clearer now.
Thanks, mirkba
Comment #3
dawehnerI definitive have used the autocomplete some time ago, so this might be a problem with broken javascript.
Can you open firebug and see whether there are any kind of js errors on your page?
They would cause the autocompletion to break.
Comment #4
esmerel commentedComment #5
izudaire commentedHi,
I'm having same problem: when having to select a filter criteria, selection box is not apperaring besides operator. Digging into html with firebug div.form-item-options-value has element.style applied (display:none)... when switched to display:whatever appears nicely. It looks like there is some javascript turning off element but don't know where to search for it.
No javascript error is appearing in firebug.
Most of the times I try to set a taxanoym term filter this problem is reproduciong, but never with other type of filters using similar screen (like language selection).
Comment #6
dawehnerThis might be a problem of #ajax, #states or #dependency . They are all hard to debug and fix.
Maybe you could provide a step-by-step clicking use-case so at least you can get a sure way to reproduce it.
Comment #7
rico.schaefer commentedI have the same problem, not only with autocomplete-field. I choose another admin-theme (ATAdmin from AdaptiveTheme), that works.
Comment #8
dawehnerWhich admin theme did you used before?
Comment #9
esmerel commentedComment #10
fischeme commentedI ran into the same bug creating a new calendar view from template (using calendar 7.x-3.2, Drupal core 7.12, Bartik admin theme) and adding a filter criterion based on a taxonomy field. I select autocomplete after selecting the field and the configure filter criterion page fails to include the entry field for specifying the value to filter against. Tracing in FireBug, all the Ajax seems to complete fine and there are no bugs reported. Again using FireBug, I found the relevant field has "display: none" in its style (code excerpt follows). Using FireBug to remove the style rule caused the field to display and I was able to successfully complete the task.
All this said, I saved my view and subsequently tried to create the problem again in another browser and the UI worked fine. Returning to my original browser, I logged out and back into my Admin account and found the functionality to work as well....So, this seems to be a rather particular situation on a new view or where something is not right in the user's session.
Comment #11
rico.schaefer commentedsorry for my late reply, before i used the seven-theme, i think.
Comment #12
stongo commentedReporting same issue using Seven as administration theme with Select List.
<div class="form-item form-type-select form-item-options-value" style="display: none; ">Comment #13
junipertwist commented4 years later and this does not appear to be fixed. I am having this problem as well, changing "display:none" to "display:block" is the only fix. Using the Seven theme.
Comment #14
carlodimartino commentedYes exactly the same problem here with Seven as the admin theme. Was driving me bonkers! Switching the admin theme to Garland fixes problem for me.