Migrate History Views

[eleddy]

Move to browserviews, figure out whats up with a metadata file and no image associated with it.

Files:

• https://github.com/plone/Products.CMFPlone/blob/master/Products/CMFPlone/skins/plone_forms/history_form.pt
• https://github.com/plone/Products.CMFPlone/blob/master/Products/CMFPlone/skins/plone_forms/history_comparison.pt
• https://github.com/plone/Products.CMFPlone/blob/master/Products/CMFPlone/skins/plone_images/history_compare_with_previous_inline.png.metadata

[giacomos]

-1
it's one of the many little things that are not used on a daily base but that makes plone more sellable as it's a shimmering feature. Plus if one of our customers is really using it and asks for a migration we will end up re-adding it. It's easier to hide it than re-adding it. Please don't.

[eleddy]

@giacomos this is going to be a problem with a lot of these features. They are great for selling but just bloat the core. This code hasn't been touched in 3 years, which is likely because its never used. IIRC, versioning isn't even enabled by default. Would you be willing to accept this ticket and move it to an add on? I feel lik it would get more love in the collective than in core, and people could update it to include more features. I know that plone has needed a general "auditing" package for a while, this could be a good start to that.

[vangheem]

Code not being touched could mean it's stable. Versioning is enabled for most types by default and is an important feature of plone.

We need to keep this IMO.

[eleddy]

@vangheem ahem, I believe just last night I was just being chastised for not removing things... ;) that's fine, we can keep it. I'll update it.

[vangheem]

hey, removing arcane old cpy junk, not versioning!! You're crazy @eleddy :)

[jensens]

outdated - CMFPlone/skins/plone_forms was already removed