Trying to build an views-imagefield-imagecache-lightbox gallery there is some issues that I cannot figure out
starting with this simple & nice example: http://raincitystudios.com/blogs-and-pods/hubert/a-simple-ajax-image-gal...
A CCK content type with 2 imagefields inside
20+ images uploaded per cck node
The problem using this approach is that paging is not possible (viewable) using per node imagefield gallery view with the argument: Node ID from URL
View displays (imagecached) images ok, even lightbox can see all images after the pager limit (e.g 10) if grouped in views. Still "gallery" view has NO PAGER
Has "views pager" been implemented in individual single node cck fields (like imagefields)? or only between different nodes? ( pager there is ... ok)
Any help appreciated... hoping I'm wrong and forgot something else or I'm bugged
Comment | File | Size | Author |
---|---|---|---|
#7 | Edit view sx2 - acl-viewsbug_post1.jpg | 63.74 KB | jannalexx |
Comments
Comment #1
merlinofchaos CreditAttribution: merlinofchaos commentedThe key word here is 'grouped'. If together then they are all a single record, so there is no pager. You need to not group them in this case.
Comment #2
jannalexx CreditAttribution: jannalexx commentedI see, but no groupings produce the same no pager situation. Tested that also. It is probably something else.
I will try to see if a new clean cck node type / imagefield can solve this or try a new installation. thanks
Comment #3
jannalexx CreditAttribution: jannalexx commentedstill no luck, same issue with any cck field (not only images)
i managed to get this working in an other older drupal version site, so it is supposed to work and thats ok & easy.
Here things are getting complicated and I try to figure out what can bring such a conflict.
tried to unload almost all modules
tried to reinstall views (tried 2.1, 2.2, dev2.x)
tried other content types
tried other themes
nothing... !
Same view export is working in the other site!
Any ideas? Has anyone experienced such a conflict? Is there a way to track this behaviour somehow an give u more details? thanks
Comment #4
jannalexx CreditAttribution: jannalexx commentedIts a deeper bug,
The ACL module, which stands for Access Control List http://drupal.org/project/acl,
forces views not to use the pager in some special cases like this one
maybe other side effects live there also. Please consider (posted also on ACL issues http://drupal.org/node/367761)
Comment #5
choster CreditAttribution: choster commentedSince #367761: incopatibility with views 2 (missing pager) is an ACL issue, I think it's safe to close the Views issue.
Comment #6
merlinofchaos CreditAttribution: merlinofchaos commentedI'm confused. That issue is posted by the same person and contains absolutely no information. I have no idea what's going on here, but we're throwing blame left and right without throwing evidence and it makes me uncomfortable.
Comment #7
jannalexx CreditAttribution: jannalexx commentedintension is to prevent others from breaking their views!.. no confusions. I reproduced the issue in a clean installation so I can now give u details
clean install drupal 6.9
install views latest 2.2
install acl (beta3, beta4) and recreate access permissions as pointed
Make a post in node 1 with some comments (more than 2)
try a view like this one:
.. find the pager..
Comment #8
salvis@merlinofchaos: We've found out in #367761: incopatibility with views 2 (missing pager) that enabling Content Access (instead of ACL) will produce the same issue. So it looks like a problem with db_rewrite_sql() — back to you...
@jannalexx: What database are you using? Maybe this provides a clue...
Comment #9
salvisComment #10
jannalexx CreditAttribution: jannalexx commentedmySQL 5, utf8. please if someone reproduced the issue, inform us.. so we can confirm. Let me know if you need further details.
You can also change the title here, final clue has to do with every field not only an imagefield as first stated
Comment #11
merlinofchaos CreditAttribution: merlinofchaos commentedIf the problem is with db_rewrite_sql() then you probably need to find the query as it's supposed to be and how it's getting rewritten incorrectly. My guess is that something is causing the COUNT query to not work quite right.
I can't easily duplicate this, though, and if the problem is in db_rewrite_sql I have very little motivation to chase it down as that's outside of Views and I've got enough to do here.
Comment #12
jannalexx CreditAttribution: jannalexx commentedthanks for all anyway,
if anyone finds the time.. this can be duplicated easily, it cant be my imagination,
if someone use those permission access modules please try and verify, at the time being i will experiment other possible solutions, and maybe I will come with a clue.
it affects all views with per node "Node ID from URL" fields cck and core, if it is an ACL or Content Access db_rewrite_sql() anomaly with core then I will have to pray and try other permission modules, good luck with all your work
Comment #13
jannalexx CreditAttribution: jannalexx commentedMore info. modules Taxonomy Access Control Lite http://drupal.org/project/tac_lite
and Taxonomy Access Control http://drupal.org/project/taxonomy_access
same behavior after rebuilding permissions
Comment #14
jannalexx CreditAttribution: jannalexx commentedexperimental solution..
Using the option distinct I get this error:
after core patch in database.mysqli.inc file from http://drupal.org/node/284392#comment-1049183
db_rewrite_sql causing issues with DISTINCT
my views work with pager and access modules enabled! (but only with distinct option!)
there is also some issues related with access modules in this thread like this one
what do you think of that? at least I have a working solution but I need your point of ..view(s)
Comment #15
neurer CreditAttribution: neurer commentedSame issue here: Trying to build a gallery with identical setup (except Views 2.3 and Thickbox) and module config. Setting distinct to YES also gives me user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DISTINCT(node.nid) [...] I'll try to apply the solution jannalexx mentioned at #14 and report back within a day.
Comment #16
neurer CreditAttribution: neurer commentedWorks. Applied the patch @ http://drupal.org/node/284392#comment-1049183 and set distinct to YES. Pager now shows up. Any chance of getting this fixed, without patching CORE?
Comment #17
jannalexx CreditAttribution: jannalexx commentednote that this is general on fields accessible by views, not only cck or imagefield related
Comment #18
gmclelland CreditAttribution: gmclelland commentedFor any one else who has this problem... I turned off the Organic Groups Access Control Module, then the pager appeared and the tutorial worked for me.
Hope that helps someone.
Comment #19
Anonymous (not verified) CreditAttribution: Anonymous commentedTested this and found the same bug, with all latest version of modules and Drupal. Pager is missing.
Comment #20
Anonymous (not verified) CreditAttribution: Anonymous commentedComment #21
merlinofchaos CreditAttribution: merlinofchaos commentedIf the patch against core mentioned in #16 fixes this, there's not much point in marking this as a bug against Views...
(To answer another question, no, that bug cannot be fixed from within Views).