Safecracker issues
Developer Preview
When editting an entry i get an database error.
A Database Error Occurred
Error Number: 1264
Out of range value for column 'edit_date' at row 1
UPDATE `exp_channel_titles` SET `channel_id` = '1', `author_id` = '1', `site_id` = '1',
`ip_address` = '127.0.0.1', `title` = 'aa', `url_title` = 'aa', `entry_date` = '1363623840',
`edit_date` = '642552522960827023525', `versioning_enabled` = 'y', `year` = '2013',
`month` = '03', `day` = '18', `expiration_date` = 0, `comment_expiration_date` = 0,
`sticky` = 'n', `status` = 'open', `allow_comments` = 'n',
`recent_comment_date` = '0' WHERE `entry_id` = '1'
Filename: libraries/api/Api_channel_entries.php
Line Number: 1812Edit_date wrong Looks like SafeCracker does fetch the edit_date for an entry, But at submit the edit_date too is offered to the API. this causes subsequent double encoding from timestamp to the format yyyymmddhhmmss. (which on 64-bit systems succeeds a few times 😊
Uses deprecated functions “Deprecated function set_human_time() called in system/expressionengine/modules/safecracker/libraries/Safecracker_lib.php”
Allow Comments The allow_comments=”yes” parameter is always reset to no for an entry. https://support.ellislab.com/bugs/detail/18278/#10097
Thanks, GDmac! I’ve taken care of these three issues and they should be fixed in the next dev preview.
Can we as dev-previewers have acces to the repo? Even (via github?) have commit acces to certain trees, or is that over-asking? Last question, why is EE still on CI 2.01, can we at least have CI 2.13?
Yeah that may be over-asking, I think we mainly don’t want to deal with getting licensing agreements from everyone for us to use their code if we take it, plus it’s a lot of overhead to review third-party code submissions and working with them to make corrections.
EE’s CI is kind of it’s own thing right now. Is there something in CI 2.13 you’d like to see in there? We may be able to patch it in. We of course would like to upgrade CI completely pretty soon, but for now, we can try to work in things that are missing. For example, the Email library has been completely replaced with CI’s latest version for EE 2.6 in order to fix some bugs and add some features (not sure if it made it in the last preview build, but I know Robin was working on it).
Just saw the dev-preview2. I don’t know if a release is imminent, i won’t be able to dive into things untill later next week.
Kevin, about CI updates. i (and many others) would really like the session library to be more integrated. Currently EE is holding of on the session library, care to share why this is so?
That’s fine, you should have time to test some more, we’ll likely let it stew for a couple more weeks, we’re trying to give more time to dev previews to make sure issues are worked out.
I would guess CI_Session hasn’t been updated because it’s pretty much been completely overridden by EE_Session so we have more control over how EE handles its sessions (and a lot has changed for 2.6 for added security and Remember Me). But upgrading CI entirely is something we’d like to do, we have upcoming features that depend on things in the latest CI, so it’s likely we’ll be updating CI_Session along the way.