Option D is the way to go, my friends. Enabling debug logging in the Admin interface is like having a superpower - you can see all the secrets of the production system without having to get your hands dirty!
Ah, the joys of debugging production issues! Option A sounds tempting, but enabling developer mode in production is a bit like putting a bandaid on a broken leg. It's a quick fix, but it's not really a long-term solution.
I'm leaning towards option B. Writing a custom logger that writes the debug information to a separate log file sounds like a more robust solution, especially if you need to keep the debug logging enabled for a longer period of time.
Option C seems like a good idea, but I'm not sure if it's the best solution. Enabling debug logging in the config file and then deploying it to Production could be risky, especially if you forget to turn it off later.
C) Option C seems like a good idea, but I'm not sure if it's the best solution. Enabling debug logging in the config file and then deploying it to Production could be risky, especially if you forget to turn it off later.
I think option D is the way to go. Enabling debug logging in the Admin interface is the easiest and most straightforward way to get the required information without having to mess with the code or deployment process.
Precious
3 months agoJulieta
3 months agoTimmy
2 months agoCharlette
2 months agoHelga
2 months agoWhitley
3 months agoBarrett
2 months agoNu
2 months agoLaura
2 months agoVallie
3 months agoAriel
3 months agoLilli
2 months agoDoyle
2 months agoEladia
3 months agoNarcisa
4 months agoMargery
4 months agoNarcisa
4 months agoDelfina
4 months agoSage
2 months agoElke
2 months agoTayna
2 months agoJacquelyne
3 months ago