Hi!
For a while now (I think probably since the update to Laravel 4.1) I sometimes get the Error Exception: "Object of class DateTime could not be converted to string", when trying to save an Eloquent object to the Database.
The message gives very little cue about the root cause for the error as it seems. I got the error in a variety of different situations, and could not figure out yet, what was the common pattern behind them. So sorry for not being more specific here on how to reproduce the problem.
It obviously is somehow related to objects with DateTime attributes, but does not happen in a predictable way. I save an object with a DateTime successfully, then change a DateTime attribute value by one day and the error is suddenly thrown. I think the message that is thrown is not very helpful to find the root cause of the issue.
Has anybody else had experienced this problem? How could you fix it? Do you know the cause? Is it a Laravel thing itself, or is the framework not used correctly? Will there be a fix, or an improvement in the next Laravel version?
Thank you for your help!
It seems that this Exception is just masking other errors. Only when I got rid of all dateTime related attributes (by setting them NULL), the real error was shown, and I could fix the actual problem. After that, the DateTime exception was not thrown anymore as well.
I have seen this before as well, one of the exception handlers serializes the attributes to create the error message, but if you have an object that can't be implicitly converted to a string (like DateTime) then it just fails and hides the original error.
I think I worked around the problem by using Carbon everywhere instead of DateTime.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast