Hello,

Found some strange behavior in an exposed User Filter today.

If the exposed filter is initially empty but is filled in by the user, the view shows X results.
If the exposed filter is filled initially with the same value (by the administrator, or if the filter is simply not exposed), the view shows X+300 results.

All other values and conditions are the same.

Not a critical issue but seems worth a look.

Thanks a lot!

CommentFileSizeAuthor
#3 ViewCode.txt44.02 KBgrahamvalue
FilterInitialFilled.png69.25 KBgrahamvalue
FilterInitialEmpty.png68.59 KBgrahamvalue
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

serenitystocks created an issue. See original summary.

chiri_iker’s picture

chiri_iker CreditAttribution: chiri_iker as a volunteer commented

I have tried to reproduce the issue .
Here is the observations -

  • If the exposed filter is initially empty , the view shows all the results
  • If the exposed filter is initially empty ,and if user choose a certain value, the view shows X results
  • If the exposed filter is filled initially with the same value, then also view showing X results

Can you please export the view and paste the code here
Cheers :)

grahamvalue’s picture

grahamvalue CreditAttribution: grahamvalue commented
FileSize
ViewCode.txt44.02 KB

Sorry,

There is a slight error in the bug description.
The difference is actually WRT to an exposed vs non-exposed filter; both using the same value.

Attached is the code for one of the views for which the discrepancy occurs.
The error happens for on other views too.

Thanks for looking into it :)

grahamvalue’s picture

grahamvalue CreditAttribution: grahamvalue commented

The discrepancy occurs when the "user name" filter is exposed and manually filled (by the user) with the currently hard-coded value.