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

[Laurence R. <l...@lr...>]

On 30 July 2011 22:05, Giacomo Spettoli <gia...@gm...> wrote:
> On 30/07/2011 22:40, Laurence Rowe wrote:
>
> On 30 July 2011 21:19, Giacomo Spettoli <gia...@gm...> wrote:
>
> On 30/07/2011 21:42, Laurence Rowe wrote:
>
> 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)
>
> I used official downloadable themes from Plone.org for testing as (as
> Zip Downloads):
> plonetheme.evergreen
> plonetheme.darkened
> plonetheme.discovery
> plonetheme.burned
> plonetheme.bananaleaf
> plonetheme.leavesdew
>
> My Configuration:
>
> Plone:
>        • Plone 4109
>        • CMF 2.2.4
>        • Zope 2.13.8
>        • Python 2.6.7 (r267:88850, Jul 29 2011, 10:54:55) [GCC 4.2.4 (Ubuntu
> 4.2.4-1ubuntu4)]
>
> plone.app.theming
>        • plone.app.theming 1.0b5
>                • Diazo theme support 1.0b5
>                • Static resource storage 1.0b4
>
> extends =
> ...
>     http://good-py.appspot.com/release/plone.app.theming/1.0b8
> ...
>
> I could import themes without activating "Immediately enable new theme"
> When selecting a theme in "Basic settings" with or without "Enable
> theme"
> I got:
> Traceback (innermost last):
>
>     Module ZPublisher.Publish, line 126, in publish
>     Module ZPublisher.mapply, line 77, in mapply
>     Module ZPublisher.Publish, line 46, in call_object
>     Module plone.app.theming.browser.controlpanel, line 35, in __call__
>     Module plone.app.theming.browser.controlpanel, line 68, in update
>     Module plone.app.theming.utils, line 431, in applyTheme
>     Module plone.registry.recordsproxy, line 43, in __setattr__
>
> 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
>
> ------------------------------------------------------------------------------
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> _______________________________________________
> Plone-developers mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
> Well actually could also be my fault (since i'm the author of all these
> theme, the plone side at least). I've checked that traceback with code and i
> realized that i've forgot to specify the doctype in all rules.xml. I have
> already done a new release for all my themes with that fix. Hope that this
> fix the problem.
>
> So long as your theme uses the default XHTML 1.0 transitional doctype,
> you don't need to specify a doctype in manifest.cfg.
>
> This error occurs because the information stored in the configuration
> registry changed and the upgrade step has not yet been run, it has
> nothing to do with anything in a theme.
>
> Laurence
>
> You're right Laurence, but i was not referring to manifest.cfg, but to
> rules.xml where the first line should be (and now it is) "<?xml
> version="1.0" ...>". Maybe that's not the source of the problem but still
> it's a little error fixed :)

That's not a doctype, it's an "XML declaration". A doctype begins
"<!DOCTYPE.." and would come after the optional XML declaration in an
XML document. Diazo does not require either for the rules.xml file.

Laurence

Laurence