The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.First of all, I would like to say that this is a spectacular module, and the patch located in http://drupal.org/node/389952 did work.
I have an issue to resolve, and I'm not certain if this patch was the cause of it (or my application of the patch). I did run into the issue of all the hunks not being applied, but after a few tries I figured out that it somehow missed the destination file for the includes in the views integration. I entered the filename, and it appeared to have patched correctly.
The issue I have is that I built a view of all members of a group and their signups, but the view refuses to display more than 50 entries at a time. I can change the amount displayed per page, and the pager works fine, but the view mysteriously cuts off after it lists 50 entries. Since the argument is the organic group with the user:signup relationship attached, I wanted to know if this patch (or the module) could possibly be causing this issue. So, could the patch have affected the views in such a way as to cut off or terminate the view prematurely?
I haven't tried building the view without the patch as I'm working on a production site and didn't wish to create any serious problems.
So, to summarize, the bug is a view that uses a group argument tied to a signups relationship to display all signups for a given group, but the display stops. I am certain of the incompleteness because I see usernames say, A-K appear (sorted alphabetically), and the view stops by displaying only half of the last user's classes. I am not certain if the bug is cause by signups itself, the patch, or another aspect of my site, but I would like to know if the patch COULD be the cause.
Thank you for your time.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | view.php_.txt | 2.23 KB | bismuthdrummer |
| #2 | problem.PNG | 16.32 KB | bismuthdrummer |
| #2 | view_signup_1.php_.txt | 6.75 KB | bismuthdrummer |
Comments
Comment #1
dwwSounds like your view is configured not to display more than 50 results. If you exported your view to PHP and attached that here, it'd be a lot easier to confirm this theory.
"I haven't tried building the view without the patch as I'm working on a production site and didn't wish to create any serious problems."
Do yourself a favor and setup a cloned copy of your live site which you use for testing. Operating without a test site is a recipe for "serious problems". ;)
Comment #2
bismuthdrummer commentedI would love to have a cloned copy of the site to run from.... unfortunately, my site is hosted generously for free on a dedicated server, and the networking guy who set it up didn't want to do a multi-site install. So, I could pay for virtual hosting somewhere, but the hosting environment would be entirely different. This is a small production site; roughly a thousand users use it once a year to register for classes at a summer camp.
I'm fine with starting from the ground up with troubleshooting.... I've tried the view set to 100, but the results stay limited to the 50 I mentioned. From my understanding, if the pager is enabled, all results should display. I've enabled the pager, so all results should display. Is this correct?
I've attached a screenshot of my problem. These Scouts (it's a Boy Scout camp) should have FIVE classes, but the last entry only has three, and there are no more pages. Also, "R" is the first letter of the last username, when there are still usernames beyond R.
I've also attached an export of my view, as requested, with the limit per page set to 100. The same problem occurred.
Comment #3
bismuthdrummer commentedIs there any more information I can provide? Where should I begin to start troubleshooting this matter?
I posted the issue here to learn whether or not the User: Signups relationship could be the cause. All of my other views work fine (without this mysterious cutoff), so I just wanted some ideas thrown at me.
Any thoughts at all?
I appreciate your work on this module. I just need some input before I go digging into php code I've never seen before.
Comment #4
bismuthdrummer commentedI rolled back from the patch to the latest stable release of signups, cleared the cache and the views cache (maybe unnecessary), and I constructed a new view of all signups. So, I simply restricted to all nodes containing User: signups relationship.
The view still truncates after 9 pages with the limit at 100 per page, stopping in the B's of the usernames.
Could this be a database error? How can I find out, and how could I possibly fix such an error?
I have 700 pages of classes that have signups attached, so redoing the entire signups system is out of the question at this point, for this summer's classes anyway. I don't have too much spare time to troubleshoot so I haven't had a chance to ramp-up on php and study/play with the code.
Any advice at all would be appreciated.
Comment #5
jzornig commentedI'm getting this issue. My view is to display all the signup node titles along with the usernames of the users signed up to each node. If I just present the results I get the correct 200+ rows presented. However as soon as I try to use a pager the results are truncated to about 50-60 results. i've tried all the pager options (full, mini, ajax on/off, 10-100 per page) always with the results truncated. i turn off the pager and all the results appear.
Comment #6
pandersb commentedIssue moved to http://drupal.org/node/960142
Comment #7
pandersb commentedIssue moved to http://drupal.org/node/960142
Comment #8
dwwI marked #960142: Pager doesn't appear and list gets cut off at the limit per page. duplicate, but at least there's an exported view over there so in theory there's enough information now to reproduce the bug. Given more than 1 person is having a problem, I'll assume this really is a bug. I don't have time to try to reproduce and debug this now, but maybe one of the other signup maintainers can take a look...
Comment #9
wendymc commentedHi there! I am experiencing this same issue. I have a view that has about 100+ entries and I set it to use pager and display 75 items per page. It then only displays about 60 items. If I set it to 20 items per page it still only shows 3 pages of results, same 60 results. If I turn the pager off and set it to unlimited it shows all of the results.
Any help would be greatly appreciated!
Here is my exported view:
$view = new view; $view->name = 'RTDAwardWinners'; $view->description = ''; $view->tag = ''; $view->view_php = ''; $view->base_table = 'node'; $view->is_cacheable = FALSE; $view->api_version = 2; $view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */ $handler = $view->new_display('default', 'Defaults', 'default'); $handler->override_option('fields', array( 'title' => array( 'label' => '', 'alter' => array( 'alter_text' => 0, 'text' => '
', 'make_link' => 0, 'path' => '', 'link_class' => '', 'alt' => '', 'prefix' => '', 'suffix' => '', 'target' => '', 'help' => '', 'trim' => 0, 'max_length' => '', 'word_boundary' => 1, 'ellipsis' => 1, 'html' => 0, 'strip_tags' => 0, ), 'empty' => '', 'hide_empty' => 0, 'empty_zero' => 0, 'link_to_node' => 1, 'exclude' => 0, 'id' => 'title', 'table' => 'node', 'field' => 'title', 'relationship' => 'none', ), 'field_awardcycle_value' => array( 'label' => '', 'alter' => array( 'alter_text' => 0, 'text' => '', 'make_link' => 0, 'path' => '', 'link_class' => '', 'alt' => '', 'prefix' => '', 'suffix' => '', 'target' => '', 'help' => '', 'trim' => 0, 'max_length' => '', 'word_boundary' => 1, 'ellipsis' => 1, 'html' => 0, 'strip_tags' => 0, ), 'empty' => '', 'hide_empty' => 0, 'empty_zero' => 0, 'link_to_node' => 0, 'label_type' => 'none', 'format' => 'default', 'multiple' => array( 'group' => 0, 'multiple_number' => '', 'multiple_from' => '', 'multiple_reversed' => 0, ), 'exclude' => 1, 'id' => 'field_awardcycle_value', 'table' => 'node_data_field_awardcycle', 'field' => 'field_awardcycle_value', 'override' => array( 'button' => 'Override', ), 'relationship' => 'none', ), )); $handler->override_option('sorts', array( 'field_awardcycle_value' => array( 'order' => 'ASC', 'delta' => '-1', 'id' => 'field_awardcycle_value', 'table' => 'node_data_field_awardcycle', 'field' => 'field_awardcycle_value', 'override' => array( 'button' => 'Override', ), 'relationship' => 'none', ), 'title' => array( 'order' => 'ASC', 'id' => 'title', 'table' => 'node', 'field' => 'title', 'relationship' => 'none', ), )); $handler->override_option('filters', array( 'field_awardcycle_value' => array( 'operator' => 'not empty', 'value' => '', 'group' => '0', 'exposed' => FALSE, 'expose' => array( 'operator' => 'field_awardcycle_value_op', 'label' => 'Content: RTD Award Cycle (field_awardcycle)', 'use_operator' => 0, 'identifier' => 'field_awardcycle_value', 'optional' => 0, 'remember' => 0, ), 'case' => 0, 'id' => 'field_awardcycle_value', 'table' => 'node_data_field_awardcycle', 'field' => 'field_awardcycle_value', 'relationship' => 'none', 'override' => array( 'button' => 'Override', ), ), )); $handler->override_option('access', array( 'type' => 'none', )); $handler->override_option('cache', array( 'type' => 'none', )); $handler->override_option('css_class', 'rtdWinners'); $handler->override_option('items_per_page', 20); $handler->override_option('use_pager', 'mini'); $handler->override_option('use_more', 1); $handler->override_option('use_more_always', 0); $handler->override_option('distinct', 0); $handler->override_option('style_plugin', 'list'); $handler->override_option('style_options', array( 'grouping' => 'field_awardcycle_value', 'type' => 'ul', )); $handler = $view->new_display('block', 'Block', 'block_1'); $handler->override_option('block_description', ''); $handler->override_option('block_caching', -1);