We've been working on improving the Cyn.in buildout for developers (these changes are in SVN trunk right now). One of the coolest little products that we've found and included in the cynindevelop.cfg file is this one called rbco.wfdocumentator - it provides a nice display of the transition graph of the various states of a workflow. More importantly perhaps, it provides a tabular summary of all the states and permissions granted to various roles in each of the states. Permissions required to flow an object through a particular transition are also listed at the bottom.
Much easier than wading through the workflow.xml and rolemap.xml files to understand what's going on, I assure you. :)
Here's what the output for the Space Content workflow looks like:
Instructions on what else is new with the cynindevelop.cfg based buildout and how to use it are coming soon.
We are engaging another cyn.in space at the academy of fine arts in Vienna. We are using the downloaded version 3.1.1. Now when we set an internal link to an item that is only project-visible we encountered an "Insufficient Privileges" Error. I looked into the error logs and found the reason: "Unauthorized: You are not allowed to access 'title' in this contex". I looked into the code and found that in the template "links_macro.pt" the property "item/title" is being used. I was able to fix the error by using the property "item/Title" - which is accessible on a catalog object. Here's the patch, i hope you can apply it for future versions!
Index: src/ubify.cyninv2theme/ubify/cyninv2theme/skins/ubify_cyninv2theme_custom_templates/links_macro.pt =================================================================== --- src/ubify.cyninv2theme/ubify/cyninv2theme/skins/ubify_cyninv2theme_custom_templates/links_macro.pt +++ src/ubify.cyninv2theme/ubify/cyninv2theme/skins/ubify_cyninv2theme_custom_templates/links_macro.pt @@ -101,7 +101,7 @@ tal:attributes="href item_url;class string:relateditemlink" > <img tal:attributes="src item/icon" border="0"/> - <span tal:content="item/title" /> + <span tal:content="item/Title" /> </a></li> </ul> </div>
Now the "Linked Content" displays right and the security issue is solved. We are very happy with cyn.in here and once more want to express our kind regards to the cynapse team!
Georg Gogo. BERNHARD
Settings are done into ZMI, so first of all :
- Go to http://your.cynin.site/root/manage/
- Then go into acl_users/your_ldap/, then in the Cache tab
- Set "Cache this object using:" to "RAMCache" and save changes.
I'm not sure, but there may be some other places where caching is relevant, feel free to comment.
Novell has used various proprietary CMS solutions over time, including TeamSite and Vignette. None of these solutions met all of their needs, nor were they easy to modify. Novell began looking at different Open Source CMS options, and decided on Plone. This presentation will briefly discuss Novell's proprietary CMS history, why they chose Plone, what Novell are currently using and developing, and their plans for the future. It will also discuss Novell's architecture for making Plone successful for enterprise websites.
Hello, every 01!
I am Georg Gogo. BERNHARD. I've been playing with plone since i saw it being presentet 2002 at the EuroPython in Charleroi, Belgium. Now I am working at the ]a[ academy of fine arts vienna. I tweeted about our recent ambitions to test cyn.in and @viraf asked me to share our experiences at the #cynapse community pages.
First I thought that there would be a lot to say about which problems we had and how we solved them, but it fact the whole procedure was pretty easy. We already have a ZEO-Cluster setup for the homepage (http://www.akbild.ac.at) and we re-used the infrastructure for cyn.in.
web01 proxy01 lvs01 webXX zeo01 | .... | +------+ +--------+ +-------+ +------+ > zope < +-----+ | | | | | | / |------| \ | | <---> apache <---> squid <---> ipvs <---> zope <---> zeo | | | | | | | \ |------| / | | +--------+ +-------+ +------+ > zope < +-----+ +------+ | .... | Virtualhost Cache Balancer Servers Storage
Our Team tested the cyn.in Desktop and WebDAV, everything works pretty well. On Apple Computers we have to use Cyberduck for WebDAV, though; the Operating Systems implementation (Finder) does not work well. We also decided not to "roll out" the Desktop and WebDAV now, because we think it is too complicated for people to actually use it since they "see too many things" in their respective clients - it might be confusing for regular users. In our opinion downstripping is still key.
Language integration for German is not finished and we don't have the resources to complete it ourselves.
When we finally presented cyn.in as a solution for collaboration we had excellent responses. People found it confusing at first sight [sic!] but then realized that it is easy to use since you'd only use some of its functions. We will definitively use it for two pilot projects now, one is a construction project for one of our buildings, the other project is internal communication in a department.
To sum things up: cyn.in seems to be the solution we were looking for.