Problem passing default argument to Views
dydecker - September 17, 2008 - 18:21
| Project: | Custom Pagers |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Description
Hi,
perhaps i am missing a step, but I can't seem to pass a default argument to Views from CP.
I want to create a pager for different Taxonomy terms. 1 term = 1 series of pages.
Please let me know if this sequence is correct;
- set the Views argument to taxonomy term ID.
- set "Action to take if argument is not present" to "select all values"
- select this View in Custom Pager UI
- Write term ID into "default argument box".
But when I do this - even just writing a number not using [term-id] token, it doesn't change the view - I just get all terms. am I missing something simple?
Cheers
#1
Are your views working properly or is it just the pagers? I just set up something I believe to be similar but have it working.
#2
Same problem here. Same set-up as Dydecker. The view works, but arguments are not passed from CP to views.
#3
Same problem here, too.
Views is behaving as if it did not receive an argument.
Setup:
Drupal 6.6
Views 2
- set up to receive taxonomy term ID as an argument
Tokens enabled
Custom Pager 6.x (patched from other thread)
- passing [term-id] as an argument
#4
This problem is experienced when the argument handler is not on the default display.
That is, you absolutely need to have the argument setup on the default display. It can't be in any other display, since Custom Pagers will not see it there. Seems to me that Custom Pagers for Drupal 6 should have an option to let you select which display you want to use, rather than assuming the default.
#5
I can't confirm that. I do have the problem although I have my argument setup on the default display.
#6
Attached is a patch that corrects a wrong variable name that holds the arguments. Works for me now.
#7
This patch fixes a similar problem for me too.
#8
Fixed in the latest dev snapshot. Thanks!
#9
Automatically closed -- issue fixed for 2 weeks with no activity.