Just chatted with davisagli on #plone and he's going to check to see if the static resources change is accidental or intentional.
However, the need to specify grok and relations options is intentional. The Framework Team wanted to bring Dexterity into Plone, but didn't want to bless grok into core. So, it's an optional, but well-supported, development path. On Mon, Feb 25, 2013 at 11:05 PM, Serge Renfer <[email protected]>wrote: > Hello, > > I gave a try to Plone 4.3b2 and tried to install a product I made with > Dexterity (ageliaco.rd2), but I couldn't get the static ressource folder to > be recognized (as a ressource). > > I googled around and found only one person talking about that : > > http://stackoverflow.com/questions/8315422/grok-finding-my-static-folder-in-a-plone-product > > It comes from a change from five.grok 1.2.0 to 1.3.2, the latest doesn't > do what it is advertised it should do : it does not register the "static" > folder as it should! > > Is this a new "feature" of five.grok and it is gonna stay that way, or is > it a bug! > If it is the first case, then its documentation should be updated to > reflect that. Otherwise has someone heard of some new version in > preparation? > > By the way, dexterity seems to have dropped grok in some way (I have to > change the required dependencies in setup.py from "dexterity" to "dexterity > [grok, relations]". > Why is that? Is it to get it lighter (there must be ways to use it without > grok, probably TTW? Then it makes sense) > > Thanks in advance! > serge > > _______________________________________________ > Product-Developers mailing list > [email protected] > https://lists.plone.org/mailman/listinfo/plone-product-developers > >
_______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
