Ask your question about FuelPHP in the appropriate forum, or help others by answering their questions.
What’s the best way to debug a website?
We have a website that’s been susceptible to a few code conflicts in the past. That’s alright, because we have regular backups in place. However, we do debugging, but I feel we can do better with the debugging aspect. Ideally, we outsource it to another company.
We went through this guide about how to prevent
websites from crashing
, and have potentially covered all major aspects.
What else can we do?
There are a million and one reasons why something might crash.
It could be logic errors, it could be sloppy programming, it could be timeouts (php runtime, webserver), and it could be webserver related (process timeouts, out of memory, incorrect configuration).
Without details of these conflicrs or crashes, its guesswork.
Like with all other things, you need people with the correct experience to address such issues.
Add a Comment
It looks like you're new here. If you want to get involved, click one of these buttons!
Apply for Membership
↳ Job Board
↳ Installation & Setup
↳ Tips and Tutorials
↳ Code share
In this Discussion