Re: Setting up multi-language navigation panels in Plone?

LinguaPlone is the solution for this, yes.

On Thu, 24 Jan 2008 09:01:25 -0800, Ingimundur Stefánsson  
<ingimundurs@...> wrote:

> Dear all.
> I would like to modify a current Plone site so that navigation panels  
> are in
> the language chosen through the flags on the site, four languages in  
> total.
> Unfortunately I do not now the plone version of the site, and am unable  
> to
> check for version, simply do not understand the directions for this. The
> site was constructed last year so that might suggest more recent  
> versions.
> Source code does not reveal this.
> Can anyone suggest how multi-language navigation panels are most easily
> achived?
> I find little answers in archives but LinguaPlone has been suggested.
> All help appreciated.
> Regards
> Ingimundur
>

--

-- 
Alexander Limi · http://limi.net

collective.captcha in comment form

I'm relativly new to Plone and I'm using Plone 3.0.5 for my personal website.
I want to allow anonymous comments but I read in the forums that spam-bots
are also spaming in Plone-sites. So I had the idea to use captcha in the
comment-form and installed collective.captcha. But now I don't understand
how to implement it in the form. What do I have to do? I read the included
text-files but like I said I don't understand what they want me to do and
add the example code. Isn't there somewhere a step-by-step howto? Thank's
for every help.
--

-- 
View this message in context: http://www.nabble.com/collective.captcha-in-comment-form-tp15242218s15482p15242218.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

Installing Python modules with Unified Installer: Deb. Etch

Am trying to get ldap authentication (after installing using the Universal
Installer on Debian Etch)
Am at the point of installing ldap module into python under /opt
Have tried instructions here: 

http://plone.org/documentation/faq/how-do-i-install-python-modules-to-the-unified-installer/

(thanks) but install falls over.
I am guessing that the problem is in the setup.cfg file with these two
lines:

library_dirs = /usr/local/openldap-2.3/lib
include_dirs = /usr/local/openldap-2.3/include /usr/include/sasl

as I am guessing they should point to directories under
/opt/Plone-3.0.4/Python-2.4.4 somewhere.

As I am a complete newbie a fuller description:
download python-ldap-2.3.1.tar.gz to /root
untar package: tar -zxvf *.tar.gz
cd python-ldap-2.3.1
$ export PATH=/opt/Plone-3.0.4/Python-2.4.4/bin:$PATH 
python setup.py install
falls over here

any help appreciated

James L.
--

-- 

CacheFu problems

I had a bunch of problems moving my 2.5.5 instance to 3.0.5 with CacheFu, and
I thought I'd fought through most of them.  I reported a possible
"AttributeError: portal_type" bug [1], and now I've got another problem: I
can't access the Cache Configuration Tool or any of its tabs without Plone
throwing an error, such as "Module Products.CacheSetup.content.cache_tool,
line 168, in getActivePolicyVocabulary" [2].

In addition, attempts to uninstall CacheFu (hoping for an uninstall and a
clean re-install) result in an error:

Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module <string>, line 4, in _facade
  Module AccessControl.requestmethod, line 64, in _curried
  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 600, in
uninstallProducts
  Module Products.CMFQuickInstallerTool.InstalledProduct, line 272, in
uninstall
  Module Products.ExternalMethod.ExternalMethod, line 231, in __call__
   - __traceback_info__: ((<PloneSite at /racf>,), {'reinstall': False},
(False,))
  Module
/var/plone/zeocluster/client1/Products/CacheSetup/Extensions/Install.py,
line 75, in uninstall
  Module <string>, line 4, in _facade
  Module AccessControl.requestmethod, line 64, in _curried
  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 600, in

plonegetpaid installation

I tried to install plonegetpaid 0.3 tarball to plone 3.0.4.
The product shows up in portal_quickinstaller. But I clicked on install
button. It never installed. I restart Zope. the portal_quickinstaller showed
an error.
Does anyone else have the problem?
--

