Scale Address Field - 7.x-2.0
This is the initial release of the 2.x version of Scale Address Field. Note that 1.x and 2.x attempt to solve very different issues. Read on for details.
Introduction to 2.x
The 2.x Scale Address Field series is completely distinct from the 1.x series; it's a ground-up rewrite that solves a different problem set. Though both are aimed at Drupal sites that serve Address Fields to unauthenticated users at scale, the 1.x branch attempted to work around usability issues while the 2.x branch is purely aimed at solving performance/scalability issues.
In particular, it resolves performance bottlenecks stemming from the generation of large volumes of cache_form data due to the way Drupal Form API's AJAX/AHAH functionality is implemented (and Address Field's reliance on the FAPI). For full details, see the README file.
Reasons to install other than scalability
Beyond database scalability improvements, this module also provides a couple of neat features that Address Field does not offer:
- Configuration of address field components, labels, and options via JSON.
- Instantaneous field updates on the client-side (no waiting for Drupal AJAX to respond).
For full details, see the README.
Upgrading from 1.x
Before upgrading from the 1.x series, you should ask your self, "Do I even need this module anymore?" Most of the bugs that the module worked around have been taken care of as of Drupal 7.27. Consider upgrading Drupal, disabling Scale Address Field, and re-evaluating.
If you believe 2.x is for you, and you're coming from 1.x, be aware of the following:
- Although end-user functionality is meant to be in parity with the Address Field module, the way in which this is accomplished is dramatically different. You may need to refactor any customizations you've built on top of Address Field / Scale Address Field.
- This initial release of Scale Address Field 2.x expects that the Address Field is rendered in the way it would be rendered by Drupal Core (field markup order, in particular). If you have a theme that alters this in any way, you may run into issues. Test thoroughly before you deploy!