Its extremely frustrating when an issue like this just gets passed around and no one will deal with it. It seems strange that I have to post it here but this is where I was directed.

There seems to be a "problem with core" that when I use views in combination with an access module (acl, content access, forum access) it will prevent a pager to be displayed (of all things) when using Node ID as an argument/filter.

Below are the very simple steps to reproduce the bug.

1. Installed a fresh copy of Drupal 6.16

2. Install views module

3. create a node and add 5 comments.

4. Create a view and add Comment: Body into the Fields and Node: Nid as a filter or argument. Also set use pager to Mini and Items per page to 2. Preview the view and notice a pager is at the bottom (works as expected).

5. Install ACL and Rebuild Permissions

6. Preview the view again and notice the pager is gone.

Installing ACL by itself wont cause the pager to disappear, but as soon as you rebuild permissions it will disappear.

Could anyone help point me the the right direction so Im not wasting everyones time?

Comments

RikiB’s picture

RikiB commented

And yet the Views people wont take responsibility for this issue either:

http://drupal.org/node/754906#comment-2822538

The only hope left is for someone from drupal core to look into this. However the chances of anyone caring at this point is pretty slim. I guess I will wait until someone more important than me runs into this issue and then fixes it over a cup of tea.

The joys of open source. :/

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Closed (duplicate)

I'd say try to keep the Views maintainers informed and get them reproduce your issue (I'm seeing it was not easy so far). This issue is already submitted as #754906: Views pager disappear if I use an argument, so once it turns out to be a core issue, you can recategorize that issue for core. No need to open multiple issues for the same problem.

danielhonrade’s picture

danielhonrade commented

Hi RikiB,

I am also frustrated but if you're really want to get it done, you can create a patch and let others check it, or hire someone to do it. The point is that drupal is an open source, if you see a problem, you can find the problem because the codes are open. People here do this voluntarily, they don't get paid so they do these things during free time unless you're are a gorgeous young sexy lady, just kidding. I hope you understand the deal here.

RikiB’s picture

RikiB commented

I understand that, and it sounds easy when you say it like that but from someone at the bottom of the pole like me its very difficult. I actually wouldn't mind someone acknowledging the problem and putting it in a queue somewhere, at least that is progress.

RikiB’s picture

RikiB commented
Status: Closed (duplicate) » Active

The views people are adamant that this is a core issue, and will no longer respond to my posts. Re-activating this.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Closed (duplicate)

Ok, recategorized the other issue as such. I've already explained that you can move around issues as the suspected cause changes.