Closed (cannot reproduce)
Project:
Relation
Version:
7.x-1.x-dev
Component:
API
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Sep 2011 at 03:46 UTC
Updated:
17 Mar 2013 at 06:57 UTC
Jump to comment: Most recent file
Comments
Comment #1
Pohjolander commentedWell, I had some sleep, and returned to the problem, successfully getting rid of the WSOD. I don't know if it was that I specifically gave the administrator permission to interact with my new type of node, or that I disabled the Relation Dummy Field in the Module Administration and was able to enter my first relations (the more likely scenario in my mind), but either way, I can now get started. Many thanks for this module.
Comment #2
rafamd commentedSo, shall we close this issue ?
Comment #3
phayes commentedI am getting this error (moved to line 742 ) when deleting a taxonomy term. I'll do a debug backtrace and report back.
Comment #4
rafamd commentedmake sure to get some sleep also :)
Comment #5
phayes commentedSo the problem ended up being that using the __construct method was causing the PHP autoloader to get confused and not properly include the relation.database.inc file. When using autoloaders we should be using the class-name as the constructor method. The attached patch fixes this.
Comment #6
phayes commentedAlso,
Note that the above patch only fixes the issue with RelationQuery - this bug may be lurking in other classes the use autoloading and a __construct method
Comment #7
mikran commentedI'm clearing the needs review tickets. Is this still an issue with latest version? I don't think the fix is correct in any case so if the problem still persists can you provide exact steps to reproduce it?
Comment #8
mikran commented