Posted by mjross on June 22, 2010 at 1:25am
3 followers
Jump to:
| Project: | Content Access |
| Version: | 6.x-1.2 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Using Drupal 6.17, I installed version 1.2 of this module, enabled it, and rebuilt the permissions when prompted to do so. Immediately afterward, the front page displays links at the bottom, labeled "2", "next", and "last" (please see the attached image). But there aren't any next pages. All three links point to ?q=node&page=1. Clicking any one of them displays the "Welcome to your new Drupal website!" page, as though the site has no content, but it does.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| pager.png | 2.39 KB | Ignored: Check issue status. | None | None |
Comments
#1
Is your front page generated by Views? My first guess is that your front page view reacts in an undesirable way to the presence of a node access module. Try installing just ACL or just CA to confirm this.
#2
Sorry for the delay in responding. I still haven't figured out how, in Drupal.org, we can receive notification that someone has replied to a post.
My front page is not generated using a view, but rather is a single page node published on the front page.
I'm new to Drupal, so I'm not entirely sure what you mean by node access modules, but within the "Access control" section of my modules page, I have enabled: Content Access, Module Grants, Module Grants Monitor, Node Tools, User Tools. Is there any other information I can provide that would be helpful?
#3
Log in and click on the "My issues" link on the right. That's the page that you'll want to visit whenever you're on d.o.
I don't know any of the modules that you mention (besides CA). You seem to suffer from module overload.
Create a development site with a new virgin copy of Drupal and install only the modules that you really need. Enable them one by one and write down for each one why you need it. Observe at which point you get the undesired behavior on the front page.
#4
Two other suggestions:
#5
Thanks for the tip.
The two Module Grants modules are needed because the website implements a complex workflow involving different content types and roles. The last two modules in my list are required by the two Module Grants modules.
That is basically what I've done. None of the enabled modules are nonessential.
As soon as I enable the Content Access module.
Good suggestion. The unnecessary pager on the front page is displayed for all unauthenticated users, and all logged in users, except 1. I verified that user 1 is not seeing the pager because the "pager" div is not part of the HTML output, and not simply suppressed with "display: none".
Thanks for the suggestion. I did so, and none of the output indicated anything about the pager.
I checked the 'frontpage' view in the Views page, and confirmed that it is not enabled.
Any idea as to where in Drupal that front page pager might be controlled (particularly anything involved with the Content Access module)? I don't know what part of Drupal controls the pager for a non-view node page.
#6
Well, start with CA and find out which of the others contribute to this problem.
CA doesn't deal with pagers at all, so it must be some other module that erroneously puts up a pager in the presence of CA (probably in the presence of any node access module).
Did you try installing just ACL without CA? This wouldn't be a solution, of course, but it would help to narrow down the suspects.
#7
I tried both of those approaches, and there was no obvious combination that's causing the problem. I don't have time to try all the permutations (the client may request site launch as early as tomorrow), so for now I'll simply use CSS to hide the pager. Thanks for the input!
#8
If/when you have a chance to find the cause of the problem, you might want to also look at theme_pager() in your theme. That's a place to start troubleshooting where the bad pager data is coming from.
#9
I know this is 2 years old but it might help somebody else figure it out...
I had a similar problem.
Work around: i increased the number of posts on main page. As soon as additional content is greater than this limit, then once again I'll have a pager to a blank area. Anyway to disable the pager on the front page?... as i was writing it I found the post to disable the front page pager..
http://drupal.org/node/250070