#Errorhandler or ErrorLogger? As far as I can see, you wrote an ErrorLogger, not an error handler. You are not registering an error handler. The only thing these classes seem to do is Logging and giving access to the errors - with the option to truncate them.

So in fact, you created a Logger that can delete all errors (now why would you do that?), so call it a Logger.

The good peeps over at psr - standards have create a really nice interface for a Logger. Implementing that interface would be a big plus since you could easily change it with a complete different logging engine if needed.

##Code "errors" You are using namespaces, that's good. But the location of your files is just illogical. Stick to psr-4 or psr-1. Standards exist because they are proved to be good. And instead of using all those requires. Use an auto loader instead. Write a custom one or use a complete solution like Symfony loader or even composer.

In your database you are only saving the error, nothing more. Some extra information would be useful. Like when did it occur for instance.

If every method starts with the same word and if that word can also be found in the class name, you probably don't need it. Writing:

$errorHandler = new ErrorHandlerController;
$errorHandler->handleErrorLogging($error);

It feels weird. You say that it should handle logging errors. But you need an error to handle error logging. But the only thing it does is log an error. So what does the ErrorHandlerController do? It passes everything to the ErrorMapper. So why not use the error mapper?

$errorHandler = new ErrorHandlerDatabaseMapper;
$errorHandler->log($error);

Way more readable.

Then your method name: returnErrorList. Return to where? The client? What you are doing is 'getting'. So getErrors or getErrorsAsList. But what is a list? It's just an array

The same goes for truncateErrorList. What is the List keyword doing there? And why is it returning something? This means that every piece of code that truncates all the errors needs to check for success, so throw an Exception.

When using the local error mapper problems will arise if the error message contains ';'.

And as a last remark. If you are creating an ErrorHandler and after you have created your error handler you write:

if($configuration['errors']['enable_error_logs'] == 1) {
    if($database->connect_errno) {
        echo $database->connect_error;
    }
}

Your class failed. It is not handling errors.

Disclaimer: everything I wrote is here to help you; If you feel offended, I apologise. This is not what I intended.

Errorhandler or ErrorLogger?

As far as I can see, you wrote an ErrorLogger, not an error handler. You are not registering an error handler. The only thing these classes seem to do is Logging and giving access to the errors - with the option to truncate them.

So in fact, you created a Logger that can delete all errors (now why would you do that?), so call it a Logger.

The good peeps over at psr - standards have create a really nice interface for a Logger. Implementing that interface would be a big plus since you could easily change it with a complete different logging engine if needed.

Code "errors"

You are using namespaces, that's good. But the location of your files is just illogical. Stick to psr-4 or psr-1. Standards exist because they are proved to be good. And instead of using all those requires. Use an auto loader instead. Write a custom one or use a complete solution like Symfony loader or even composer.

In your database you are only saving the error, nothing more. Some extra information would be useful. Like when did it occur for instance.

If every method starts with the same word and if that word can also be found in the class name, you probably don't need it. Writing:

$errorHandler = new ErrorHandlerController;
$errorHandler->handleErrorLogging($error);

It feels weird. You say that it should handle logging errors. But you need an error to handle error logging. But the only thing it does is log an error. So what does the ErrorHandlerController do? It passes everything to the ErrorMapper. So why not use the error mapper?

$errorHandler = new ErrorHandlerDatabaseMapper;
$errorHandler->log($error);

Way more readable.

Then your method name: returnErrorList. Return to where? The client? What you are doing is 'getting'. So getErrors or getErrorsAsList. But what is a list? It's just an array

The same goes for truncateErrorList. What is the List keyword doing there? And why is it returning something? This means that every piece of code that truncates all the errors needs to check for success, so throw an Exception.

When using the local error mapper problems will arise if the error message contains ';'.

And as a last remark. If you are creating an ErrorHandler and after you have created your error handler you write:

if($configuration['errors']['enable_error_logs'] == 1) {
    if($database->connect_errno) {
        echo $database->connect_error;
    }
}

