Re: plone.app.widgets and Plone 4.3.3

Peter Mathis <[email protected]>
Newsgroups gmane.comp.web.zope.plone.user
Message-ID <[email protected]>
yes, this gets close as well ...
unfortunately plone.formwidget.autocomplete isn't compatible with jquery >= 1.9
and you have to pin plone.app.discussion to 2.2.13 (2.3.3 isn't 
released yet .. see 
https://github.com/plone/plone.app.discussion/blob/master/CHANGES.rst)



On 2014-10-10 08:34:50 +0000, Johannes Raggam 
<[email protected]> said:

> 
> 
> 
> 
> I got it to work with the latest plone.app.widgets from github.
> TinyMCE's image and link popups do work, but I couldn't upload images.
> So there might still be some issues left.
> 
> [sources]
> plone.app.widgets =3D git 
> git-9UaJU3cA/F/[email protected]:plone/plone.app.widgets.git
> Products.CMFPlone =3D git 
> git-9UaJU3cA/F/[email protected]:plone/Products.CMFPlone.git 
> branch=
> =3D4.3.x
> # not strictly necessary. latest p.a.widgets should also go with plone.app.=
> event 1.2.x
> plone.app.event =3D git 
> git-9UaJU3cA/F/[email protected]:plone/plone.app.event.git
> 
> [versions]
> zc.buildout =3D >=3D 2.2.1
> setuptools =3D >=3D 2.2
> plone.app.jquery =3D >=3D 1.9.1.2
> plone.app.jquerytools =3D >=3D 1.6.1
> 
> # plone.app.event > 2.0 dependencies
> plone.app.portlets =3D 2.5.2
> z3c.form =3D 3.2.1
> plone.app.vocabularies =3D 2.1.16
> plone.app.querystring =3D 1.2.2
> 
> 
> 
> 
> 
> On Thu, 2014-10-09 at 16:06 +0200, Peter Mathis wrote:
>> Thanks Andreas!
>> That indeed helped me out.
>> I list the versions I've pinned.
>> The rest is from 4.3-latest/versions.cfg
>> =20
>> [versions]
>> plone.app.contenttypes =3D 1.1b3
>> plone.app.event =3D 1.1.2
>> plone.app.jquery =3D 1.8.3
>> plone.app.portlets =3D 2.5.1
>> plone.app.widgets =3D 1.4.0
>> =20
>> Everything is up and running ...
>> =20
>> =20
>> =20
>> =20
>> Andreas Jung schrieb:
>>> 
>>> This is our  version.cfg that works with plone.app.contenttypes,
>>> plone.app.widgets and plone.app.event under Plone 4.3.3. All
>>> other combinations with newer versions had issues in one way or the
>>> other. I also recall issues with TinyMCE.
>>> 
>>> -aj
>>> 
>>> [versions]
>>> geopy=3D0.95.1
>>> plone.app.layout =3D 2.3.9
>>> plone.app.portlets =3D 2.5.1
>>> Pygments =3D 1.6
>>> z3c.unconfigure =3D 1.0.1
>>> ZopeSkel =3D 2.21.1
>>> zopeskel.dexterity =3D 1.5.4.1
>>> zc.buildout =3D 2.2.1
>>> setuptools =3D 2.2
>>> #plone.app.event =3D 1.2.4
>>> #plone.app.widgets =3D 1.5.0
>>> plone.app.event =3D 1.1.2
>>> plone.app.widgets =3D 1.4.0
>>> plone.app.contenttypes =3D 1.1b2
>>> fs =3D 0.4.0
>>> pep8 =3D 1.5.7
>>> plone.app.testing =3D 4.2.4
>>> 
>>> Peter Mathis wrote:
>>>> Hey there,
>>>> i'd really like to use p.a.event[dexterity] and p.a.widgets in Plone
>>>> 4.3.3 but unfortunately TinyMCE is broken (link and image dialog popup=
> s
>>>> throw "e.tiny is undefined" JS error)
>>>> 
>>>> I came across this thread https://github.com/plone/mockup/issues/395 a=
> nd
>>>> tried to use p.a.widgets with my own mockup bundle and
>>>> https://github.com/jquery/jquery-migrate but again I ran out of luck .=
> ..
>>>> tinymce ++plone++ resources weren't found ... gosh
>>>> 
>>>> next thing was to pin down versions to p.a.widgets 1.5.0 and p.a.event=
>  <
>>>> 2.0 but no working TinyMCE ... same JS error "e.tiny" undefined ...
>>>> (/&%$=C2=A7"!%
>>>> 
>>>> so my question dear fellow developers:
>>>> what do we need for releases of p.a.event|p.a.widgets which simply run=
> s
>>>> OOTB on Plone 4.3.3
>>>> 
>>>> I'm willing to put all my efforts in this :)
>>>> 
>>>> regards
>>>> petschki
>>>> 
>>>> 
>>>> ----------------------------------------------------------------------=
> --------
>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Repor=
> ts
>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=3D154622311&iu=3D/4140/o=
> stg.clktrk
>>> 
>>> 
>>> 
>>> -----------------------------------------------------------------------=
> -------
>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Report=
> s
>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>> http://pubads.g.doubleclick.net/gampad/clk?id=3D154622311&iu=3D/4140/os=
> tg.clktrk
>>> 
>> =20
>> =20
>> =20
>> -------------------------------------------------------------------------=
> -----
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> http://pubads.g.doubleclick.net/gampad/clk?id=3D154622311&iu=3D/4140/ostg=
> .clktrk
>> _______________________________________________
>> Plone-Users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/plone-users
> 
> --=20
> programmatic  web development
> di(fh) johannes raggam / thet
> python plone zope development
> plone framework  team  member
> mail: office-//[email protected]
> web:  http://programmatic.pro
>       http://bluedynamics.com
> 
> 
> 
> This message has one or more attachments. Select "Save Attachments" 
> from the File menu to save.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2




------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.