Before I saw this module I did a function and used with php format in header. Not the best way :p
Youre solution is supercool. I made this modification becouse I wanted to use this on header area for creating administrative links and restrict access per role. This is also tested with and worked for me.
Sorry I couldnt make patch.. Dont know why it didnt work for me.
This package doesnt work I deleted one row my mistake :S Ill make new one.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | views_linkarea.tar_.gz | 2.13 KB | kaido.toomingas |
| #2 | add_role_based_access_multiple_1445560-5622656.patch | 2.68 KB | kaido.toomingas |
| #1 | add_role_based_access-1445560.patch | 2.41 KB | kaido.toomingas |
| #1 | views_linkarea.tar_.gz | 2.12 KB | kaido.toomingas |
| views_linkarea.tar_.gz | 2.15 KB | kaido.toomingas |
Comments
Comment #0.0
kaido.toomingas commented.
Comment #0.1
kaido.toomingas commented.
Comment #1
kaido.toomingas commentedAdded changes witch I described before + added changed wich has been submitted http://drupal.org/files/issues/996974-viewslinkarea-query-class-array.patch changes becouse I had the same problem again.
Comment #2
kaido.toomingas commentedMutliple access role patch and version for download.
Comment #3
jantimon commentedWouldn't it be cleaner to use the role machine names instead of the ids?
This would help people who export views with features.
Comment #4
Bevan commentedThis related issue has a simpler patch that handles many of the use cases this patch also handles: #1451266: Links should not render if user does not have access
Comment #5
kaido.toomingas commentedI do agree!
Comment #6
geek-merlinaccess should *never* be done via roles, the proper way is to use permissions.
see: #1445494: block.module maintains visibility via roles thereby establishing a hidden permission system
so marking as dup of #1451266: Links should not render if user does not have access
Comment #6.0
geek-merlinReview