-- 
View this message in context: http://www.nabble.com/plonegetpaid-installation-tp15272131s15482p15272131.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.

Re: CacheFu problems

On Feb 4, 2008, at 8:01 AM, deesto wrote:

> I had a bunch of problems moving my 2.5.5 instance to 3.0.5 with  
> CacheFu, and
> I thought I'd fought through most of them.  I reported a possible
> "AttributeError: portal_type" bug [1], and now I've got another  
> problem: I
> can't access the Cache Configuration Tool or any of its tabs without  
> Plone
> throwing an error, such as "Module  
> Products.CacheSetup.content.cache_tool,
> line 168, in getActivePolicyVocabulary" [2].
>
> In addition, attempts to uninstall CacheFu (hoping for an uninstall  
> and a
> clean re-install) result in an error:

   [snip]

> Please help me to get past these errors and get CacheFu working again?
>
> Thanks,
> ~John
>
> [1] http://plone.org/products/cachefu/issues/119
> [2] http://paste.plone.org/19336

Is this the same instance where all this crazy stuff happened...
http://www.nabble.com/problem-upgrading-CacheFu-td14672299s15482.html#a14672299

buildout error - need help

Greetings,

I'm trying to setup a Plone buildout for a non-root user "plone".

So far my environment is:

- fresh install of CentOS 4.6 brought up2date

- as root user, ran a modified version of the Plone 3.0.5 Unified Installler
to setup Python 2.4.4 and other required stuff (commented out install of
zope/plone). This installed python in /opt/plone/Python-2.4.4

- as root user, ran "easy_install ZopeSkel" which setup "Best match:
ZopeSkel 1.5.1"

- modified plone user's profile to pickup new version of python

- as plone user, created project buildout with "paster create -t
plone3_buildout centenary"

- as plone user, bootstrap the buildout with "python bootstrap.py"

- as plone user, build the system with "bin/buildout"
this produced the following output and error:
=====================================
Getting distribution for 'plone.recipe.plone'.
Got plone.recipe.plone 3.0.5.
Getting distribution for 'plone.recipe.distros'.
Got plone.recipe.distros 1.3.

Re: plonegetpaid installation

Katt, on 2008-02-04:
>
> I tried to install plonegetpaid 0.3 tarball to plone 3.0.4.
> The product shows up in portal_quickinstaller. But I clicked on install
> button. It never installed. I restart Zope. the portal_quickinstaller showed
> an error.

It always helps to paste the actual error here.  Especially, look in
your event.log file on the file system or in the error_log within your
Plone Site to see if there is a meaningful traceback there.  Or even
if you think the tracebak is not meaningful, paste it here anyway. :)

> Does anyone else have the problem?

No.

I do not know if a lot of the getpaid developers read this list.  You
may want to try the getpaid developers list (it's okay also if you are
not a developer):

http://groups.google.com/group/getpaid-dev

--

-- 
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]

Re: CacheFu problems

Hi Ric,

On Feb 4, 2008 4:28 PM, Ricardo Newbery <ric@...> wrote:
>
> On Feb 4, 2008, at 8:01 AM, deesto wrote:
>    [snip]
>
> > Please help me to get past these errors and get CacheFu working again?
> >
> > Thanks,
> > ~John
> >
> > [1] http://plone.org/products/cachefu/issues/119
> > [2] http://paste.plone.org/19336
>
>
> Is this the same instance where all this crazy stuff happened...
> http://www.nabble.com/problem-upgrading-CacheFu-td14672299s15482.html#a14672299

Yes, indeed: it is the same one.

> It looks like your CacheFu installation is all messed up.
>
> I believe you've already fixed issue [1] ...  but not before
> incorrectly deleting a bunch of stuff manually...

Unfortunately, [1] wasn't fixed at the time of my original writing.
It's fixed now, though, thanks to the highly-combustible instructions
in your response. ;)

Indytube