I am running the latest dev version of Autosave (I also tried the stable version) on Open Atrium , and forms don't appear to be auto-saving in the database. A blue pop-up bar appears at the bottom of the node while editing, but no data is written to the autosaved_forms table and therefore no recovery is possible.

I'm not sure if this is a problem with Autosave or an issue with Atrium. Any thoughts on what could be going wrong?

Comments

ericaordinary’s picture

ericaordinary commented

I should have added I'm running Drupal 6.19 and Atrium 6.x-1.0-alpha9.

ericaordinary’s picture

ericaordinary commented

Further info: I have created two clean drupal installs, one with atrium and one without, both with Garland theme and no contrib modules besides autosave and atrium. The latest stable version of Autosave is working correctly on the drupal site, but not working on the atrium site. The pop is appearing like before but with text on it this time (there was no text in my previous install, just a blue bar), but no data is being saved to the DB.

I will continue to debug to see if I can narrow down the issue.

liquidcms’s picture

liquidcms commented

well i know Autosave works. Atrium messes up a few things so would guess something there. I have a couple Atrium installs around; i'll see if i get some time later this week and perhaps and i can install and test.

ericaordinary’s picture

ericaordinary commented

liquidcms: thanks for the speedy reply.

Some more info - it seems this is Organic Groups related rather than Atrium directly, possibly an issue with persistant URLs. For nodes posted into a group the autosave_save function doesn't seem to be getting called at all. These nodes will have a URL of mysite.org/groupname/node.

For nodes that are not posted into groups on atrium the module is saving into the DB, however the javascript "view / ignore / etc" functionality isn't working as it should. Instead the new auto-saved content appears on the node when viewing even though it wasn't saved by submitting the form, and when editing the node the old and new content appears in a text area below the original body field (see https://skitch.com/ericaordinary/fdu31/test-story-2-vanilla-atrium.local...). I don't know if this is related to the above or a separate issue altogether.

If I get some time I'll do a bit more digging into this and test out the dev version of the module as well in case it fixes the second issue.

Russell Mann’s picture

Russell Mann commented

subscribing, has anyone successfully used autosave with og and/or atrium?

liquidcms’s picture

liquidcms commented

i can confirm that Autosave is not working with Atrium - feel free to provide a patch and i will commit.

nikkilabrum’s picture

nikkilabrum commented

subscribing, having same problem with Drupal Commons.

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented

Subscribing.

metareason’s picture

metareason commented

Subscribing

a_c_m’s picture

a_c_m commented

Have you tried using the patch here : http://drupal.org/node/850934 ?

liquidcms’s picture

liquidcms commented
Status: Active » Postponed (maintainer needs more info)

the strongarm fix was committed; not sure if that impacts use with Atrium (doubt anything to do with OG).. please retest with latest -dev and let me know.