Grok finds my static folder in a flat product

Question

I found that in the Plone installation, where 1.2.0 five.grok is installed, I just had to have a “static” folder in my egg source, and grok would register it accordingly.

When I switched to environment with 1.3.0 five.grok installed, this static folder was not registered. I can of course register it explicitly in the configure.zcml file, which works fine. Checking the source code for five .grok really has something to do with this: the StaticResourcesGrokker class has been removed from meta.py between 1.2.0 and 1.3.0 from five.grok.

I'm just trying to figure out if there is a new way to have a static folder registered in the "grok way", or am I just going back to using explicit registration in the configure.zcml file?

Answer 1

I have no explanation why such a convenient feature has disappeared. All I could find was fixing diff:

http://svn.zope.org/five.grok/trunk/src/five/grok/meta.py?rev=123298&r1=112163&r2=123298

As you can see from diff, the StaticResourcesGrokker class was destroyed during the merge with sylvain-zope213. (sic), no comment.

Until this function is restored, it is best to manually register a static folder.

Answer 2

Perhaps the answer is here:

• http://grok.zope.org/doc/1.3/upgrade.html

Quote:

" DirectoryResource . Fanstatic WSGI.