Skip to content
  1. Sep 09, 2011
  2. Feb 25, 2011
  3. Feb 14, 2011
  4. Jan 20, 2011
  5. Jan 18, 2011
  6. Jan 17, 2011
  7. Jan 11, 2011
  8. Jul 06, 2010
  9. Jul 04, 2010
  10. Feb 25, 2009
  11. Feb 24, 2009
  12. Dec 09, 2008
  13. Dec 05, 2008
  14. Nov 24, 2008
  15. Nov 20, 2008
    • Brandon Bergren's avatar
      OK, I've been sitting on this MUCH longer than is comfortable. · 2b771e20
      Brandon Bergren authored
      This is a major change that I have been testing and writing locally. I just tagged UNSTABLE4 before this commit so there's a point to go back to if I end up having to roll back.
      
      * Add per-location-field weights and defaults.
      * Add location_api_variant() that I will increment when breaking something in the future that might be used from another module. It is now 1.
      * Make settings on location_cck work nicely.
      * Field settings are now in a table.
      * Field settings defaults can now be overridden in the UI.
      * Field settings are now weighted. (Draggable in D6!)
      * "Force Default" may now be used for all fields.
      * Content type settings validation is repaired again.
      * Major COW changes (again) -- Should not have any impact on sites, but be careful until the new code is proven.
      * Tests were added to ensure COW functionality doesn't break. (Tests were committed earlier)
      
      API Changes:
      
      * If you were using a location_element, the #location_settings is now the *entire* settings array, not $settings['form']['fields']!
      * hook_locationapi() 'collection default' and 'default values' ops  have been merged into a single 'defaults' op, which now allows specifying default weight.
      * Collection status 3 is now 4. (Relevant for the 'country' field.)
      2b771e20
  16. Oct 21, 2008
    • Brandon Bergren's avatar
      A) Clean up a bunch of duplication and centralize the way location settings are handled. · dc57b3f8
      Brandon Bergren authored
      This allows us to have multiple user locations, and simplifies the API for associating locations with other things.
      
      The variables used by location got all shuffled around because of this, but I put in compatibility code to keep setting location_maxnum_{nodetype} and location_defaultnum_{nodetype}, because there is a lot of contrib modules checking for them.
      
      B) Made user locations work more like node locations.
      
      C) Allow more than one location to be "required".
      
      D) Reorganize the variables. Now there is a single variable per content type. (location_settings_{nodetype})
      
      E) Make virtual fields hideable, and add the map link as a virtual field.
      
      F) API change: The return value of 'virtual fields' op is now an array of keys and values, where the values are the labels for the hide checkboxes.
      dc57b3f8
  17. Oct 09, 2008
    • Brandon Bergren's avatar
    • Brandon Bergren's avatar
      * Add function location_province_code(). · 42e9eb5c
      Brandon Bergren authored
      * Fix $op 'delete' on hook_locationapi().
      * API CHANGE: Use location_save_locations() with an empty array instead of deleting rows from {location_instance}. This lets us have "real" deletion instead of relying on garbage collection.
      
      Before:
      <code>
      db_query("DELETE FROM {location_instance} WHERE genid = '%s'", 'mykey:'. $obj->id);
      </code>
      
      After:
      <code>
      $locations = array();
      location_save_locations($locations, array('genid' => 'mykey:'. $obj->id));
      </code>
      
      * Remove garbage collection routine and UI from settings page. References are checked automatically now.
      42e9eb5c
  18. Oct 07, 2008
  19. Oct 03, 2008
  20. Sep 09, 2008
  21. Aug 18, 2008
  22. Aug 06, 2008
  23. Jul 24, 2008
  24. Jun 05, 2008
  25. Mar 21, 2008
  26. Mar 06, 2008
  27. Feb 04, 2008
  28. Jan 24, 2008
  29. Jan 23, 2008