Needs work
Project:
Custom Pagers
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Sep 2011 at 13:47 UTC
Updated:
4 Nov 2011 at 01:03 UTC
Jump to comment: Most recent file
Comments
Comment #1
hydra commentedWell, where did you run into this message? You can use the module perfectly without having views enabled, so in fact it's not a requierment on views necessery!
But it would ne nice to have a notice in the configuration page, that you can use views as base for a custom pager, if you enable views. The default mode for this is, that the area is just not displayed. Baybe an advice, some extra text there to help the user understanding, that there is the possibilty to download the views module to extend this would help.
Something like this perhaps
Comment #2
hydra commentedstatus updat
Comment #3
s.daniel commentedHmm sorry for not posting that information right away. I believe it was right after I enabled the module but coudn't say for sure now.
It was through the upgrade process from d5 through d6 to d7 so I had so many errors to fix and this one was a quick one ;)
Maybe someone else will run into this some time and can add some information ---> set to needs more info?
Comment #4
13rac1 commentedThis is a bug. The following error will be generated when Views is not available.
I like the idea in #1, but also either Views needs to be a requirement or module_exists() needs to be used.