uc_addresses 7.x-1.0-alpha2

In this second alpha release of Ubercart Addresses 7.x-1.0, lots of features have been added, though the "base" features (address book, checkout, order administration) did not change much. Ubercart Addresses now integrates with Entity API, which means you can access addresses from Rules and Panels and a lot of other modules that provide Entity related functionality. The other great addition is extended Views integration. In 7.x-1.0-alpha1 you already had "basic" Views integration, meaning you could create a view of addresses using fields. The 7.x-1.0-alpha2 version brings much more, especially access related features. This are the new features:

• Create a View using the address row style, allowing you to create an address listing themed just like in the address book;
• When using fields: view, edit and delete links;
• Filter the View by address access;
• In arguments/contextual filters: validators for address access;
• Address access checks for Views displays;
• A View to replace the address book page (this View is disabled by default).

Changes since 7.x-1.0-alpha1

API changes

• Issue #1894858 by MegaChriz: made API change in UcAddressesPermissions to be able to check access for other users.
• Issue #1910626 by MegaChriz: API change: specified field data types.

Bug fixes

• Issue #1829348 by MegaChriz: sort countries list after translation.
• Issue #1854736 by MegaChriz: fixed notice bug that occurred when having a field appearing in one of the address panes only.
• Issue #1860040 by MegaChriz: ensure an address instance is assigned to the order when an user without addresses enters checkout.
• Issue #1895918 by MegaChriz: fixed bug where trying to load a non- existing address could lead to a PHP notice error.
• Issue #1927258 by MegaChriz: fixed bug where selecting an address at checkout leaded to checkbox fields always being checked.
• Issue #1961590 by MegaChriz: fixed "empty" address format.

New features

• Issue #1843562 by MegaChriz: respect Ubercart's "same address for billing and delivery by default" setting.
• Issue #1866096 by MegaChriz: populate extra fields from previous orders.
• Issue #1871916 by MegaChriz: display a warning when a field handler is missing.
• Issue #1831424 by MegaChriz: added Entity integration.
• Issue #1900150 by MegaChriz: added Views address access filters.
• Issue #1900176 by MegaChriz: added Views address action links.
• Issue #1908904 by MegaChriz: added uc_addresses relationship in user based views.
• Issue #1900468 by MegaChriz: Entity integration: added address properties to user and uc_order.
• Issue #1942748 by MegaChriz: added Views address row style plugin.
• Issue #1942746 by MegaChriz: added Views display access plugin and Views argument validator plugins for addresses.
• Issue #1433034 by MegaChriz: added default View for the address book page.

Other changes

• by MegaChriz: moved UcAddressesTextFieldHandler from the example module to the main module and renamed the used handler in the example module.
• Issue #1911136 by MegaChriz: separated schema definitions from field handler API definitions in the example module.

Plans for the next release

For the next release, integration with Feeds is planned. Then it will become possible to import addresses from a CSV-file (and from other sources to, due to Feeds' great architecture).
The next release will be most likely the first bèta for the 7.x-1.0 series.

Issues:

• #1309546: Address import / Feeds integration

Missing a feature?

I plan to create a first release candidate for the 7.x-1.0 series in early July, 2013. From then on, I plan to move my focus on to other projects which means I'll be spending less time on this project.
So, if there is a feature you would like to get in, then go on and help to make it happen! You don't have to be a coder to get your feature in. Writing a plan on how you would like the feature to work, eventually provided with graphical designs can already be enough. I'm willing to do the coding if the feature is well enough described (but only until July 2013).
There are already some issues in consideration, see #1910860: Ubercart Addresses roadmap. These issues may not make it when there is not enough interest in them.