Your class failed. It is not handling errors.

Disclaimer: everything I wrote is here to help you; If you feel offended, I apologise. This is not what I intended.

#Errorhandler or ErrorLogger? As far as I can see, you wrote an ErrorLogger, not an error handler. You are not [registering an error handler][1]. The only thing these classes seem to do is Logging and giving access to the errors - with the option to truncate them.

So in fact, you created a Logger that can delete all errors (now why would you do that?). So call it a Logger ;)

The good peeps over at psr - standards have create a really nice [interface][2] for a Logger. Implementing that interface would be a big plus since you could easily change it with a complete different logging engine if needed.

##Code "errors" You are using namespaces, that's good. But the location of your files is just illogical. Stick to [psr-4][3] or [psr-1][4]. Standards exist because they are proved to be good. And instead of using all those requires. Use an auto loader instead. Write a custom one or use a complete solution like [Symfony loader][5] or even [composer][6].

If every method starts with the same word and if that word can also be found in the class name, you probably don't need it. Writing:

Way more readable ;)

The same goes for truncateErrorList. What is the List keyword doing there? And why is it returning something? This means that every piece of code that truncates all the errors needs to check for success. Throw an Exception ;)

Your class failed. It is not handling errors ;)

Disclaimer: everything I wrote is here to help you; If you feel offended, I apologise. This is not what I intended. [1]: http://php.net/manual/en/function.set-error-handler.php [2]: http://www.php-fig.org/psr/psr-3/ [3]: http://www.php-fig.org/psr/psr-4/ [4]: http://www.php-fig.org/psr/psr-1/ [5]: http://symfony.com/doc/2.0/components/class_loader.html [6]: https://getcomposer.org/

#Errorhandler or ErrorLogger? As far as I can see, you wrote an ErrorLogger, not an error handler. You are not registering an error handler. The only thing these classes seem to do is Logging and giving access to the errors - with the option to truncate them.

So in fact, you created a Logger that can delete all errors (now why would you do that?), so call it a Logger.

The good peeps over at psr - standards have create a really nice interface for a Logger. Implementing that interface would be a big plus since you could easily change it with a complete different logging engine if needed.

##Code "errors" You are using namespaces, that's good. But the location of your files is just illogical. Stick to psr-4 or psr-1. Standards exist because they are proved to be good. And instead of using all those requires. Use an auto loader instead. Write a custom one or use a complete solution like Symfony loader or even composer.

If every method starts with the same word and if that word can also be found in the class name, you probably don't need it. Writing:

Way more readable.

The same goes for truncateErrorList. What is the List keyword doing there? And why is it returning something? This means that every piece of code that truncates all the errors needs to check for success, so throw an Exception.

Your class failed. It is not handling errors.

Disclaimer: everything I wrote is here to help you; If you feel offended, I apologise. This is not what I intended.

#Errorhandler or ErrorLogger? As far as I can see, you wrote an ErrorLogger, not an error handler. You are not [registering an error handler][1]. The only thing these classes seem to do is Logging and giving access to the errors - with the option to truncate them.

So in fact, you created a Logger that can delete all errors (now why would you do that?). So call it a Logger ;)

The good peeps over at psr - standards have create a really nice [interface][2] for a Logger. Implementing that interface would be a big plus since you could easily change it with a complete different logging engine if needed.

##Code "errors" You are using namespaces, thats good. But the location of your files is just unlogic. Stick to [psr-4][3] or [psr-1][4]. Standards exist because they are proved to be good. And instead of using all those requires. Use an autoloader instead. Write a custom one or use a complete solution like [Symfony loader][5] or even [composer][6].

In your database you are only saving the error. Nothing more. Some extra information would be usefull. When did it occur for instance.

If every method starts with the same word. And if that word can als be found n the class name. You probavly don't need it. Writing

$errorHandler = new ErrorHandlerController;
$errorHandler->handleErrorLogging($error);

