asphaltjesus wrote
| Will Strohl wrote
Well, the key is obviously to recreate the problem, and then check the event log and event viewer.
|
And how, exactly, would he do that? He can't go back in time. Which is just one reason why dnn is so fragile.
If you're not going to be positive and helpful, please do not post to the forums. Being negative really makes it so much more difficult for people to get and give help - which is ironically the very thing you're complaining about.
You can indeed look at past errors in the Event Log of Windows, and the Event Viewer in DNN. This is why they exist.
asphaltjesus wrote
| Will Strohl wrote
Those are really the only 2 places to look for errors,
|
Which makes my point about the lack of tools. In the very complicated stack on which DNN sits, there are only 2 places to look for errors. Two! And those two aren't terribly verbose and/or the messages aren't well documented.
Lack of tools? Exactly how many places should an application have to look for errors??? Honestly, I wish that there was only one, not 2.
The messages are generally not even DNN's. Since you're looking to blame people, you can blame Microsoft for the text in the exceptions. Besides, the real information is in the stack trace - not in the error message itself.
Do you have a better suggestion that will help the poster of this thread? Please post it here.
kai wrote
Here we are. My site is back again and running with the 9 days old backup (files and db). And again, i changed nothing on my server.
And in the backup is the module i mentioned allready included. Therefore i don't think that the module is the guilty one.
So, any clues?
Were you able to duplicate the site outage on your local system? Was it a direct duplicate of the live site (files & db)? If not, I know it's a pain in the neck, but pull down a duplicate copy of your 9 day old back up and have that set-up on your development system.
What version of DNN and what module/version is having this problem?
Are any of your images corrupted in any way? I have experienced similar issues when an image was not saved correctly, but it only brought down the site when the referencing page was hit.