Feature Request #1844
Enabling hooks in groups of files and per module patch.
| Status: | Closed | Start date: | 07/16/2009 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: |  Chris Bandy |
% Done: | 0% |
|
| Category: | Core | |||
| Target version: | 2.4 | |||
| Resolution: | fixed | Points: |
Description
Hi!
First: Thank you all for this nice framework, I code couchsurfing.com and we are migrating our code to kohana :)
As our application is very big, migrating is a long process, and in our first migration step, we are forced to use many hooks from the original app, and then as we properly port, we disable them, we have many modules, and a single enable all does not make our life simple. we've tried to leave the system code untouched, but on this one we solved by having hooks that are enabled by simply existing on a hooks/enabled folder, then hooks can be enabled an disabled easily per application and per module.
The patch is very simple. and well be happy to have it included on your next releases so we can keep the kohana system folder intact.
Related issues
History
Updated by Jeremy Bush almost 4 years ago
- Category set to Core
- Priority changed from Normal to Low
- Target version set to 2.4
Updated by Jeremy Bush almost 4 years ago
- Status changed from New to Review
Updated by Ben Rogers almost 4 years ago
couldn't this also be solved by renaming the extension to something other than what is defined by EXT? this could be resolved by just fixing #1761
Updated by Jeremy Bush over 3 years ago
- Status changed from Review to Assigned
- Assignee set to Chris Bandy
- Priority changed from Low to Urgent
Updated by Chris Bandy over 3 years ago
- Status changed from Assigned to Closed
- Resolution set to fixed
#1761 is fixed, so as Ben suggested above, you can disable hooks by changing their file extension from EXT.