Closed (fixed)
Project:
Views (for Drupal 7)
Version:
6.x-3.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jun 2010 at 20:17 UTC
Updated:
28 Sep 2011 at 19:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
dawehnerwhy are we not iterating over $views_page->arguments?
the name of an argument is to specific, we should have a look at the table/field of the argument.
Powered by Dreditor.
Comment #2
marcp commentedGreat point! Here's the new patch.
Comment #3
bonobo commentedAny movement/word on this? This is working great for us in a few different places.
Comment #4
dawehnerCan you explain why you do this?
Default argument's are only used when Action to take if argument is not present: which is not the case here. I don't see the point why it's needed currently.
Comment #5
bonobo commentedThe default behavior doesn't work for blocks when using any path that isn't the standard user/uid path -
So, if you create a view with a page display that lists all posts by a user; this page can be accessed at (for example) foouserposts/uid - for the page display, the argument will filter by uid.
However, if at foouserposts/uid you wanted to display an "About the Author" block, the same argument won't work - so, while it works for a page display, it doesn't work for a block display.
This patch fixes that.
Comment #6
bonobo commentedAny word here?
Comment #7
dawehner@bonobo
Please be so fair and don't dump issues. There are 160 patches in the views issue queue which needs review.
I would perhaps check also for table == 'user'
Comment #8
bonobo commentedDefinitely not "dumping" the issue, and definitely not demanding anything in any way, shape, or form.
Saying "I've been busy" is a completely acceptable response, and I'm fine with that. It's been a month since there was any movement on this - we found what appears to be a bug, we supplied a patch, and we have tested that patch in a few different contexts. When you asked questions, we responded, and in the case of #2, above, rolled a new patch.
All I was doing was asking if there had been any movement on this - "no" is a perfectly acceptable answer.
While we'd like to get this rolled into views, we're perfectly capable of maintaining it on our own as well.
If there is anything we can do, please let us know. If you're not going to review the patch, that's fine too.
Comment #9
dawehnerYou know the views issue queue is kind of bussy. A month is nothing here: See http://drupal.org/project/issues/views?text=&status=8&priorities=All&cat...
If there would be movement someone would have posted a comment. All this unnecessary pushing of issues is annoying.
Comment #10
clashar commentedsubscribe,
not sure but I think I have similar problem, I use argument
"User: Uid"
- "provide default arg"
- "User ID from URL"
but devel shows "Query: No query was run"
Everything is ok, if I use for example "User ID from logged in user", but that's not what I need
Comment #11
clashar commentedby the way, I use 6.3 dev. and when I check - "User ID from URL", new box appears "Default argument: ", maybe I don't understand well but it is confusing for me, there will be always user id from URL why then provide box "Default argument: "
Comment #12
bonobo commented@clashar - this issue is for the 6.x-2 branch.
I'm not entirely sure what issue you are describing but it should probably be opened in a separate issue.
Also, if you can include some specific steps to replicate the issue, it will help get more focused feedback.
For example, info about your drupal version, your OS and PHP version, and any other installed modules will help.
Comment #13
clashar commentedI applied patch from #2 manually to 3.x.dev but it didn't help.
Sorry for so many postings, seems it's not the same issue.
Comment #14
bonobo commented@clashar - the patch in this issue is against Views 2.
You are using Views 3, so the patch won't apply.
I'm not entirely sure that the issue you are reporting is a bug, or is related to a config error, but in any case you should open a separate ticket for it.
In the absence of a patch to solve a bug, any screenshots that show the issue, along with more info about your site setup, will help you get more focused feedback.
Comment #15
clashar commentedbonobo, thanks for quick reply.
Often I am not yet sure if I should create a new issue, for this case I will open a new issue providing screenshots.
Comment #16
merlinofchaos commentedMy comments here http://drupal.org/node/840668#comment-3841378 apply here as well. IN short: Need a 6.x-3.x patch to merit consideration.
Comment #17
marcp commentedAttached is a patch for 6.x-3.x.
You can test it out quickly with the following view, which provides a page accessible at userposts/% and a block that should show up on any page where uid is an argument. Before applying the patch, the block will not appear when viewing userposts/%.
Comment #18
merlinofchaos commentedCommitted to all branches.
Comment #19
chuckbar77 commentedI upgraded from Views-6.x-2.12 to Views-6.x-2.x-dev and all my views pages that had path as user/% with argument went blank. Can this be the reason?
Comment #20
marcp commented@chuckybar77 - Try starting over with your upgrade, but remove the 4 lines of code provided by the patch and see if that fixes your problem.
Looks like you need to run update.php after upgrading from 6.x-2.12 to 6.x-2.x-dev also, so you might try that first.
Comment #21
merlinofchaos commentedIf your pages are blank, check the php error log.
Comment #22
Letharion commentedIssue was fixed, and then incorrectly re-opened.