Posted by Hydra on April 11, 2011 at 10:12pm
8 followers
| Project: | Advanced Forum |
| Version: | 6.x-2.x-dev |
| Component: | Views |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
When I enable the advanced forum modul, I receive this Message a dozen times.
Notice: Undefined property: view::$row_index in views_handler_field->get_render_tokens() (line 1198 of /var/kunden/webs/bcweb/spiderkingz/d7/sites/all/modules/views/handlers/views_handler_field.inc).
I'm using the actual 7.x-2.0-alpha1 of advanced_forum and the 7.x-3.x-dev views version.
Comments
#1
Errors/warnings are actual problems. Notices should be fixed, but it's often it's just a bit like a codestyle issue.
See http://api.drupal.org/api/drupal/includes--bootstrap.inc/function/watchdog and http://www.ietf.org/rfc/rfc3164.txt
So update priority.
In d6 displaying notices would kill you!
This code now works more like the default table preprocess function.
You could use this in 6.x-1.x as well, because this is a function which is in views since a certain version.
#2
patch from #1 dereine works for me! Thx
#3
Changing status
#4
#5
-
#6
#7
Ok, ok. Committed to 7.x-dev.
Thanks for the patch dereine.
#8
@troky
Hydra is still learning drupal.org :(
#9
Hydra = dereine's padavan :P
#10
You guys amaze me and we stand (or sit) indebted. I posted elsewhere on this as follows:
Troky then directed me to this thread. Thanks! However, I'm a total newb and don't know what to do to fix the error.
I'm in D7 and have installed Advanced Forum 7.2x alpha1, CMA, ctools 7.x-1.x-dev, ACL-7.x-1.0-beta2
Maybe I should have avoided a dev version of ctools? Your help is always appreciated!
#11
Advanced Forum 7.2x alpha1You should better use the dev version of advanced forum, because it's fixed there.
#12
Remove the most useless issue tag ever seen.
#13
Thanks dereine.
I tested the patch with views 6.x-2.12 and the render_fields method works fine.
Committed to the Advanced Forum 6.x-2.x branch (I had trouble attributing you as the patch author in git, sorry).
#14
Thanks, the patch in #1 helped me on 7.x-2.0-alpha1.
#15
oops - realised I should have been setting issues to "fixed" rather than "closed (fixed)"
#16
Well, it is fixed and ported and there is no reason not to close it :)
#17
Automatically closed -- issue fixed for 2 weeks with no activity.