Re: Migrating content - an alternative approach

GET requests and long URL are not suitable for accepting an arbitrary
amount of junk data. Especially Zope performs a validation on the length
of the HTTP header which may not exceed 8192 chars by default.

-aj

Espen Moe-Nilssen wrote:
> Hi
> 
> I have made a browser view ( https://github.com/espenmn/medialog.lxml/ )
> to migrate/copy content to Plone. It is using lxml (with setting for «safety»)
> 
> It works like this
> http://plonesite/folder/@@createpage?url=http://path/to/some/content&selector=#id_or_class
> 
> This works as planned. It creates a Plone page with bodytext from CSS selector of external page
> I am now thinking about making a browserview that can take a list of URLs (the sitemap, maybe)
> 
> What would be the right approach to call several  views in a row (programically)
> like this
> 1) http://plonesite/folder/createpage?url=someurl
> 2) http://plonesite/folder/createpage?url=anotherurl
> 3) etc
> 
> (hopefully continuing with the next if «something goes wrong)
> 
> Espen
> ------------------------------------------------------------------------------
> Slashdot TV.  
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/



------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/