ergophobe - 5:27 pm on Jun 11, 2012 (gmt 0)

I'm totally AGAINST modifying the modules

Agreed. Sometimes it can't be helped, but in that case I create a new module. Say my site is called My Site, I'll use an MS prefix as in "image_MS" for a module name. I have only done this once or twice and only with not regularly maintained third-party modules. I would not do it with anything in core.

Most often, I can use the hook system and get in there and modify forms or whatever. Most sites I build end up with a module called "tweaks_XX" (i.e. tweaks_MS in the My Site case).

I then use this module whenever I need to just hook in and make a small change in behavior. This keeps everything working through upgrades as long as the API doesn't change (which should be a major version change only, and even then perhaps not).

I checked the theme

And you're using only one theme for both public and admin?