Re: [Zope] HTTP Post Handler In Zope
Tom Purl schrieb:
> Hi everyone. I'm converting my personal web site from a Wordpress blog
> into a ZWiki wiki site. I transferred all of the content, and would like
> to create some "redirect pages" so that anyone visiting my old page url's
> would be redirected to their new home. So, if someone wanted to visit the
> following old, Wordpress url:
>
> http://mysite.com/?p=30
>
> ...the would get redirected to this ZWiki page:
>
> http://mysite.com/SomePageName
>
> The problem is that I'm not sure how I can "catch" the old url requests.
> I tried creating a Script (Python) object named "?", but Zope didn't let
> me use that name.
>
> Does anyone have any idea as to how to do this? Any help at all would be
> greatly appreciated!
You replace index_html with a python script with that name.
In this script you get p by
p=context.REQUEST.form.get('p','')
if p:
find old target via catalog? Return it or
redirect...
return usual content
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] HTTP Post Handler In Zope
Hi everyone. I'm converting my personal web site from a Wordpress blog into a ZWiki wiki site. I transferred all of the content, and would like to create some "redirect pages" so that anyone visiting my old page url's would be redirected to their new home. So, if someone wanted to visit the following old, Wordpress url: http://mysite.com/?p=30 ...the would get redirected to this ZWiki page: http://mysite.com/SomePageName The problem is that I'm not sure how I can "catch" the old url requests. I tried creating a Script (Python) object named "?", but Zope didn't let me use that name. Does anyone have any idea as to how to do this? Any help at all would be greatly appreciated! Tom Purl ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] standard_error_message in ZPT
Sam Boggess schrieb: > Does anyone know if it possible to rewrite the standard_error_message > in Page Templates? Yes. > And if so how do you reference the objects within the error message? > > error value Its options/error_value The object is called with named arguments - hence the options namespace in ZPT. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] standard_error_message in ZPT
Does anyone know if it possible to rewrite the standard_error_message in Page Templates? And if so how do you reference the objects within the error message? error value doesn't work. Thanks. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)
Jan-Ole Esleben wrote at 2005-12-16 12:40 +0100: > ... >However, as I see it, the problem is that what Zope actually _is_ >(i.e. mostly the ZODB) is an unhealthy way of coupling data and >implementation Coupling data and behaviour (what you might call "implementation") is the main feature of object orientedness. I find this very productive (especially multiple inheritance). Apart from that: for all solutions you have to make tradeoffs based on your aims. The ZODB aimed at ease of integration and ease of implementing simple multi-threaded applications (such as Web application servers). To make the second easier, it removed a major fault class: locking faults in application code. With the ZODB, you need not to worry about setting locks to make the modification of persitent objects safe. Because of that, you will usually not have problems with deadlocks or data inconsistencies due to forgotten locking. However, this ease has a price: the quite costly ZODB cache maintained for each connection in a connection pool. To limit RAM consumption, the ZODB versions before 3.4 had a limit on the number of connections in the pool. With ZODB 3.4, the number of connections are no longer limited. Connections exceeding the pool size become temporary connections the cache of which is destroyed when the connection is closed. Thus, you can now have a rather small number of ZODB connections (to hold RAM consumption in check) and a rather large number of workers to reduce the risk of deadlocks caused by resource exhaustion. If you are ready to modify ZServer a bit, you could even create workers on demand (usually, they are preallocated). However, this will cost you much of your control over resource usage... >(which is _exactly_ why my implementation didn't work >immediately). This of course comes from its origins in TTW development >where there wouldn't actually have been many user made products. I do not think that it has anything to do with TTW development. It is just that Zope did not target arbitrary web services implementations but much simpler web applications such as blogs, CMS, portals, ... This applications usually do have a precise notion of interior and exterior of themselves -- no need to call back to itself via HTTP rather than caller back directly. If you are smart (and you do not want to replace Zope by a different system altogether), then you will implement your own WebServices dispatcher -- one that recognizes when the call it in fact internal and then does make an internal call. If such calls are frequent, then you will gain performance as well. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: Leave the ivory tower now!
Andrew Sawyers wrote: On Sun, 2005-12-25 at 10:03 +0800, Bakhtiar A Hamid wrote: The 'closed group' dissolved a while ago. that's sad(?) anything came out of the group? i think we need to do to zope.org what we did to zope2. ignore and build. leave it as old.zope.org and link from the new site. That was the plan. I'd like to revive the plan. :) Volunteers? Andrew Count me in Michael -- http://zope.org/Members/d2m http://planetzope.org ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Leave the ivory tower now!
On Sun, 2005-12-25 at 10:03 +0800, Bakhtiar A Hamid wrote: > > The 'closed group' dissolved a while ago. > > > that's sad(?) anything came out of the group? i think we need to do > to zope.org what we did to zope2. ignore and build. leave it as > old.zope.org and link from the new site. > That was the plan. I'd like to revive the plan. :) Volunteers? Andrew ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Leave the ivory tower now!
> > > what's needed to spruce up the howtos, or zope.org? iirc, there was a > closed group with that mission setup some time back > > > It wasn't really 'closed' - just 'well defined'. It fell apart, due to both of the committed developers backing out due to commitments they couldn't get around. I am still highly interested in helping lead this and actually doing work if we had 1 or 2 others who were committed. We also already have a designer put in some time to assist with a "nicer" look and feel who is still willing to work on this. The goal was not to just 'spruce' things up, but rather change the focus of the site from everything to just Zope the software, Zope Documentation, and Zope Community. I was just talking about this on Christmas with someone, so there's still hope it will happen. Andrew Sawyers ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
