[Zope-CMF] Multilingual site with CMF/Plone?

Erik Lange erik@digitalforbruger.dk
Wed, 12 Feb 2003 10:00:08 +0100

At 02:57 AM 2/12/03, Andy McKay wrote:
>>Something that doen't "behaves different to CMFDefault even on simple 
>CMF Default != CMF

I know :-)

I queted Aussum, and believe what he meant, was CMF Core.

>CMF Default is one way of doing it, Plone is another, MMManger is another, 
>Zope Turbo sounds like its another. You have chosen to make MMManager 
>compatible with CMF Default by the sound of it and assume Plone should 
>follow this path.

No, that's not what I'm saying. I'm saying that many new Zopistas runs into 
trouble using Plone, because you have chosen to follow a different path, 
and they're not aware of that - that's all.

>>Have you tried using CMF Portlets or My Media Manager with Plone?
>I've looked at them and I'll probably be working on integrating CMF 
>Portlets, or something similar into Plone for our next release.

So, as I have said before, new users should not expect other CMF products 
to work out-of-the-box with Plone, and if they're not up to doing the 
fiddling themselves, they should wait for the "Plonenification" of the 
product they wish to use with Plone.

>>I'm not saying Plone is bad, but I believe that nothing is perfect in 
>>this world... Why do you get so offended by this ? Because we don't 
>>participate in making Plone perfect ? Well, if someone tells us of an 
>>error in one of our products, we're thankfull for the info, even if the 
>>person doesn't offer to correct the error.
>Im not offended, Im glad there are so many other products building on the 
>CMF. That's good for everyone.

Thanks, I agree.

>>Now, if there are good reasons to doing things differently ( because CMF 
>>is ugly / broken / incorrect or doesn't do what we want ), I truely 
>>believe this should be fixed in CMF, and not in a seperate product, 
>>making either everything depending on this seperate product or forcing 
>>people to make two releases of their products, one for CMF and one for Plone.
>That implies that if we want to do anything different we should pass that 
>down to CMF. We all know that isn't going to happen :)

Why not ?

>Similarly there are different CMS's out there like Silva, CPS, are you 
>suggesting they should all pass their changes down to CMF or Zope? They 
>aren't bug fixes or improvements, they are just different.

Well, if the CMF is ugly / broken / incorrect or doesn't do what we want, 
I'm sure your suggestion or improvements will be appreciated.

>The ability for us to use a common platform like Zope and CMF is great, 
>but there is some point where projects are going to fork away. If for the 
>sake of argument there is a fork for Plone, it's an extremely minor fork 
>away from CMF Default.

Fine - I'm just saying that it's confusing people, who aren't aware of the 
difference, how minor it might be.

>We aren't forcing anyone to do anything. If everyone decides they dont 
>want to make their products work with Plone, then fine. That's Plone's loss.
>And really Im going to reiterate, what really does a user have to do make 
>their product compatible with Plone? The answer for products I have 
>converted is minimal to none.

Okay - I'm still just saying, that it's confusing new Zopistas, that's all.

>>Please don't take this personally :-(
>Im not.

Thanks :-)

Kind regards,
Erik Lange