Re: [Zope-dev] breaking apart INSTANCE_HOME.
Am Freitag, 25. Juli 2003 15:52 schrieb Chris McDonough: I propose that we add two more options to the config file: import-directory extensions-directory This is a VERY good idea. And allow import to be made from an installed product similar to the way external scripts work. And let it find its extension automatically. So we could we could import the file myImport.zexp that resides in Products/MyProduct/import as MyProduct.myImport -- mit freundlichen GrĂ¼ssen Robert Rottermann www.redCOR.ch ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: CVS: Zope/lib/python/TAL - TALGenerator.py:1.65
Hi! Chris McDonough wrote: Hmm. Without this fix, many CMFDefault (and possibly CMFCore) skins don't work. Is there a way to fix the offending CMF skins so that it works under Zope versions both with this fix and without (so we don't need two versions of CMF)? More importantly, is anyone willing to actually do this work? CMFCore has no skins. CMFDefault is the only product in cvs.zope.org:/cvs-repository/CMF using i18n. CMFDefault has just one template using this pattern: index_html_utils.html uses i18n:attributes=alt title So it would not be much work to change CMF. I'm not talking about third party products building on top of CMF. Plone was already discussed, I don't know what's the case with other products. What about backporting the i18n fix to Zope 2.6.2 ? Using CMF / Plone with i18n support requires Zope 2.6.0 anyway. Maybe we could force people updating CMF / Plone also to update Zope to 2.6.2. This way CMF / Plone could switch to the new spec. Just my 2 cents. Yuppie ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: CVS: Zope/lib/python/TAL - TALGenerator.py:1.65
On Sat, 2003-07-26 at 04:21, Yuppie wrote: CMFCore has no skins. CMFDefault is the only product in cvs.zope.org:/cvs-repository/CMF using i18n. CMFDefault has just one template using this pattern: index_html_utils.html uses i18n:attributes=alt title Sorry for overstating the problem. So it would not be much work to change CMF. Can it be changed in such a way that it works under 2.6.2, 2.7, and HEAD without the fix? It'd be a shame to require that people upgrade to a new version of CMF and/or Zope for one skin. I'm not talking about third party products building on top of CMF. Plone was already discussed, I don't know what's the case with other products. What about backporting the i18n fix to Zope 2.6.2 ? Using CMF / Plone with i18n support requires Zope 2.6.0 anyway. Maybe we could force people updating CMF / Plone also to update Zope to 2.6.2. This way CMF / Plone could switch to the new spec. I don't like breaking b/w compatibility this way, but honestly I don't really understand the issue about why this change was made in the first place, so perhaps I should go read up on that. - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Restart button and Products dir in Zope 2.7 beta 1
Hi, I tested todays Zope CVS checkout on Python 2.2.3 on FreeBSD 5.0. I noticed the following issues: (1) I noticed that the restart button is missing on the Control Panel. Is this intended behaviour for Zope 2.7? Or did I encounter a bug? There is still a Shutdown button, BTW. (2) I also tried to install some products in the INSTANCE_HOME/Products directory. There was a README.txt there telling: Additional products for your Zope instance should be installed in this directory. A freshly created instance should only contain this README.txt file in this directory. I tried adding a product to this directory (Formulator from CVS), but it didn't loaded when I restarted the Zope instance (from commandline because of (1)). It loads fine if I move it to SOFTWARE_HOME/Products. Can anybody comment on these issues? Should I create bugreports in the collector? PieterB -- http://zwiki.org/PieterB ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Restart button and Products dir in Zope 2.7 beta 1
On Sat, 2003-07-26 at 19:22, PieterB wrote: Hi, I tested todays Zope CVS checkout on Python 2.2.3 on FreeBSD 5.0. I noticed the following issues: (1) I noticed that the restart button is missing on the Control Panel. Is this intended behaviour for Zope 2.7? Or did I encounter a bug? There is still a Shutdown button, BTW. You must start zope under the control of the zopectl script to be able to restart it from the control panel. This is part of the zdaemon refactoring that was done by Guido. (2) I also tried to install some products in the INSTANCE_HOME/Products directory. There was a README.txt there telling: Additional products for your Zope instance should be installed in this directory. A freshly created instance should only contain this README.txt file in this directory. I tried adding a product to this directory (Formulator from CVS), but it didn't loaded when I restarted the Zope instance (from commandline because of (1)). It loads fine if I move it to SOFTWARE_HOME/Products. That's odd. I could swear I tested this. Please add this line to your config file: products $INSTANCE/Products It should start to work then... - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )