Closed (fixed)
Project:
Smartqueue Per User
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Critical
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Aug 2008 at 05:07 UTC
Updated:
30 Aug 2008 at 17:52 UTC
Jump to comment: Most recent file
Comments
Comment #1
ezra-g commentedBumping priority: This is critical for sites with 1000's of users.
Comment #2
ezra-g commentedThis patch adds a configurable option to hide add/remove links from administrators. If you're not familiar with appling/testing patches, please let me know. Thanks!
Comment #3
satcom74 commentedI applied the patch and it works as far as not showing Add to and Remove from links for every user. So far every thing seems to be working as far as users adding to and removing from the queue. I did notice that on the admin login only, when admin goes and clicks the Node Queue Icon or link he gets the following error.
* warning: array_keys() [function.array-keys]: The first argument should be an array in /var/www/drupal/modules/nodequeue/nodequeue.module on line 2036.
* warning: implode() [function.implode]: Bad arguments. in /var/www/drupal/modules/nodequeue/nodequeue.module on line 2036.
* 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 nid = 47 GROUP BY sqid' at line 1 query: SELECT sqid, MIN(position) AS position FROM nodequeue_nodes WHERE sqid IN () AND nid = 47 GROUP BY sqid in /var/www/drupal/includes/database.mysql.inc on line 172.
* warning: Invalid argument supplied for foreach() in /var/www/drupal/modules/nodequeue/nodequeue.module on line 408.
This isn't urgent for me in that in my case admin will not be administering these user smartnodes. But, if that is breaking other nodequeues like for other admin-administered content, I could see where that would be a problem.
I'm attaching the following images:
Admin logged in before patch clicking Node Queue icon that is with each teaser. (In my example it is labeled My Favorites)
Admin logged in after patch showing error.
Admin logged in looking at teasers showing that the Add to and Remove from icons are gone.
Comment #4
ezra-g commentedThanks for this review.
Do you by any chance have the dev version of smartqueue_og installed ;). That could be causing this error and in fact it's the only way I was able to reproduce it. It seems to be caused when one visits the nodequeue tab on a node that actually cannot belong to any queues, and therefore shouldn't have a tab.
If you clear the menu cache, does the nodequeue tab (and the error) disappear?
Comment #5
satcom74 commentedI'm not using the smartqueue_og module. I cleared the cache_menu table in mysql. Is that sufficient? I'm still getting the error.
Comment #6
ezra-g commentedOK, let's get to the bottom of this:
Could you please open up nodequeue.module and after line 2035, "
function nodequeue_set_subqueue_positions(&$subqueues, $nid) {"add the following snippet so that ithe first 3 lines of that function look like this:
[corrected for a typo]
or if you have devel.module installed and enabled:
Then, visit a page that generates one instance of those errors and paste the output here. Thanks!
Comment #7
ezra-g commentedIn the meantime, or if you're unable to do that in the near future, can you clarify a few things about what yous said,
Which permissions does that admin login have assigned to his role? Please list all nodequeue and smartqueue_users permissions.
Since I'm having trouble reproducing the error, you said "icon or link" -- Since nodequeue has no icon, do you mean either the add/remove links or the nodequeue tab?
Comment #8
ezra-g commentedActually, this error looks like the same one that you reported in #294167: Getting the following error when I actually add a node to queue. Could it be the same problem with your setup that you were experiencing there?
Comment #9
ezra-g commentedPatch no longer applies. Is re-rolled here for that reason, not to address the errors reported by satcom74.
Comment #10
ezra-g commentedCommitted to 5.x.
Comment #11
ezra-g commentedComment #12
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.