By Sameo on

Hello.

I'm pretty new at Drupal and just recently found core files changing (aka hacking) as an awesome thing. It's so much quicker and easier to do basically everything. I got hooked on this and before everyone will start bashing me that I shouldn't do it...
1. I have enough experience in PHP & MySQL, so I really know what I'm doing.
2. Making a website to myself, so I remember where and what I changed before.
3. Don't get me wrong, I'm not rewriting a huge parts of code, just tweaking there and here.

So what could go wrong?

// Sameo

⋅ Categories: Drupal 7.x

Comments

gaslamp’s picture

gaslamp commented
  • Unintended consequences when using contributed modules. Harder to diagnose issues because your core will be different than all others.
  • Updates to Drupal core may undo what you did, and a chain reaction on any other modules you've used or created
Sameo’s picture

Sameo commented

Thanks, Thai Yin.

Modules don't bother me because I don't use them, but the second thing is pretty scary to me. I could take a look to overrides again, however is it even possible to do everything with overrides that you can do by changing core files?

yasir farooqui’s picture

yasir farooqui commented

Drupal is really good in allowing you to make overrides for almost everything, so drupal does not recommend that you change the core. I will agree with earlier reply to this post, because if you will change the core then other modules will not get the expected results from drupal core functionality and definitely updating the drupal core will clear all your changes.