Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I *think* this View is provided by the Views module (if not apology): machine name Glossary.
On first enabling it, I only got access to 10 items meaning that any that any content starting with letter 'I' or above cannot be skimmed through. If I merely set the pager to be Inherited from the parent then I get access to all content. Likely not the proper way to 'fix' it but it works for me.
Feel free to close if that's a moronic report...
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | glossary-view-1193284-14.patch | 743 bytes | linl |
| #13 | glossary.png | 61.75 KB | dawehner |
| #12 | 1193284-glossary-view-export-7.txt | 6.47 KB | linl |
| #12 | 1193284-glossary-view-export-6.txt | 5.68 KB | linl |
Comments
Comment #1
neoglez commentedI don't know exactly what you mean, i don't see any 'Inherited from parent' configuration option for the pager.
Comment #2
dawehner@neoglez
If you have an attachment display you can configure to load the pager from the main display.
You can find it under the pager settings on attachment displays.
Comment #3
RogueM commentedyes, that's exactly what I did, if I'm following you: I set Inherit pager to Yes using the Attachment display. I guess I could have more simply and more logically set the attachment pager to 'display all items' but I'm getting an Ajax error when I select that option...
Comment #4
RogueM commented... btw note that I am using Views 3. I understand that the UI is significantly different than previous version, so perhaps that's why we are using different descriptive. Perhaps.
Comment #5
neoglez commented...just missed the attachment display
Still sounds to me like working ok (as designed):
That's OK.
(Undestanding getting access as viewing)
Or you mean only 10 elements are shown and no pager navigation??
That's ok too. (i assume the parent is using full pager )
Of course, the ajax is another thing.
(i can not reproduce this part)
Comment #6
RogueM commentedyes, the ajax error I got rid of just now, so edited my post (sorry)... now I set it up to 'display all items' with the same effect.
What I mean is that, out-of-the box, on my servers, you can only select the first 10 options above the display, from A to H, plus a couple of quote marks since we've got some content starting that way. So, no way to access content that starts with the letter I (i.e 'I've posted this comment') and up from the glossary.
Hope that clears the meaning of my previous post.
Comment #7
neoglez commentedNow i undesrstand, yes this is the normal behavior, i think this not classify even for a Feature Request since what you want to achive can be done (as you did) already.
Comment #8
RogueM commentedthen I don't understand what the glossary view is for, besides an example of listing select topics in a ordered fashion... I can't see anyone having any use for it as it ships, but as you said it can be tweaked to taste.
Comment #9
linl commentedSorry to reopen, but this doesn't seem right. The description of the glossary view says "A list of all content, by letter", but it shows only the first 10 letters, A-J, rather than A-Z.
In Views 2 the default view shows a full A-Z list in the attachment, but in Views 3 I have to change the Attachment "Items to display" from 10 to "Display all items" in the Basic settings to make it work as expected.
I've also noticed the same thing in Views 6.x-3.x-dev (2011-Jul-31).
Comment #10
neoglez commentedWhat should be written?? Someting like: A list of all content, by letter, showing only the first 10 letters and configurable to show ALL LETTERS??
As i said before this doesn't classify as a bug report.
Please read Views issue queue guidelines.
Comment #11
merlinofchaos commentedHm. No, the glossary is intended to not use paging on the summary. There may be an unintended change due to the shift to pager plugins in Views 3 that nobody caught. It probably just means adjusting the glossary view and re-exporting.
Comment #12
linl commentedAttached are exports of adjusted glossary views to show all letters, for both 6 and 7.
Comment #13
dawehnerI just tested it it with ~1100 nodes and the output looked fine.
PS: Needs review means that there exist a patch. So is this still an issue on the latest dev version?
Comment #14
linl commentedApologies for using the wrong status in #12.
Yes, it is still an issue in the latest dev, I've attached a patch.
Comment #15
dawehnerThis makes sense, commited to 7.x-3.x.
It probably be worth to backport but the patch does not apply
Comment #16
dawehnerAll views should probably be reexported for 6.x-3.x
Comment #17
beto_beto commentedhello
i want to ask how could i theme Glossary views Attachment ?
any suggestion plz
thank you
Comment #18
chak_boss commentedHi all,
No one has giving the proper solution for this.
please anyone help for this.
How to print all the letters in glosssary view.
There need any custom code to do?
Thanks
Comment #19
chris matthews commentedThe Drupal 6 branch is no longer supported, please check with the D6LTS project if you need further support. For more information as to why this issue was closed, please see issue #3030347: Plan to clean process issue queue