headers already sent + other error messages

[Lurttinen]

Well, errors

Headers already sent, corrupting a table, detect if user has forced incorrect url settings for cookies, etc...
Can we detect an error and try automated repairs for it?

For headers, parse through files and see if there is something that is not supposed to be. Corrupt / REPAIR and cookies check what the domain really is and not what the user thinks it is.

Something like that.
Fix (some) errors automagically.

[ToonArmy]

What I'd like to see is links presented for solutions to error messages.

[Lurttinen]

I believe our Support Team could narrow top ~10 common errors with solutions in phpBB3.

[EXreaction]

Check out some of the stuff we have setup to run automatically in the STK (repairing the styles and repairing the config.php file).

[jwxie]

What I'd like to see is links presented for solutions to error messages.

I think you are referring to those Help files. I think it would be nice, espeically link to a wiki (but I hate connecting to Internet, well hahah).

[ToonArmy]

What I'd like to see is links presented for solutions to error messages.

I think you are referring to those Help files. I think it would be nice, espeically link to a wiki (but I hate connecting to Internet, well hahah).

Huh?

[bolverk]

I have to agree with ToonArmy, I would rather see a robust ACP inline help or mini-FAQ available to the board admin rather than attempt to develop the application with enough of a level of AI to replace the experience and skill of a human being. If there was such a thing as a 1:1 ratio of common errors to root causes it might be possible however the very nature of many errors as having multiple potential root causes makes *automagically* very unlikely to be successful.

[jwxie]

What I'd like to see is links presented for solutions to error messages.

I think you are referring to those Help files. I think it would be nice, espeically link to a wiki (but I hate connecting to Internet, well hahah).

Huh?

LOL You said you want to see links to error message - just like those help files. If your Live MSN is down, it usually tells you an error code - as soon as you click Yes or some button, it will direct you to a webpage where it explains what that error means and how to resolve it.

Our wiki should be use for this purpose too - as a help file.

[Desdenova]

Well, errors

Headers already sent, corrupting a table, detect if user has forced incorrect url settings for cookies, etc...
Can we detect an error and try automated repairs for it?

For headers, parse through files and see if there is something that is not supposed to be. Corrupt / REPAIR and cookies check what the domain really is and not what the user thinks it is.

Something like that.
Fix (some) errors automagically.

While that is a nice idea, it is not something that should be done automatically due to the amount of server load it could generate. I'd rather see something like an ACP module for running diagnostics, you could toss in several checks within the module, have it perform a series of tests, and notify the user of the results at the end.

[ToonArmy]

While that is a nice idea, it is not something that should be done automatically due to the amount of server load it could generate. I'd rather see something like an ACP module for running diagnostics, you could toss in several checks within the module, have it perform a series of tests, and notify the user of the results at the end.

Agreed especially as some repair operations could potentially do more harm.

LOL You said you want to see links to error message - just like those help files. If your Live MSN is down, it usually tells you an error code - as soon as you click Yes or some button, it will direct you to a webpage where it explains what that error means and how to resolve it.

Our wiki should be use for this purpose too - as a help file.

We've got the same idea here, just explaining/understanding it differently.

I have to agree with ToonArmy, I would rather see a robust ACP inline help or mini-FAQ available to the board admin rather than attempt to develop the application with enough of a level of AI to replace the experience and skill of a human being. If there was such a thing as a 1:1 ratio of common errors to root causes it might be possible however the very nature of many errors as having multiple potential root causes makes *automagically* very unlikely to be successful.

I was thinking taking the environment dependant strings out of PHP error message for example and using the remainder to look up a human friendly description of the problem, or some such. For example the headers not sent error message on line 1 of a file, you'd be able to read (somehow) that you've white space at the beginning of whichever file is causing the problem.