So I am not the only person who had bad experiences with Plone? Good to know it was not my own dumbness alone that led me to the conclusion Zope would be a good idea if the Zope people stopped having revolutionary ideas and sat down to document and clean up what they already have...:)
I've been running a Plone based site for two years. The SQL database became non writable on a couple of occasions but apart from that it has been very stable and a breeze to use after about a week getting the hang of it.
We just lost half a year trying to build a scalable Intranet site with Plone and Zope, for an organisation which really needs that scalability. Never again.
We even had some of Europe's best Plone/Zope experts on the project, and they came to the conclusion that it's not really possible (outside some very narrow fields where you can just use Squid or other similar caching to create scalability from where there is none) to create scalable web applications using those tools.
One of the largest problems was th
"Everything should be made as simple as possible, but not simpler."
-- Albert Einstein
Link to project (Score:5, Informative)
http://maven.apache.org/ [apache.org]
Re:Link to project (Score:-1, Troll)
And believe me, Maven is crap of Plone-esque proportions. Check Hani's blog.
Plone-esque proportions (Score:2, Informative)
Re:Plone-esque proportions (Score:0)
Re:Plone-esque proportions (Score:1, Informative)
We even had some of Europe's best Plone/Zope experts on the project, and they came to the conclusion that it's not really possible (outside some very narrow fields where you can just use Squid or other similar caching to create scalability from where there is none) to create scalable web applications using those tools.
One of the largest problems was th