Crashing, Fatal Errors, and Lag
Permalink
I am overseeing a small website project atwww.www.thehealingspaceonmain.com.... I have had no big problems but my client has been complaining about the system crashing and receiving fatal errors when logged in and making changes within Concrete5. Could there be a problem in the back-end? Or maybe some core files have been removed/changed?
Also, When not logged in and just visiting the site I noticed that it is pretty slow. There are not any bulky images or Flash (yet) to slow it down so I am a bit confused.
Thanks.
Also, When not logged in and just visiting the site I noticed that it is pretty slow. There are not any bulky images or Flash (yet) to slow it down so I am a bit confused.
Thanks.
first of all what is the debug level? dev or production? also is the sql local or on another server?
the debug level is set to Development because while I edit things I want to see specific errors if they arise. The site is still a work in progress (tweaking CSS and graphics).
The hosting and server is from Network Solutions and called 'mysqlv12'.
The hosting and server is from Network Solutions and called 'mysqlv12'.
make sure SQL query logging is off in concrete5
turn caching on in concrete5
turn caching on in concrete5
Thanks, I want back and found out that Concrete5 had been logging all queries and emails. I turned them off and confirmed that caching was on.
Thanks but its still a bit slow. I will be meeting with my client tomorrow to see exactly which errors she is receiving when she says it "CRASHES and gives me FATAL ERRORS"
Thanks but its still a bit slow. I will be meeting with my client tomorrow to see exactly which errors she is receiving when she says it "CRASHES and gives me FATAL ERRORS"
if that query logging was on you're going to want to clear out the huge table it was filling
yea i would do that
oh Frz in the svn you guys removed the database logging? why not just split it up into different types of queries?
oh Frz in the svn you guys removed the database logging? why not just split it up into different types of queries?
it was a silly feature. there are so many queries in every page load that by the time you even goto the reports to find what you were looking for you've flushed the query down several pages.. moreover mysql can do this on its own.
its gone because we hear the above constantly.
its gone because we hear the above constantly.
