Found by mauryg in #572916: Optional admin approval:
The date of creation of bookings is either not set or not displayed correctly.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | publicbookings.573612-2.patch | 2.22 KB | Anonymous (not verified) |
Found by mauryg in #572916: Optional admin approval:
The date of creation of bookings is either not set or not displayed correctly.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | publicbookings.573612-2.patch | 2.22 KB | Anonymous (not verified) |
Comments
Comment #1
Anonymous (not verified) commentedIts committed.
Comment #2
mauryg commented@tirsales
I installed the DEV version I downloaded yesterday on my live site. I confirmed that the publicbookings.module contains the patch.
I created a booking, confirmed it then updated it. When I looked at the update page again the creation data was still 0000-00-00 00:00 and the modified date was blank. Then I read your code and noted that it REQUIRES that the SQL triggers option be checked. When I did that and repeated the process, the creation date was correct but the modified date was still blank. I confirmed this using phpMyAdmin to check the table in the database. The modified date was still 0000-00-00 00:00.
Comment #3
Anonymous (not verified) commentedActually the patch should REMOVE the need to use "using_sql_triggers" ... I guess I committed the wrong version.
Comment #4
Anonymous (not verified) commentedI just got the dev from the server and the patch (removing the need for bookingsapi_using_sql_ts_triggers) is in. But I forgot another thing (committed and attached)
Comment #5
Anonymous (not verified) commentedComment #6
Anonymous (not verified) commented