Closed (outdated)
Project:
Location
Version:
6.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Aug 2009 at 22:20 UTC
Updated:
19 Jul 2016 at 12:02 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
yesct commentedPlease check to see if this is still a problem in the new release. If it is, reply with a new summary and set the status back to active.
Also, there seem to have been a lot of "default" type issues, maybe do a search for default in the issue queue and see if another is a duplicate...
http://drupal.org/project/issues/location?order=last_comment_timestamp&s...
Comment #2
igor.ro commentedThe problem was because of using location_default_location to get empty location.
but as you can mind "empty" and "default" locations are not the same.
Here is the patch
Comment #3
shaneonabike commented+1
Comment #4
nilla054 commentedWhen adding a new content type, default values are loaded to certain fields. when the user edits the default value and previews it, the new value is reflected in the node preview but the form still holds the default value and when the form is submitted the default value is saved instead of saving the new value.
Form works fine when it is not previewed (new value is saved into the database)
Comment #5
karens commentedAn issue with a patch for the Location module does not belong in the CCK issue queue. If something is wrong with the way default values work in Location fields, that is most likely a Location issue.
Comment #6
rooby commentedThis should be needs review.
The patch still applies with offsets.
I have not a chance to review right now though.
Comment #7
podarokbot recall
Comment #8
podarokbot
Comment #10
legolasboClosing old D6 issues as D6 is end of life