Closed (duplicate)
Project:
Drupal core
Version:
7.x-dev
Component:
trigger.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 Feb 2009 at 16:29 UTC
Updated:
10 Jan 2011 at 11:51 UTC
Jump to comment: Most recent file
Comments
Comment #2
antgiant commentedComment #4
antgiant commentedComment #6
antgiant commentedSpending more time convincing test bed it's validly formatted than I did fixing the bug.
Comment #8
antgiant commentedI think the manual node override is causing problems.
Comment #9
antgiant commentedApparently, I forgot to attach.
Comment #10
antgiant commentedSince the original design may have been attempting to prevent namespace collisions. Here is a new patch that requires the "hook being described" to begin with the module name.
Comment #12
antgiant commentedre-rolling to account for #383066: hook_nodeapi_X => hook_node_X
Comment #14
antgiant commentedI think the auto tester had a bad day.
P.S. Is there anyway to get notification of testing failure?
Comment #16
antgiant commentedI think the auto tester had another bad day.
Apparently nobody wants this fixed?
Comment #18
antgiant commentedRe-rolling to account for #353069: Make drupal_get_form to return unrendered forms.
Comment #20
antgiant commentedUndoing namespace restriction from #10 as it appears to be crashing cron. Perhaps related to #246096: Cron triggers are not executed.
Comment #22
antgiant commentedI suppose I deserve that for trying to edit the patch directly.
Comment #24
antgiant commentedMissed a line in my namespace removal patch.
Comment #26
antgiant commentedIt seemed like a good idea at the time to check that. Sigh.
Comment #28
antgiant commentedI believe that #324183: Better Access Control in Custom Triggers is the root cause of this problem.
Comment #29
gnassar commentedSince now #324183: Better Access Control in Custom Triggers is effectively a WONTFIX for 7.x and will only be dealt with in 8.x, should this issue be reopened?