Gitter is no longer the official chat used by Plone. Please see the official Plone support channels at https://plone.org/support. • forum: https://community.plone.org • Discord (chat, voice, video, sprints): https://discord.com/invite/zFY3EBbjaj • conference videos and slides: https://ploneconf.org • How to contribute: https://plone.org/get-started • Latest releases: https://plone.org/download • Intro to Plone: https://plone.com • Plone news and events: https://plone.org
@MrTango I just installed mosaic 2.2.1 on top on plone 5.1 using the actual coredev buildout with the following local.cfg:
[https://webchat.freenode.net (hariom), irc.freenode.net] Hi, I'm setting up Plone in production mode. Need your advice, is it good to install it as non-root user? I've installed required dependent libraries already.
We never install Plone as root. Of course you should use a non-root user.
[https://webchat.freenode.net (hariom), irc.freenode.net]@syncbot it seems like my internet connection is not stable today. Earlier I sent the following message:
[https://webchat.freenode.net (hariom), irc.freenode.net] Is UnifiedInstaller option good in that case (non-root) as it creates a plone user and then drops down to that before running buildout
[https://webchat.freenode.net (hariom), irc.freenode.net] or is it better to create an unprevillaged plone user and then su to that and run ./install.sh script?
Ramiro Batista da Luz
@petschki I did this: A checkout on the 1.x branch creating a working in progress branch. Did some translations, then did a pull request against 1.x
@MrTango did a review, merged and created the 1.5.1 release.
My suspicion is that the release was created based on the master branch.
Because the branch 1.x doesn't have the piece of code that is raising the exception.
Ramiro Batista da Luz
My mistake, it hve.
@ramiroluz well ... all good. the compare url is the same ... and the release was made from 1.x branch as you see in the commits https://github.com/collective/Products.windowZ/commits/1.x ... I think (reading your traceback again) the problem is the missing plone.api dependency which is not a part of core in 4.3 ... this has to be placed in WindowZ/setup.py