Here is a new defect I just encountered with beta12.
I was testing the Workflow module, that I will need on my production site, and when returning to my Views-generated front page I received:
user warning: Unknown column 'n.nid' in 'on clause' query: SELECT pid FROM url_alias INNER JOIN node_access na ON na.nid = n.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 1 AND na.realm = 'workflow_access') OR (na.gid = 0 AND na.realm = 'workflow_access_owner'))) AND ( dst = "<front>") in /var/www/sites/all/modules/pathologic/pathologic.module on line 163.
Not quite sure what the net result of that is. Using Drupal 6.4, Workflow-6.x-1.0-rc1.
Thanks again!
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | pathologic.module.zip | 2.8 KB | Garrett Albright |
| #2 | pathologic.module | 2.91 KB | Garrett Albright |
Comments
Comment #1
Garrett Albright commentedWow, Workflow sure is mangling that query…
I think I know how to work around it, though. Thanks again for spotting another problem; I'll try to get an update hammered out on my lunch hour.
Comment #2
Garrett Albright commentedrismondo, please replace your pathologic.module file with the attached and let me know if it fixes the problem. As I've never really used Workflow and don't have it installed anywhere, I'm not really in a good position to test it myself.
Thanks.
Comment #3
rismondo commentedI wish I could: I tried to recreate the setup that generated the error above, but the error (which previously showed up several times) doesn't appear any longer, even with beta12. I'll try some more and post a reply if I manage to recreate the exact scenario and test your patch...
Comment #4
Garrett Albright commentedOdd. Well, thanks for trying, anyway.
Comment #5
rismondo commentedThe error showed up again, but it's not very predictable. I replaced pathologic.module with your latest patched version, and so far all seems well.
Comment #6
Garrett Albright commentedThe attached version is tweaked a little more so that it uses a Drupal function instead of making a database call itself. That way, if database problems occur while using Pathologic, it's somebody else's problem. Please give it a try as well.
Comment #7
rismondo commentedSeems ok, I'm not getting any messages (for now).
Comment #8
Garrett Albright commentedOkay, I've just released a new D6 release which implements this fix. So I'm gonna mark this issue as fixed.
Comment #9
rismondo commentedExcellent, thank you for looking into this issue, and the prompt fix!
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.