Closed (duplicate)
Project:
Link
Version:
6.x-2.9
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
20 Feb 2010 at 17:51 UTC
Updated:
24 Aug 2012 at 14:41 UTC
Jump to comment: Most recent file
Hi there,
I needed to filter nodes with link-fields by their given URL, but there it seems there is no argument handler for that, yet. Since raw URLs are not suitable for being arguments (slashes in the URL prevent Views to interprete the URL as ONE argument), they have to be urlencoded. I've attached a patch here which adds the appropriate Views handler where the URL argument gets decoded before processed. There is also a validator plugin which can be configured to check against internal/external/mailto/front URLs.
Please review
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 720380_2.patch | 7.14 KB | sammys |
| #1 | link.patch | 5.72 KB | japanitrat |
| link.patch | 5.82 KB | japanitrat |
Comments
Comment #1
japanitrat commentederr, wrong patch. new one attached here.
Comment #2
sammys commentedHere is a patch to additionally add a filter to restrict nodes displayed to those matching the current URL being browsed by the user. This is handy for using a link field to store internal links that are used to determine when nodes are displayed in a view (e.g content pane view).
Probably would be good to add an operator to it allowing a 'not match' situation but I don't have the time to add this in right now.
Comment #3
broncomania commentedThis is exactly what I am looking for, but your patches here break my current views. I use views 3 alpha 4 and link 2.9. Are these patches incompatible with existing views or is this maybe a bug in your patches or in views 3?
Comment #4
dqdPlease post here for all issue relating to views integration, which needs work and reports from all users as much as possible. (all versions)
#1325112: Integration of Link module and Views
Comment #5
NaX commentedThanks a lot guys, this is exactly what I was looking for. FYI: views 2.16