Django 1.4 now has a powerful and flexible way to handle i18n urls. For compatibility and simplicity reasons, I think django-cms should move to that mechanism.
I've started the work on that here (help welcomed! :-) ):
Many tests are not passing anymore and there are still a few things to sort out:
Also, please note the rewrite may need a decision of #910 .
Yes, as noted somewhere (forgot which issue, probably multiple ones), moving to i18n_patterns is my preferred solution (if it proofs feasible) to solve our hacky MultilingualURLMiddleware and to ideally remove our reverse monkeypatching.
I made a pull request #1236 which you closed mentioning move to i18n patterns. I hope they support everything Django CMS needs?
multilingual middleware has been removed
awesome! Which are the related commits?
Thx! :) Now I can upgrade!