[Community] ZCO Style error more precisely (new error message)
Ludwig Max Brinckmann
ludwigbrinckmann at gmail.com
Tue Aug 29 00:19:54 EEST 2006
Do you still have any other ZCO data stores defined? If so, could you try to
delete them? I somehow have the feeling that at the point where the error
occurs (trying to edit a layer) Primagis tries to populate a drop down box
from the list of ZCO datastores and since one of them is somehow corrupt,
creating the drop down list fails and then Zope fails to produce the page.
I would maybe just try it with one simple shapefile, if you have one, rather
then doing the trickery with the ovf file.
Ludwig
On 8/28/06, Gérard Vidal <Gerard.Vidal at inrp.fr> wrote:
>
> I have tried your proposal.
> Everything goes well in the zco creating process (at the end I can see
> the layer, I use the world map ovf from the demo) but the primaGIS
> layer creation fails with the following error . I can add with no
> problem a scale bar and access to a view.
>
> Traceback (innermost last):
> Module ZPublisher.Publish, line 114, in publish
> Module ZPublisher.mapply, line 88, in mapply
> Module ZPublisher.Publish, line 40, in call_object
> Module Products.CMFFormController.FSControllerPageTemplate, line 102,
> in __call__
> Module Products.CMFFormController.BaseControllerPageTemplate, line 46,
> in _call
> Module Shared.DC.Scripts.Bindings, line 311, in __call__
> Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec
> Module Products.CMFCore.FSPageTemplate, line 195, in _exec
> Module Products.CMFCore.FSPageTemplate, line 134, in pt_render
> Module Products.PageTemplates.PageTemplate, line 104, in pt_render
> - <FSControllerPageTemplate at /test/base_edit used for
> /test/test/test/primagislayer.2006-08-28.1889426998>
> Module TAL.TALInterpreter, line 206, in __call__
> Module TAL.TALInterpreter, line 250, in interpret
> .../...
> Module TAL.TALInterpreter, line 406, in no_tag
> Module TAL.TALInterpreter, line 250, in interpret
> Module TAL.TALInterpreter, line 734, in do_defineSlot
> Module TAL.TALInterpreter, line 250, in interpret
> Module TAL.TALInterpreter, line 477, in do_setLocal_tal
> Module Products.PageTemplates.TALES, line 221, in evaluate
> - URL: file:Archetypes/skins/archetypes/widgets/selection.pt
> - Line 113, Column 12
> - Expression: <PythonExpr field.Vocabulary(here)>
> - Names:
> {'container': <PloneSite at /test>,
> 'context': <PrimaGISLayer at
> /test/test/test/primagislayer.2006-08-28.1889426998>,
> 'default': <Products.PageTemplates.TALES.Default instance at
> 0x01327C10>,
> 'here': <PrimaGISLayer at
> /test/test/test/primagislayer.2006-08-28.1889426998>,
> 'loop': <Products.PageTemplates.TALES.SafeMapping object at
> 0x06BBC3C8>,
> 'modules':
> <Products.PageTemplates.ZRPythonExpr._SecureModuleImporter instance at
> 0x0131C288>,
> 'nothing': None,
> 'options': {'args': (),
> 'state':
> <Products.CMFFormController.ControllerState.ControllerState object at
> 0x06D3E970>},
> 'repeat': <Products.PageTemplates.TALES.SafeMapping object at
> 0x06BBC3C8>,
> 'request': <HTTPRequest,
> URL=
> http://localhost:9090/test/test/test/primagislayer.2006-08-28.1889426998/base_edit
> >,
> 'root': <Application at >,
> 'template': <FSControllerPageTemplate at /test/base_edit used for
> /test/test/test/primagislayer.2006-08-28.1889426998>,
> 'traverse_subpath': [],
> 'user': admin}
> Module Products.PageTemplates.ZRPythonExpr, line 47, in __call__
> - __traceback_info__: field.Vocabulary(here)
> Module Python expression "field.Vocabulary(here)", line 1, in
> <expression>
> Module Products.Archetypes.Field, line 441, in Vocabulary
> TypeError: unsubscriptable object
>
> Ludwig Max Brinckmann a écrit :
> > Sorry, I have not followed this in its entirety, but I think the
> > problem you have run into is that the PrimaGIS map uses symbolizers in
> > ZCO that are for whatever reason corrupt or illdefined. Because the
> > Primagis map tries to find ZCO symbolizers or datastores that are not
> > there or do not work, it throws up some index exception and
> > unfortunately that also disables your ability to edit the layer as
> > they require these objects to be editable....(that's why if you define
> > the symbolizers with other data you get a bit further, as it now finds
> > the names)
> >
> > I have in the past run into trouble similar to this and the demo has a
> > certain vulnerability to this.
> >
> > My approach has been not to install the demo, but to try to build a
> > PrimaGIS map from scratch by hand, i.e. first define a simple
> > datastore in ZCO and its symbolizers, perhaps starting with a
> > shapefile, and defining a simple symbolizer for it and then to define
> > a PrimaGISLayer on top of this.
> >
> > I can assure you that once through these teething troubles, things get
> > easier...
> >
> > I am not running anything on windows at the moment, so I cannot help
> > you with this, but let me know if building a map by hand works better
> > than the demo...
> >
> > Ludwig
> >
>
>
> --
> Gérard Vidal
> Directeur ERTé ACCES INRP-ENS
> 19 Mail de Fontenay
> 69347 Lyon Cedex 07
> e-mail Gerard.Vidal at inrp.fr
> tél : (0)4 72 76 62 00
> "Si la matière grise était rose, personne n'aurait plus d'idées noires."
> Pierre Dac
>
> _______________________________________________
> Community mailing list
> Community at lists.gispython.org
> http://lists.gispython.org/mailman/listinfo/community
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gispython.org/pipermail/community/attachments/20060828/17993d3b/attachment.htm>
More information about the Community
mailing list