I'm still using a webpage with Plone 2.0.5, but now it's time to change to a newer version of Plone (4.3.11). In my old Plone installation I have an "Extensions-Folder" in /opt/Zope-2.7.8/instance1/Extensions, but I can't find that folder en 4.3.11. Do I have to create it? Where?
Maybe in /opt/Plone/zeocluster/parts/client1/ and /opt/Plone/zeocluster/parts/client2/, or in /opt/Plone/zeocluster/parts/zeoserver/ ??? I don't know where...
External methods (i.e. the scripts inside Extensions folder) are deprecated and currently recommended to be replaced by a browser view inside one of the project's packages.
but if you really need to. Then you can create it at <buildout_dir>/parts/<instance_name>/Extensions
where <instance_name> is probably just "instance"!
I did it in order to use collective.jsonify on a (Development) Plone 4.1 instance this week - still works.
BUT this is old tech, there maybe security issues with using this in Production
But Plone isn't searching External Methods in this directory (after buildout and restart). But after creating a filesystem link in ${buildout:directory}/parts/client1/Extensions it works. So it seams that the configuration line doesn't work. Why not?
Maybe because couldn't find a [instance] group, therefore I inserted it in [instance-base] group...
Do I have to create a[instance] group in base.cfg?
I tested and it works. You may check if there's a line starting with "extensions" in parts/client1/etc/zope.conf and whether it points to the desired folder.
The name of the section doesn't matter as long as it's controlled by the plone.recipe.zope2instance recipe. Btw see:
No, syntax is correct, as you can see if you look for zope-conf-additional in the first link I sent. Did you run buildout after making those changes? If so could you please post your CFG files here?