There seems to be a problem when working on a site that's off-line.

I can click to make the field editable, as expected, and I can edit within the field, as expected. But when I move the focus from the field, I get the red system warning "status : Operating in off-line mode," and the field 1) reverts to its previous contents 2) stays in the "editable" look (i.e. does not resume looking like the rest of the "View" page).

I didn't notice this while working in my sandbox since it does not need to go off-line. However, when I started updating my live site, I took it off-line, and noticed this issue.

Comments

frankcarey’s picture

Ajax calls probably getting 404/503 errors? I know other AJAX modules (Fupload) that have this issue as well.

Bairnsfather’s picture

I can't say it's 404/503 since that's not what was reported.

I've since uninstalled this module although I can imagine myself revisiting it, but I still have more than a few questions.

But the short answer is I do not know exactly what was generating the message, it was in the same area as the field I was editing AND turning modules on/off and making the site online/offline convinced me it was editablefields. The error was styled like other system error messages, boxed in red and said "status : Operating in off-line mode." Hm, I don't see a screen snapshot on my desktop which I can attach here…

I originally thought this module would be great for large content types, with lots of fields. In my mind I imagined this module would allow me to present a lot of fields on one page, and let visitors surgically edit the content (i.e. fields in the cck type). I imagined this would be superior: to have Drupal only update the fields of the record being browsed, instead of loading/submitting the whole thing via the /edit page.

HOWEVER, due to the fact I was using InnoDB tables (and a version of MySQL before 5.2) an error message came up at some point written to my web pages that indicated CCK was trying to UPDATE the whole record (content type), not just the one field I'd updated. So because of those issues I had to redesign my content types and put editablefields on the back burner.

But I wanted to report this anyway.

joelpittet’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Closing this to triage the queue. Feel free to comment if you'd like this to be re-opened, though currently there is nobody supporting the 6.x branch.