entity_lister 7.x-2.0-alpha1

Install

Works with Drupal: 7.x

MD5: 3d4254da36324365c7a88567d28c217f

SHA-1: dd511451edfcf13743cfbeff0b85643eb5cdac33

SHA-256: eb44fd7fa4f32f4850281ed4fbfcd57e2524b1599e5356ef5e43da85648a051c

Download entity_lister-7.x-2.0-alpha1.zipzip 23.49 KB

MD5: 7b55a55c27d4ce09cba38ba10bdd77fb

SHA-1: 219f23e203eb0b4952bd6e5e431259a289b6b040

SHA-256: 1e5360ca0bbdd235fc8c2b1b50f7694c5134fa65945e13dac5c817411e81f8cc

Differences between the 2x branch and 1x branch are minor and for the vast majority of applications will not affect your output at all. However, the 2x branch exists because there is some small chance you could get different output than you do with 1x and we are strictly excluding all changes from the 1x branch that could affect output (with obvious exceptions for critical bugs, if any arise).
In other words, if you are using Entity Lister 1.0 or 1.1 and you upgrade to 2.0-alpha1, you will probably not notice any difference, especially if you haven't extended the EntityLister class.
If you extend the EntityLister class in your application, chances are greater that you will notice a difference when upgrading from 1x to 2x and will have to make adjustments in your class.
The 2x branch makes better use of entity_get_info() and entity_view(), so look for those calls if you extend the class. In renderItems(), instead of checking if an <entity_type>_view function exists, in the 2x branch we use entity_view().
The "item_list" config option has been eliminated in 2x, since it's possible to achieve the same output using a template and view mode. If you use the "item_list" config in 1x, you will need to make some minor theming changes for 2x.
This is an alpha release, so strictly speaking, API-breaking changes could still be allowed into the 2x branch at some point.

Created by: arnoldbird
Created on: 21 Nov 2013 at 20:50 UTC
Last updated: 13 Dec 2013 at 15:58 UTC