Timeline for Why don't we hack core?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 1, 2014 at 12:34 | comment | added | Toby Allen | A decent Source control system should be able to tell you what has changed and show all modifications to core. Searching for strings in a codebase should be standard part of your debugging toolkit in php. | |
| Jan 31, 2013 at 8:31 | comment | added | Pawel G | Looks good Chris. I'll definitely have a look. | |
| Jan 30, 2013 at 21:33 | comment | added | Chris Burgess | Bet you wish you'd heard about drupal.org/project/hacked earlier? | |
| Jan 30, 2013 at 17:19 | comment | added | Charlie Schliesser | This. If you inherit a site that was built on any given framework, and then discover that the framework was hacked and thus the documentation for that framework is potentially irrelevant, you're in a world of pain. (in addition to all of the other aforementioned reasons above...) | |
| Jan 30, 2013 at 16:59 | history | answered | Pawel G | CC BY-SA 3.0 |