Closed (works as designed)
Project:
Signup
Version:
5.x-2.4
Component:
Views integration
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
13 Sep 2008 at 20:23 UTC
Updated:
23 Sep 2008 at 21:59 UTC
The Current Signups block displays only registered signups that are still open. Where can I change it so that it displays all registered signups for that user regardless of whether they're open or closed.
Comments
Comment #1
sunfish commentedJust realized that a custom view can solve my problem. But...
When I tried to add one more filter "Signup Node Open/Closed are Closed", I received the following error:
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 ''') AND (signup_log.uid = 1) LIMIT 0, 10' at line 1 query: SELECT node.nid, node.title AS node_title, node.changed AS node_changed FROM node node LEFT JOIN signup signup ON node.nid = signup.nid INNER JOIN signup_log signup_log ON node.nid = signup_log.nid WHERE (signup.status = '0') AND (. '') AND (signup_log.uid = 1) LIMIT 0, 10 in /drupal_root/includes/database.mysql.inc on line 172.
Comment #2
sunfish commentedUpdate
While adding an additional filter of any kind results in a sql error, deleting the current one doesn't. So I achieved what I want by deleting the default filter.
Comment #3
sunfish commentedJust one more thing, adding more than one sort criterion also causes sql error...
Comment #4
dwwSounds like this might be a bug, if anyone can reproduce it. I don't have time now (hopefully soon) but if anyone else can try, that'd be great. Thanks.
Comment #5
dwwGlad you found the existing filter and just removed it -- that's certainly the best solution to your originally stated question.
I just tried to reproduce the bug on a test site and failed -- I could add any filters and sorts I wanted on this view and never hit any SQL errors. I also recently modified these views on groups.drupal.org and had no problems there, either. If you have reason to believe this is a bug, please provide more info on exactly how to reproduce what you're seeing. Thanks.