http://blog.gmane.org/gmane.comp.web.zope.plone.versioning hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.web.zope.plone.versioning/792 <pre>I filed the following bug at plone.org: Previous revision of versioned File shows wrong values of the last revision https://dev.plone.org/plone/ticket/11998 Any insights about that? ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 </pre> Marcio Mazza 2011-07-10T14:44:40 http://comments.gmane.org/gmane.comp.web.zope.plone.versioning/791 <pre>Hello, is this list still active? Looking at the archives, I have the impression that perhaps discussion is taking place some place else. Nevertheless: I have a site running under Plone4 with some custom content types. The content types are built with the appropriate paster templates, the fields use annotation storage. When I enable versioning (in the control panel for my types), everything *seems* to work (links and views are all in place), however, nothing is being versioned, and the diff tool tells me there is no difference between versions. I'm wondering if I forgot something obvious. Sadly, not only my custom fields are not being versioned, but also the inherited fields like title and description. It works however for standard types (on the same site). What other information do you need to perhaps help? I already began spreading print statements around in the code to see where the information gets lost, so I'm not afraid of working that out. TIA, best regards, Christoph -----------------------</pre> Christoph Pingel 2011-07-01T08:23:42 http://comments.gmane.org/gmane.comp.web.zope.plone.versioning/790 <pre>Hello everybody, this is my first message to the list, and is because i need to implement some new functionality and i thought about CMFEditions to do it. To simplify the story, i have 2 CT's: CT "A" is a folderish for CT "B" (which is not a folderish) they both have files and i'm using fss to manage that. now, what i need to do is to have a new CT, "C" that will have reference to one or more "A" objects. Now, when that happens, i need all of "A" objects referenced to not be able to be changed, so that's when CMFEditions come in. (actually they can be, like an errata, but that's another scope) What i came up with is that the reference from "C" is actually a reference to an exact version of "A" so no matter if that object is modified, i always access the version i wanted. I managed to make "A" and "B" versionable, and works fine with fss, but i'm not being able to integrate the "A" version with the "B" objects inside. What i would need is that when i have, say, version 1 of "A" i also have the "B"</pre> Franco Pellegrini 2009-08-11T19:51:13 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.versioning