Allow ordering in EasyNewsletters

[Gagaro]

I have a project in which EL have folders to store image, old NL, collections, ...

Having the possibility to order is really useful there.

[coveralls]

Coverage remained the same at 78.851% when pulling 87fa66185d9b563aa4948d15edd62e6a09851726 on gagaro-ordering into f117ffab747645d6da17c2fad413b78a9e940cc1 on master.

[coveralls]

Coverage remained the same at 78.851% when pulling 87fa66185d9b563aa4948d15edd62e6a09851726 on gagaro-ordering into f117ffab747645d6da17c2fad413b78a9e940cc1 on master.

[MrTango]

changing base class is not an trival task and needs also an upgrade step to migrate existing objects to the new object type. I'm not sure if that make sense now, as we are planing to migrate to Dexterity in one of th next major steps. Then would have this too. I'm fine in merging this, if you provide also a upgrade step that makes sure nothing brake's on existing content.

[Gagaro]

Do you have any idea when the migration to Dexterity would be? I could wait if this is not too far away.

Thanks

[MrTango]

Hart to say, could be anytime in the next 2-3 years I would say. It depends on people who want to work on that and on funding for this tasks too. Either by clients or community. There are some other task, which bring more visible advantages and therfor easier to sell to clients, like the Mosaico editor integration or making DX Collections configurable so that we could define the ENL-Aggregation templates per collection. Also logging of the send out process into the issue and some tools to manage bounces and hold the subscriber list clean. So as usual depend on who is willing to invest time and/or money in what task.