[Product-Developers] Re: collective.contentlicensing 2.2.0 compatibility with Plone 4.0a3

David Glick davidglick at groundwire.org
Mon Jan 11 19:14:38 UTC 2010


Raphael Ritz wrote:
> jmf wrote:
>> Le vendredi 08 janvier 2010 11:11:34 AM, Graham Perrin a écrit :
>>> Graham Perrin wrote:
>>>> Please: any suggestions on how to make collective.contentlicensing
>>>> compatible with Plone 4?
>>>>
>
> Hi folks,
>
> looking at
>
>   http://dev.plone.org/collective/browser/collective.contentlicensing
>
> it seems like people are working on it.
>
> Since this product is on my watch list anyway, I just gave it a try.
> Starting from
>
> http://svn.plone.org/svn/collective/collective.contentlicensing/branches/davisagli-sanity-and-modernization 
>
>
> I got it up and running on Plone 4 (a3) after the following changes:
>
> <snip>
>
> I'm hesitant to check that in as it breaks backwards compatibility
> (depending on how far back you go) so I thought I better ask:
>
> Should I do such changes on
>
> 1. trunk (that would need more changes even)
> 2. the modernization branch mentioned above
> 3. a new branch (branching off from where?)
>
> What do people prefer?
>
> Last but not least I'll note that while the product's functionality
> is in place after the changes mentioned above the presentation layer
> is still broken as the templates need to be adjusted for the new
> translation engine.
Note that my branch was a pretty significant change in the 
implementation (I switched to using a schema extender, in part to 
support the use of the product with LinguaPlone). I didn't have the time 
or energy to push for it to be merged to trunk, so I'm not sure if the 
package maintainers were aware of my branch, and I believe some 
diverging work has been done on trunk since I made the branch...but I 
haven't really paid close attention and don't know the current 
status...sorry.
David

--
David Glick
Web Developer
Groundwire
206.286.1235x32
davidglick at groundwire.org
http://groundwire.org

ONE/Northwest is now Groundwire!




More information about the Product-Developers mailing list