The nodes I'm exposing to user contain location information, which I inputed. We want to allow the user to update the Body, but not the Title, nor the Location, thus your module is perfect. After creating the revision some of the nodes Location data disappears (example: state) , while other location information (example: Lat/Lon) is preserved. The Body of the node is being properly updated. Any thoughts on how we can preserve all the location data?

CommentFileSizeAuthor
#4 location_for_body_revision.patch6.84 KBrobertgarrigos

Comments

jamesJonas’s picture

Hum, just tested using a Revert (reverting a node to a previous version). All location information was lost, including lat/lon.

Now testing formfilters module. Was able to expose just the body by filtering the other fields in the forms. Seems to be working. This may be a work-around.

robertgarrigos’s picture

Assigned: Unassigned » robertgarrigos

Would you mind to explain how exactly you get those location fields? Are they cck fields or generated by any other module? How can I exactly reproduce this bug? Thanks for your help

jamesJonas’s picture

The location fields are place there via the location.module. First enable locations module, and then enable for the target content type you wish to test. This is done by going to 'content type' and hitting the location link on the top. Set the number of locations to one and enable the fields you wish to caputre the locations for (address, city, state...). I have the gmap module installed. I heard that there may have been an issue during location update which was resolved in the next dev version of the gmap module.

robertgarrigos’s picture

StatusFileSize
new6.84 KB

I tried to reproduce this error with the latest modules with no luck. I guess latest dev version of gmap solved the problem. However, there is patch to apply to location.module (5.x-1.x-dev) in order to get rid of a php error message.

robertgarrigos’s picture

Status: Active » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.