Closed (fixed)
Project:
Ooyala
Version:
7.x-2.0-beta6
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Nov 2011 at 02:27 UTC
Updated:
23 Jan 2014 at 03:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
arithmetric commentedAttached is a patch to remove the problem code.
Comment #2
jyee commentedI didn't find this patch until just now, but I had made the exact same changes manually and they removed the warnings.
Comment #3
deviantintegral commentedPatch looks great to me. Committed to 7.x-1.x.
Comment #5
Media Crumb commented*whoops*
Comment #6
Media Crumb commentedI'm seeing this same issue under the Ooyala Channels module. Anyone else have this problem and/or know how to fix it?
Comment #7
Media Crumb commentedFixed. I'll add a patch when I get home. Sorry for reopening.
Comment #8
quicksketch@MediaCrumb: Could you post your patch? Does this affect the current 2.x versions?
Comment #9
quicksketchI found this call-by-reference in the 7.x-2.x branch of Ooyala project in the Ooyala Channels module. I didn't see any other call-by-references, so hopefully this resolves the instance that's causing trouble.
Committed to the 7.x-2.x branch. I couldn't find issues in the 6.x-2.x branch.
Comment #10
Media Crumb commentedThat was the same patch I had quick. So sorry I forgot to post it. Been using it since November with no issues.
Comment #11
quicksketchThanks @MediaCrumb for the confirmation. :)