Re: Silva 1.5 beta 1 released

Marc Petitmermet wrote:
> well, i gave it a first try.

Thanks for all the great feedback!

> 1. the button "install default layout" on /silva/service_extensions  
> throws an error: 404 – document not found

Oops, perhaps I threw away too much logic somewhere when working on 
removing old layout related code! I will make an issue for this. Issue 1479

> 2. kupu: there isn't a margin anymore between the left browser window  
> border and the text in kupu; the text is glued to the left border.  
> (firefox-1.5)

issue 1481


> 3. smi > properties: the element name for "Language of content in  this 
> area" should be "language" and not "description".

Issue 1480

> 4. kupu: i don't have spell checking software installed. sometimes i  
> get an "error loading, status 500" window and sometimes, mostly when  i 
> have selecte some text before clicking on the icon, the content of  kupu 
> is loaded into a new browser window. it would be much nicer when  there 
> would be a message similar to "spell checking not available".  there are 
> lots of broken pipe errors in the error_log of zope.

We are thinking of just plain disabling spellchecking in Kupu -- it's an 
immature feature that we should never have enabled just like that.

Issue 1482

> 5. kupu > edit html code: does not work. the toolbox moves completely  
> to the left.


Argh, another kupu issue: 1483

> 6. smi: the lookup screen of a ghost gives a zope error (reference  
> button of ghost object):
>   Error Type: NameError
>   Error Value: global name 'IContent' is not defined
> traceback: see [1]

Import problem. I'll let Eric fix this, as it's his bug. :) Issue1484

> 7. smi: the lookup screen of a ghost folder gives a zope error  
> (reference button of ghost object):
>   Error Type: NameError
>   Error Value: global name 'IContent' is not defined
> traceback: see [2]

Same issue, I expect.

> 8. kupu: get links reference and selecting a ghost folder gives a  zope 
> error:
>   Error Type: AttributeError
>   Error Value: getPhysicalPath
> traceback: see [3]

> 9. kupu: get links reference and selecting a ghost folder in a ghost  
> folder gives a zope error:
>   Error Type: AttributeError
>   Error Value: unrestrictedTraverse
> traceback: see [4]


More lookup window errors...  See 1485

> 10. smi: silva shouldn't allow broken ghosts to be published.

Hm, some questions about this one.. was this impossible before and how 
is it now possible? I.e. is this a new Silva 1.5 problem? Please discuss 
at issue 1486

> 11. smi: i thought that we got rid of the "unknown author" a long  time 
> ago;-) but when i create a ghost by copy a document and pasting  as 
> ghost the author is "unknown" in the content screen. in the  properties 
> tab the creator is set correctly and the last author is  the author of 
> the ghosted document. in the publish screen the last  author is also 
> "unknown", the creator is correct. and this remains  the same even after 
> publishing, editing, republishing, etc.

Hm, again, I wonder whether this is a new issue or an existing one. Code 
didn't change in this area.

> 12. smi: extfile seems to be partially working with zope-2.8.5  
> (https://infrae.com/issue/silva/issue1433). silva image uploading is  no 
> problem but silva file uploading returns an error:
>   Error Type: NameError
>   Error Value: global name 'return_url' is not defined
> traceback: see [5]

Which version of extfile are you using? Latest svn version from the 
Plone collective? I added your report to the issue you mentioned.

> 13. smi: trying to renaming a published document gives a strange  message:
>   «${item}» could not be renamed
> silva shouldn't even allow the user trying to rename a published  document.

That's why it says 'could not be renamed'. The message is the same, but 
this is an i18n related change. The fix is easy, I expect we'll get a 
few more here and there.

> 14. smi: renaming a closed document gives the same message:
>   «${item}» renamed successfully    (20 jan 06 01:31)
> or «${item}» renamed successfully, «${item}» renamed successfully, «$ 
> {item}» renamed successfully    (20 jan 06 01:33)

And here are the few more places. I expect there are some more. Just 
report them in issue 1488 and I'll fix 'm.

> 15. smi: nitpicking here;-) why does the "Kupu Editor" button not  have 
> an elipsis like the other buttons? i thought that in english  everything 
> should be lowercase (https://infrae.com/issue/silva/msg7532)

Issue1489

> 16. smi > properties: the properties screen does not behave as  
> expected. i have the SilvaRendererDemo product installed. therefore,  
> when clicking on the "settings..." button in the properties screen it  
> should change to "back..." and give me a change to get back to the  
> initial properties screen.
> 
> 17. smi > properties: same as 16. but for the "addables..." button.  
> this would make it consistent to the user lookup screen.

Issue 1490

> i also tried to upgrade content from silva-1.4. the content upgrade  
> from 1.4 to 1.5 passed without errors after i have removed the  
> silvaexternal source and silvanews products. 

Note that SilvaExternalSource checked out from CVS should work with 
Silva 1.5. We still need to pull a release for that. SilvaNews needs a 
bit more (shallow) work to be 1.5 compatible.

> of course quite a few  
> documents throw errors now because of the missing products. trivial  
> content seems to have been upgraded without problems and are fully  
> editable, preview-able and publishable. i cannot test my custom  layouts 
> because the all rely on silvaexternal source and/ or silva  news and 
> therefore throw nasty errors.
> 
> i like the added "publishing actions" in the contents screen and  these 
> intelligent "close/ publish now" buttons (you should add this  to the 
> history.txt file).

True. I keep reminding everybody we need to do that. :) I'll add an 
issue for that too:

issue1491

Thanks again for all the valuable feedback! We obviously have some 
bugfixing to do!

Regards,

Martijn