While I agree with the reasons behind for removing the field in the first place there is a major problem when this field is not available at least as a behavior. For the migration process from AT to plone.app.contenttypes it is not desirable to (silently) discard the location information. There should be a way to preserve this information during the migration.
Andreas hvelarde wrote > On 13-05-2014 15:21, Philip Bauer wrote: >> Omitting the field in DX was intentional. See >> https://github.com/plone/plone.app.contenttypes/issues/30 > > HV> no, it wasn't; as I mentioned we had a conversation about this on > the Dexterity developers group more than 2 years ago and we came into > the conclusion that the field should be added, but no index should be > included letting the integrators the freedom to use whatever location > implementation they wanted to use. > > I simply can't find the ticket on the Google group. > > I know this because I ended adding a location field on collective.nitf, > package that was on it's early stage of development at that time: > > https://github.com/collective/collective.nitf/commit/b3ecfdf8a4f61b4bc0f7bf36b9c3298b66adb169 > > may be David remembers this. > > best regards > > > _______________________________________________ > Product-Developers mailing list > Product-Developers@.plone > https://lists.plone.org/mailman/listinfo/plone-product-developers > > > smime.p7s (5K) > <http://plone.293351.n2.nabble.com/attachment/7571371/0/smime.p7s> -- View this message in context: http://plone.293351.n2.nabble.com/location-field-missing-in-Dexterity-plone-app-contenttypes-tp7571357p7571377.html Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list product-develop...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-product-developers
