Releases: symbiote/silverstripe-addressable
Releases · symbiote/silverstripe-addressable
Silverstripe 5 support
Guzzle updates, Silverstripe version update
Updates to fix guzzle security issues, attach to latest Silverstripe version
5.0.3
5.0.2
5.0.1
5.0.0: Add MapboxGeocodeService to allow using Mapbox services
* Add MapboxGeocodeService * Rename GeocodeService to GoogleGeocodeService * Implement GeocodeServiceInterface
4.0.1: Update the hasExtension check on Addressable class
Could not find `'Addressable'` because the class is now namespaced. Changed to `Addressable::class`
4.0.0 - SilverStripe 4 upgrade
Changes from SilverStripe 3.X
GoogleGeocoding
changed class name toSymbiote\Addressable\GeocodeService
- The static method
address_to_point
was changed to a non-static method calledaddressToPoint
. This allows you to use the Injector and replace GeocodeService with something else if you need to.
- The static method
Addressable::set_allowed_states(array('' => '', 'NSW' => "New South Wales"));
has been deprecated in favour of config values.Addressable::set_allowed_countries(array('' => '', 'AU' => "Australia"));
has been deprecated in favour of config values.Addressable::set_postcode_regex(...);
has been deprecated in favour of config values.Addressable::set_postcode_regex
config value has been deprecated in favour ofAddressable::postcode_regex
- NOTE: Previously there was a hack in Addressable that read
Addressable::set_postcode_regex
config value, then calledAddressable::set_postcode_regex()
to update theprotected static postcode_regex;
value in the Addressable __construct() method.
- NOTE: Previously there was a hack in Addressable that read
3.0.1
- Fix tests and get them running in TravisCI
- Change to PSR-2
- Add comments surrounding how things work / why certain features exist
Fix Frontend Fields
Changes:
- Make updateFrontEndFields on Geocodable compatible with DataObject #56