Comment 1 for bug 1024807

This situation occured on unpredictable occasions. I know that it is the worst situation for any person working in information technologies. But one thing i'm sure of, is that it is not something coming from a specific misused state or misleading manipulations of authpuppy.

Here's some example of what i done : I subscribed a new user with a "validation" status. When i save it, a symfony page appear. (One thing i've noticed is that symfony always give the same error number, so i don't pay attention to symfony's message as long as seeing a symfony page means error).

I restart the server with the frondend_dev.php url part. I always tend to see SQL Statements on first instance. I've seen an SQL statement with a "WHERE" part made with "id=?". Taking this same SQL statement and makink it run in Mysql give an error, "id can't be compared to ?".

For each user subscribed with any other status than validation, everything's fine, i didn't get any error.

The second example is when i subscribe a user who already exist, always with this "validation" status. Instead of having a trapped error saying that this user exist, i have a symfony page with the common error 400, But as soon as a status is different than "validation", there's a message telling me that the email adress already exist, wich is ok.

Anyway, i'll try to make a document giving specific point of this situation.

I just want to say that what i do is not in any negative purpose. I'm in a situation (that i keep personal) where i have to stay home not by choice, Authpuppy is, in my point of view, a very good product. Everything's not perfect in this world anyhow.