Re: files service, kupu, etc.

Hey,

It's good to be getting some feedback, though a bit unfortunatele it 
happened after 1.0 final was released... :)

Marc Petitmermet wrote:

> files service
> -------------
> we were used to be able to have multiple file repositories. i have added 
> several files service in different folders but silva-1.0 does not care 
> about it. do i have to setup Config.py of ExtFile specifically for this 
> task?

This looks like a dropped feature when the system got revised. I'll add 
an issue about it. Issue1023.

> kupu
> ----
> - kupu does not yet support complex lists. i fear that my complex lists 
> get destroyed when users start using kupu...

Not a very extensive description about what happens. Created issue 1024.

> - i still have this problem with cropped images. insert an image into a 
> document and save it. then crop the imported image. go back to the 
> document and there is still the previous version of the image in kupu 
> (but it's the correct cropped version in the forms editor and the 
> preview tab). remove the image and insert it again; there is still not 
> the cropped image. but when you insert the same document into a 
> different document: voilà, the cropped version appears!
> the only workaround i have found so far: go to the forms editor, make a 
> shift-reload of the page and then go back to kupu; now the cropped 
> version is here. but this workaround does not always work. e.g. i could 
> not get the correct image into kupu after uncropping the image, reload 
> the page in the forms editor and then move to kupu. (same problems in 
> mozilla-1.6, 1.7, 1.8a2, macosx)
> - buttons are not yet stateful with lists.

What does this mean? What is a stateful button?

> force upgrade
> -------------
> how can i force an upgrade of silva content? e.g. i move silva-0.9.3 
> content form one server to a different one where silva-1.0 is installed 
> and my content is not imported in the silva root but in a sub 
> publication...

This is not a supported feature of the upgrade process. The upgrade 
process can only upgrade a *whole* Silva 0.9.3 root to Silva 1.0. Doing 
partial upgrades is not recommended - there may be references in the 
Silva root (such as the catalog, groups) the chance of breaking 
something is increased.

If you want to do something like this, use XML export from the old 
server and import into the new one. Unfortunately, the XML format is 
currently incomplete (does not carry assets, for instance). For 1.1 we 
have some XML export/import improvements in the pipeline that should 
make the the export format far more complete.

> typo
> ----
> found a small typo in an error message of the cropping feature:
> "'0x146-50x196' defines an impossible croping"
> this should be "cropping"

Fixed.

Thanks,

Martijn