Re: [Plone-developers] AttributeError: doctype – when activating theme in Diazo Control panel of plone.app.theming 1.0b8 with Plone4.1

[Armin Stroß-R. <dev...@ac...>]

Hi Laurence, Hi Giacomo,
Am 30.07.2011 um 21:42 schrieb Laurence Rowe:

> On 30 July 2011 18:25, Armin Stroß-Radschinski <dev...@ac...>  
> wrote:
>> When doing a curiosity import of zipped themes into a vanilla Plone
>> 4.1 Diazo import dialog for documentation purposes I got the  
>> following
>> error "AttributeError: doctype" (current not found via Google)
...
>> AttributeError: doctype
>
> This sounds like you upgraded the version of plone.app.theming but did
> not run the migration step on the site. Go to the Add-ons control
> panel and click upgrade next to plone.app.theming.
>
> Laurence


Thanks Laurence for a pointer for the blind.

Everything now working as expected. That was a very poor mistake.
Hope Giacomo takes his effort to improve his files not as a pain.


Armin


Some crude ideas I may post on http://plone.uservoice.com/

UI improvement to lead to better user understanding of errors.
===================================================

First of all: Today it is a lot easier to find well known error  
Messages in Plone and contribute a solution documentation.
http://plone.org/documentation/error
http://readthedocs.org/docs/collective-docs/en/latest/troubleshooting/exceptions.html
http://readthedocs.org/docs/collective-docs/en/latest/introduction/writing.html

A suggestion for improving the debugging process for newcomers I take  
from this:
In the traceback displayed in the UI - Plone could provide this  
information automatically as a suggest:

1. Links to these ressources and a motivational text to conribute to  
these ressources:

2. As a result for this case:
Scan for any add ons or parts of the software, that display an obvious  
waiting of the system for missing useraction or update and display  
them as a list by default or via a link in the traceback page.

3. Prefacing "ToDo" List for topics rated "important" on top of the  
add on installer Page, like the current Update suggest for Plone  
itsself.

3rd Party Updates installed by buildout that need migrations should be  
able to hold a "untouched" flag like the "safe download" database in  
MacOSX until the necessary migrations are finished. The Quickinstaller  
still provides this in a more general form, but there are some cases  
where we need more info at the right place saving support time. Maybe  
I am overseeing something that is already present.

No idea for now how to implement this. Need to gain access to  
collective / collective.github.com first and scan PLIPs or http://plone.uservoice.com/ 
  first.


--
Armin Carl Stroß-Radschinski, Dipl. Designer
acsr industrialdesign, Landgrafenstraße 32, 53842 Troisdorf, Germany

Telefon +49 (0) 22 41 / 94 69 94, FAX +49 (0) 22 41 / 94 69 96
eMail a.s...@ac... - http://www.acsr.de
UST. ID Nr: DE154092803 (EU VAT ID)