Hi all,
I've been running a test-setup using ZPublisher/WSGIPublisher.py
mongrel2 -> wsgid -> zope2
I'm running into some minor, some larger issues. Most importantly,
transactions are not committed. You know better than I do what that
means. For me, I can't create Plone sites, or even DTMLDocuments. And
when I create then using ZServer, I can't delete them any more through
the wsgi route.
I have a small patch against WSGIPublisher.py (branch 2.13) that fixes
above behaviour (attached).
After applying it creating and deleting content works ok, but when using
the sunburst theme, the created site looks completely unstyled, whereas
using the classic plone theme everything looks much better.
The plot thickens however because when I enable debug-mode, everything
works great!
Maybe someone with better understanding of the mechanics involved now
has an epiphany.
FYI, I'm using the following buildout:
https://github.com/pjstevns/plone.mongrel2
thanks.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/info@nfg.nl/+31.85.877.99.97
________________________________________________________________
Hi,
We've just tagged the 1.0 NEO release.
NEO aims at being a replacement for use-cases where ZEO is used, but
with better scalability (by allowing data of a single database to be
distributed over several machines, and by removing database-level
locking), with failure resilience (by mirroring database content among
machines). Under the hood, it relies on simple features of SQL
databases (safe on-disk data structure, efficient memory usage,
efficient indexes).
Release highlights:
- production-ready !
- asynchronous replication across clusters, for inter-datacenter
redundancy
- there will be no further expensive data schema changes within the 1.x
branch as there were in 0.x branch
- replication performance is significantly increased
- general implementation performance improved
- several bugfixes
What you need to know if you are used to ZODB features:
- Blob API is not implemented yet.
- pack's GC phase will not be implemented in NEO, it relies on
zc.zodbdgc for this: http://pypi.python.org/pypi/zc.zodbdgc
For more details, look at README and CHANGES included with the sources:
http://git.erp5.org/gitweb/neoppod.git/blob/HEAD:/READMEhttp://git.erp5.org/gitweb/neoppod.git/blob/HEAD:/CHANGES
NEO is published on pypi as "neoppod":
http://pypi.python.org/pypi/neoppod
Regards,
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
On 29 August 2012 15:44, Tres Seaver <tseaver(a)palladion.com> wrote:
> On 08/29/2012 09:25 AM, Tres Seaver wrote:
>> That base class has been gone since ZConfig 2.9.2. I don't think the
>> Zope2 trunk has pinned / unpinned ZConfig in a long time, so I'm not
>> sure why it would just now break (ZConfig 2.9.2 was released in
>> February, and 2.9.3 in June).
>
> I just pushed a change to the Zope2 trunk to use the new speling.
While Tres fixed the error on Zope trunk, the same fix is still needed
by zLOG. According to
http://svn.zope.org/repos/main/zLOG/README-trunk.txt:
"""
This package has been re-integrated into the Zope2 package. Maintenance
happens on the 2.11 branch and new development could occur inside
`Zope2/src/zLOG`.
"""
However, Zope 2.12, 2.13 and trunk still use the egg and the only
place it seems to exist in that package is at
/Zope/branches/2.11/lib/python/zLOG, presumably where it was moved
from during eggification.
I'm going to restore zLOG trunk by copying in the current 2.11 branch
so it can be fixed in a similar manner.
Laurence