KupuPopupWindow: usage in public forms, SilvaMetadata, etc.

[Marc Petitmermet]

I would like to use an embedded version of KupuPopupWindow (and not tinymce) in public forms. The advantage would be to automatically get valid silva-xml data which can then be used in the backend to create silva documents if needed.

[Andy Altepeter (aaltepet)]

It would also be nice to be able to use the kupupopupwindow on the properties tab, in SilvaMetadata.

[Andy Altepeter (aaltepet)]

Marc has also reported the following related to the KWP:

> is there a possibility to disable the "get link reference..." button
> in the link tool box? on a public page i don't always want users to
> have access to the silva innards.

I understand what you're saying here, but I think the development effort would be too much. The "get link reference..." button is very tightly coupled with the link tool.

> the second time i click on the edit button, after saving inbetween,
> the selection of toolboxes made in the zmi is ignored; all are shown.

Is this still happening? I'm not able to reproduce.

[Marc Petitmermet (petitmermet)]

On 01. Dez 2009, at 05:01 Uhr, Andy Altepeter wrote:

> Marc has also reported the following related to the KWP:
>
>> is there a possibility to disable the "get link reference..." button
>> in the link tool box? on a public page i don't always want users to
>> have access to the silva innards.
>
> I understand what you're saying here, but I think the development effort
> would be too much. The "get link reference..." button is very tightly
> coupled with the link tool.
>
>> the second time i click on the edit button, after saving inbetween,
>> the selection of toolboxes made in the zmi is ignored; all are shown.
>
> Is this still happening? I'm not able to reproduce.

sorry, cannot test because the svn checkout of the Formulator trunk version does not work with buildout Silva-2.1.7:

   Formulator/Form.py", line 6, in ?
      from App.class_init import InitializeClass
   ImportError: cannot import name InitializeClass

which version of Formulator should i use for testing with Silva-2.1.7?

regards,
marc

[Kit Blake (kitblake)]

I think Formulator 1.12 will work with Silva 2.1.x, but Andy has been steering the Formulator ship lately. In the buildout I believe it's earlier:
{silva-all:base}/Formulator/tag/Formulator-1.11.5 Formulator

[Andy Altepeter (aaltepet)]

Actually, 1.11.6 is the latest formulator tag for Silva 2.1. I believe Formulator 1.12 will work, but there is no tag for that yet -- officially it is the version for Silva 2.2.

[Marc Petitmermet (petitmermet)]

On 01. Dez 2009, at 20:12 Uhr, Andy Altepeter wrote:

> Actually, 1.11.6 is the latest formulator tag for Silva 2.1. I believe
> Formulator 1.12 will work, but there is no tag for that yet --

and Formulator 1.12 does not contain the KupuPopupWindow field

> officially it is the version for Silva 2.2.

i have now a working buildout with Silva 2.2b1. in short: KupuPopupWindow does not work.
as soon as i click on the edit button a window opens and it shows kupu with the following content:

  Sorry
  An error happened while processing your request.

in the error_log:

Request URL http://localhost:8090/silva22/index/kupu_popup_iframe
Exception Type KeyError
Exception Value 'frontend.css'

Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module Products.Five.browser.metaconfigure, line 417, in __call__
  Module Shared.DC.Scripts.Bindings, line 313, in __call__
  Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
  Module Products.PageTemplates.PageTemplateFile, line 126, in _exec
  Module Products.PTProfiler.ProfilerPatch, line 83, in __patched_render__
  Module Products.PageTemplates.PageTemplate, line 98, in pt_render
  Module zope.pagetemplate.pagetemplate, line 115, in pt_render
  Module zope.tal.talinterpreter, line 271, in __call__
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 379, in do_startEndTag
  Module zope.tal.talinterpreter, line 408, in do_startTag
  Module zope.tal.talinterpreter, line 485, in attrAction_tal
  Module Products.PageTemplates.Expressions, line 206, in evaluateText
  Module zope.tales.tales, line 696, in evaluate
   - URL: index
   - Line 4, Column 2
   - Expression: <PathExpr standard:'context/frontend.css/absolute_url'>
   - Names:
      {'container': <Silva Document instance index>,
       'context': <Silva Document instance index>,
       'default': <object object at 0x100374200>,
       'here': <Silva Document instance index>,
       'loop': {},
       'nothing': None,
       'options': {'args': (<Products.Five.metaclass.SimpleViewClass from /Applications/Silva/buildout-trunk/devel/Products.Silva/Products/Silva/browser/kupu_popup_iframe.pt object at 0x107aee550>,)},
       'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x107a2eab8>,
       'request': <HTTPRequest, URL=http://localhost:8090/silva22/index/kupu_popup_iframe>,
       'root': <Application at >,
       'template': <ImplicitAcquirerWrapper object at 0x107af2110>,
       'traverse_subpath': [],
       'user': <User 'admin'>,
       'view': <Products.Five.metaclass.SimpleViewClass from /Applications/Silva/buildout-trunk/devel/Products.Silva/Products/Silva/browser/kupu_popup_iframe.pt object at 0x107aee550>,
       'views': <zope.app.pagetemplate.viewpagetemplatefile.ViewMapper object at 0x107af2310>}
  Module Products.PTProfiler.ProfilerPatch, line 32, in __patched_call__
  Module zope.tales.expressions, line 217, in __call__
  Module Products.PageTemplates.Expressions, line 131, in _eval
  Module zope.tales.expressions, line 124, in _eval
  Modu...

[Andy Altepeter (aaltepet)]

Marc,

The kupupopupwindow is in the Silva product (Products/Silva/kupupopupfield.py), not Formulator, since it is a silva-only Formulator field.

It looks like a recent change to the Silva core removed the install of the zodb-based layout components during the initial install of Silva (e.g. <silva_root>/[frontend.css, layout_macro, etc]). These apparrently now fully replaced by silva.core.layout and related modules. I've fixed the kupu_popup_iframe so it loads frontend.css from the correct location.

[Kit Blake (kitblake)]

Andy, by "loads frontend.css from the correct location", you mean calling it from the globals dir? It won't disappear from there. And the one in the root just imported frontend.css from globals.

[Andy Altepeter (aaltepet)]

Hi Kit, yes, I mean that the popupkupu iframe now loads frontend.css from globals.

[Sylvain Viollon (thefunny)]

There is no longer anymore Kupu support in Silva 3.0.