search

cccs-web / core

CCCS' customized django web application
4 stars 11 forks source link

Upgrade Mezzanine and mezzanine_pagedown #147

Closed pwhipp closed 9 years ago

pwhipp commented 9 years ago

We are currently using our own 3.1.3 fork of Mezzanine.

We should upgrade and use the 3.1.9 release version (or update our fork as necessary).

This task may involve some hours of effort because we know that there are issues with mezzanine_pagedown (which is at 0.7 and should move to 0.9 (fixed 0.8)).

cccs-ip commented 9 years ago

Thanks for alerting me to this. I am not sure what you mean by 'fixed 0.8'. Currently our markdown editor doesn't show preview...

pwhipp commented 9 years ago

Sorry - 0.9 is expected to be a fixed version of 0.8 so that we can use it.

cccs-ip commented 9 years ago

I would be happy to upgrade Mezzanine after we sort out a few more of our high priority issues

cccs-ip commented 9 years ago

Please go ahead and try this out via staging

pwhipp commented 9 years ago

This will also address #140.

pwhipp commented 9 years ago

This is available for testing in staging.crossculturalconsult.com

The visible changes should just be that the pagedown stuff works as we hoped. Behind the scenes both Mezzanine and the pagedown are set up differently to accommodate things.

The version of mezzanine is still 3.1.3 because that is the latest version supported by the upstream modeltranslation fork. I have linked the next removed ancestor (Stephen's full mezzanine) which is at version 3.1.10 but there is a fair amount of work involved in merging it because kniyle's fork is 20 commits ahead of and 200 commits behind Stephen's. A gap that I hope Kniyle will close at some point.

If you are happy with this I can merge it into master and deploy it to production.

cccs-ip commented 9 years ago

Pagedown looks good. I am seeing no bugs just yet. Let's deploy. Thank you.

pwhipp commented 9 years ago

Done.