Closed (fixed)
Project:
Rules Link
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Mar 2012 at 08:51 UTC
Updated:
12 Mar 2013 at 12:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
sepgil commentedWhen does this error occur?
Comment #2
kaizerking commentedI am using erecruiter install profile,it has got "job manage" view. This occured when i was clicking on one of the links manage jobs.
Comment #3
BenK commentedI'm getting the exact same error when using the latest -dev version. I'm displaying a Rules link in a view which is part of a Panel. The error occurred after I updated to the latest commits over the past couple of months.
Any ideas?
--Ben
Comment #4
BenK commentedHey everyone,
I've rolled back the latest git commits and have confirmed that the error seems to have been introduced during the following commit:
http://drupalcode.org/project/rules_link.git/commit/cf9cbae
This commit was intended to solve the following issue:
Issue #1401780 by fubhy: Allow custom link titles for the views links.
(http://drupal.org/node/1401780)
Any ideas about how to fix? I've rolled back to the commit right before this one and the error message goes away.
Thanks,
Ben
Comment #5
mitchell commentedNo patch yet to work on, but this is the right issue to fix the bug. If anyone has more info or can help track it down, that would be very nice.
Comment #6
haradhansharma commentedi m facing same problem also on beta7. And waiting for kind solutions.
Comment #7
sepgil commentedI can't replicate this issue, can anyone provide an example view.
Comment #8
wipeout_dude commentedSince the update to 7.x-1.0-Beta4 I am seeing a lot of these errors being logged..
Notice: Undefined index: rules_link_rewrite in views_handler_field_rules_link->render() (line 47 of /home/websites/platform/sites/all/modules/contrib/rules_link/rules_link.views.inc).
I have looked at the view and the can't see that the rules links are being rewritten..
As I say I didn't see this with beta3 so its something that's changed between beta3 and beta4..
Comment #9
wipeout_dude commentedWould there be any issues if I roll back to beta3?
Comment #10
sepgil commentedThere are some Improvements you would loose, but nothing major.
Anyway could any of you post an exported view, which produces such errors? I'd really like to fix issue, but as stated before, I haven't been able to reproduce it.
Comment #11
wipeout_dude commentedHere is a view that's producing the error.. Hope it helps..
Comment #12
tribsel commentedsame problem, rollback to beta3 fixed it
Comment #13
omissis commentedHere's a patch to at least get rid of the error message.
I am not sure what's the source of the problem yet, I'll see if I'll be able(and have time) to debug it to its roots.
Comment #14
omissis commentedRerolled patch since previous one's wasn't working properly.
Comment #15
sepgil commentedThx for the patch, I committed it.