IT feels weird. You say that it should handle logging errors. But you need an error to handle error logging. But the inly thing it does is log an error. Always. So what does the ErrorHandlerController do? IT passes everything to the ErrorMapper. So why not use the errorMapper?

$errorHandler = new ErrorHandlerDatabaseMapper;
$errorHandler->log($error);

Way more readable ;)

Then your method name: returnErrorList. Return to where? The client? What you are doing is 'getting'. So getErrors or getErrorsAsList. But what is a list? it's just an array

The same goes for truncateErrorList. What is the List keyword doing there? And why is it returning something? This means that every piece of code that truncates all the errors needs to check for success. Throw an Exception ;)

When using the local error mapper probels will arise if the error message contains ';'.

And as a last remark. If you are creating an ErrorHandler. and after you have created your errorhandler you write:

if($configuration['errors']['enable_error_logs'] == 1) {
    if($database->connect_errno) {
        echo $database->connect_error;
    }
}

Your class failed. IT is not handling errors ;)

Disclaimer: everything I wrote is here to help you; If you feel offended, I apologise. This is not what I intended. [1]: http://php.net/manual/en/function.set-error-handler.php [2]: http://www.php-fig.org/psr/psr-3/ [3]: http://www.php-fig.org/psr/psr-4/ [4]: http://www.php-fig.org/psr/psr-1/ [5]: http://symfony.com/doc/2.0/components/class_loader.html [6]: https://getcomposer.org/

#Errorhandler or ErrorLogger? As far as I can see, you wrote an ErrorLogger, not an error handler. You are not [registering an error handler][1]. The only thing these classes seem to do is Logging and giving access to the errors - with the option to truncate them.

So in fact, you created a Logger that can delete all errors (now why would you do that?). So call it a Logger ;)

The good peeps over at psr - standards have create a really nice [interface][2] for a Logger. Implementing that interface would be a big plus since you could easily change it with a complete different logging engine if needed.

##Code "errors" You are using namespaces, that's good. But the location of your files is just illogical. Stick to [psr-4][3] or [psr-1][4]. Standards exist because they are proved to be good. And instead of using all those requires. Use an auto loader instead. Write a custom one or use a complete solution like [Symfony loader][5] or even [composer][6].

In your database you are only saving the error, nothing more. Some extra information would be useful. Like when did it occur for instance.

If every method starts with the same word and if that word can also be found in the class name, you probably don't need it. Writing:

$errorHandler = new ErrorHandlerController;
$errorHandler->handleErrorLogging($error);

It feels weird. You say that it should handle logging errors. But you need an error to handle error logging. But the only thing it does is log an error. So what does the ErrorHandlerController do? It passes everything to the ErrorMapper. So why not use the error mapper?

$errorHandler = new ErrorHandlerDatabaseMapper;
$errorHandler->log($error);

Way more readable ;)

Then your method name: returnErrorList. Return to where? The client? What you are doing is 'getting'. So getErrors or getErrorsAsList. But what is a list? It's just an array

The same goes for truncateErrorList. What is the List keyword doing there? And why is it returning something? This means that every piece of code that truncates all the errors needs to check for success. Throw an Exception ;)

When using the local error mapper problems will arise if the error message contains ';'.

And as a last remark. If you are creating an ErrorHandler and after you have created your error handler you write:

if($configuration['errors']['enable_error_logs'] == 1) {
    if($database->connect_errno) {
        echo $database->connect_error;
    }
}

Your class failed. It is not handling errors ;)

Disclaimer: everything I wrote is here to help you; If you feel offended, I apologise. This is not what I intended. [1]: http://php.net/manual/en/function.set-error-handler.php [2]: http://www.php-fig.org/psr/psr-3/ [3]: http://www.php-fig.org/psr/psr-4/ [4]: http://www.php-fig.org/psr/psr-1/ [5]: http://symfony.com/doc/2.0/components/class_loader.html [6]: https://getcomposer.org/