http://permalink.gmane.org/gmane.comp.web.zope.plone.remember hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/913 <pre>Hi, I have just released membrane 2.1.4, with a fix by Craig Haynal: False user property values were being converted to empty strings which would cause the property sheet to treat them as strings and make it impossible to set these properties back to True. Thanks Craig! </pre> Maurits van Rees 2012-04-13T11:34:47 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/912 <pre>Hooray! Thanks much, Maurits, for seeing this through! Ken On Fri, Apr 6, 2012 at 11:00 AM, Maurits van Rees &lt; m.van.rees-1kr/fGE7kR33Vop2t1AMdg&lt; at &gt;public.gmane.org&gt; wrote: -- Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2012/04/1333727988182 To unsubscribe send an email with subject "unsubscribe" to remember-81qHHgoATdGNjXQcXLqYpFN6ohzGQtmt&lt; at &gt;public.gmane.org Please contact remember-manager-81qHHgoATdGNjXQcXLqYpGD2FQJk+8+b&lt; at &gt;public.gmane.org for questions. </pre> Ken Manheimer 2012-04-06T15:59:30 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/911 <pre>Hi folks, Products.remember is on github now: https://github.com/collective/Products.remember Thanks to Rok Garbas for solving a permission problem! </pre> Maurits van Rees 2012-04-06T15:00:06 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/910 <pre>Hi, Marits. Sorry I've been unresponsive about this - my available time is very low at the moment. The repository migration I did was actually based on something Alex Clark was doing - he was migrating some other repositories, and offered help to others who were doing the same thing. Therefore, I'm not entirely sure what the process was - I added myself to the permissions.cfg in the collective.github.com &lt;https://github.com/collective/collective.github.com&gt; github repository, he processed that and enabled an "Import from subversion" link, on the Products.remember github repository that I created, which I used. I gather that wasn't the right thing - perhaps a generic github script? - and I should have instead used the https://github.com/plone/svn-migrate script. It sounds like, in order to use svn-migrate, you needed to be added to the [repo:Products.remember] collective team, but it looks like you're now included. Ken On Mon, Apr 2, 2012 at 11:58 AM, Maurits van Rees &lt; m.van.rees-1kr/fGE7kR33Vop2t1AMdg&lt; at &gt;p</pre> Ken Manheimer 2012-04-02T16:47:11 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/909 <pre>Op 22-03-12 12:31, Maurits van Rees schreef: As far as I saw, no actions had been taken on the github repo (no issues filed, no new commits, no pull requests), so today I indeed removed https://github.com/collective/Products.remember. It got recreated again by the automatic scripts that read permission.cfg as indicated in http://collective.github.com. But I have no admin access anymore. I am asking Rok Garbas for help. For a bit more detail see https://github.com/collective/collective.github.com/pull/229 Ken and Ross, you are in the same github team: https://github.com/organizations/collective/teams/138790 Do you somehow still have admin access? Meanwhile, https://github.com/mauritsvanrees/Products.remember has the same repo, in case anyone is desperately in need of that. If anyone gets admin access, a pull from this repo (with all branches and tags) should work fine too. I will likely delete my own repo after a while once everything is fine. Hang in there! :-) </pre> Maurits van Rees 2012-04-02T15:58:36 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/908 <pre>Hi, Op 8 feb 2012, om 21:29 heeft ken manheimer het volgende geschreven: Which link is that? I think the link you see on a fresh repository is a link that has no chance of working for any collective project. Maybe I am just repeating rumours, but that link will need to read in the full Plone svn collective and will quit after an hour, which is not enough. Or did I miss something? But you did import trunk, so something at least worked. :-) https://github.com/plone/svn-migrate advocates to clone this svn-migrate project, run its buildout, sync the collective repository (which may take a few days this first time) and write a config file with instructions on which directories to take from svn to create the new project. I finally took a look at this, using svn-migrate. I have created a repository in my own github account, which has all the tags and branches: https://github.com/mauritsvanrees/Products.remember I guess the best thing would now be to remove the collective/Products.remember repository, create</pre> Maurits van Rees 2012-03-22T11:31:09 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/907 <pre> Thanks! Will have to try it on my scratch repo. Before doing the migration I corresponded with Alex Clark, and got instructions from him and from the collective.github.com main page to use the link on the new repository to do the migration. I assume it uses the collective's svn-migrate, and I haven't determined what it does underneath, but figure it was the right thing to do. However, when I visit the new git repo's web view and follow the branches link&lt;https://github.com/collective/Products.remember/branches&gt;, it reports that there are no unmerged branches. Similarly, the Tags link reports zero tags. ? Ken -- Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2012/02/1328733006264 To unsubscribe send an email with subject "unsubscribe" to remember-81qHHgoATdGNjXQcXLqYpFN6ohzGQtmt&lt; at &gt;public.gmane.org Please contact remember-manager-81qHHgoATdGNjXQcXLqYpGD2FQJk+8+b&lt; at &gt;public.gmane.org for questions. </pre> ken manheimer 2012-02-08T20:29:49 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/906 <pre> git is stupid that way: you have to push tags separately. Use this: git push --tags svn2git does that automatically. Please don't use another tool to do a svn-&gt;git conversions (in particular do not rely on git svn). Wichert. </pre> Wichert Akkerman 2012-02-08T07:04:19 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/905 <pre> :-) I actually did the migration last friday, Feb 3 - should have posted a followup here: - https://github.com/collective/Products.remember - I renamed the svn trunk directory: .../trunk-MOVED-TO-GITHUB-COLLECTIVE/&lt;https://svn.plone.org/svn/collective/Products.remember/trunk-MOVED-TO-GITHUB-COLLECTIVE/&gt; - and left some notes directing to the git repo: - README.github&lt;https://svn.plone.org/svn/collective/Products.remember/trunk-MOVED-TO-GITHUB-COLLECTIVE/README.github&gt; in the trunk directory, and - a note at the top of the README.txt&lt;https://svn.plone.org/svn/collective/Products.remember/trunk-MOVED-TO-GITHUB-COLLECTIVE/README.txt&gt;in the same directory I have a few questions for those with git savvy out there, due to my own, limited git familiarity: - How would you tag the new repository with 1.9b2? I'm able to tag a local clone, but that apparently doesn't incur changes that can be pushed back to the origin. - Does anyone know if there is an easy way to creat</pre> ken manheimer 2012-02-07T22:32:40 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/904 <pre>go go go! -- ~Spanky On Feb 4, 2012, at 6:17 AM, Maurits van Rees wrote: -- Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2012/02/1328636471547 To unsubscribe send an email with subject "unsubscribe" to remember&lt; at &gt;lists.coactivate.org. Please contact remember-manager-81qHHgoATdGNjXQcXLqYpGD2FQJk+8+b&lt; at &gt;public.gmane.org for questions. </pre> Tom Kapanka 2012-02-07T17:41:06 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/903 <pre>Op 02-02-12 00:30, ken manheimer schreef: +1 </pre> Maurits van Rees 2012-02-04T14:17:17 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/902 <pre>Hey, all. There's an increasing trend to migrate Plone products from the Plone subversion repository to GitHub, which will only be accelerated by the recent shutdown of the plone.org SVN browser service. I would like to make the Products.remember migration happen, soon, and have scoped it out so it should be easy to do. I believe the result of the migration would be that the trunk in the plone.org svn repo would be replaced by a note, indicating the new location on GitHub, so ongoing development and new releases would be done via GitHub. The current branches and tags would still be accessible in the svn repo, however, so production checkouts wouldn't break. See the http://collective.github.com web page for info about the Plone collective on GitHub. (From the bit I've done with GitHub, it seems to be an outstanding source code management platform, with a somewhat more elaborate but substantially improved workflow compared to the svn service.) Any objections to the migration? I need to do the migration</pre> ken manheimer 2012-02-01T23:30:13 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/901 <pre>Op 25-11-11 11:39, Бессарабова Ирина schreef: Hi, I had another look. Indeed: the core Plone 4 migration apparently wants to make sure that portal_memberdata is available as a tool and that it is the standard MemberDataTool from PlonePAS. In Products.remember we want it to be our own tool. What Plone does also means most properties of portal_memberdata are removed. It probably works fine for a normal website, but not with membrane and remember installed. A second problem is that Products.membrane has some upgrade steps that replace the SearchableText index of the membrane_tool catalog with a better one. The way in which this is done, means that the new SearchableText index is filled but the other indexes are empty. I have fixed both problems with some upgrade steps in new releases: Products.membrane 2.1.2: - Fixed problem that occurs after upgrading the SearchableText index of the membrane_tool, which happens after upgrading to membrane 2.0 or to Plone 4: the membrane</pre> Maurits van Rees 2011-12-16T22:17:19 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/900 <pre>Hi Mauritz, On 8 December 2011 01:41, Maurits van Rees &lt;m.van.rees-1kr/fGE7kR33Vop2t1AMdg&lt; at &gt;public.gmane.org&gt;wrote: Does the product end up in the products in the root Zope Control Panel or Yes product is in zope products and it's profile appears in portal_setup. There are no warnngs or errors front or back when viewing qi. Regarding the "install method", I checked the following files: __init__.py doesn't reference remember at all, config.py uses ADD_MEMBER_PERMISSION and setuphandlers.py uses getAdderUtility. I not sure what where else to look. Thanks, that pulls in membrane 2.1.1. -- Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2011/12/1323331798277 To unsubscribe send an email with subject "unsubscribe" to remember-81qHHgoATdGNjXQcXLqYpFN6ohzGQtmt&lt; at &gt;public.gmane.org Please contact remember-manager-81qHHgoATdGNjXQcXLqYpGD2FQJk+8+b&lt; at &gt;public.gmane.org for questions. </pre> Mike Metcalfe 2011-12-08T08:09:55 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/899 <pre>Op 07-12-11 12:31, Mike Metcalfe schreef: That is two times the same number. That is certainly possible, but I guess for Products.membrane you mean 1.1b5? Well, the exact number is not too relevant in that case actually as long as it is 1.1bX: just switch to 1.1 for both products then. Hm, kinda hard to say without having the code of that client's product. Perhaps the install method of this client product is expecting things in Products.remember or membrane that have been changed? Are you getting an error or warning in the logs (or on the foreground) when you look at the portal_quickinstaller? Does the product end up in the products in the root Zope Control Panel or does it vanish (or show an error) there as well? I think that combination should work, but maybe I got myself confused. Checking now... Ah, you are correct, Products.remember 1.2 and Products.membrane 1.1 definitely do not match. Sorry about that. For clarity I have just released Products.remember 1.2.1 that has an offic</pre> Maurits van Rees 2011-12-07T23:41:55 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/898 <pre>I have a Plone 3.3.5 site in production that has remember and membrane pegged at versions 1.1b3 and 1.1b3 respectively. When I peg them at 1.2 and 2.1.1, the client's product that uses remember no longer appears in portal_quickinstaller (if I switch back and rebuild, it reappears). I also tried remember 1.2 with membrane 1.1 but on starting zope, p.remember/content/member.py fails to import Products.membrane.at on line 36. (which isn't in membrane 1.1) On 2 December 2011 16:00, Maurits van Rees &lt;m.van.rees-1kr/fGE7kR33Vop2t1AMdg&lt; at &gt;public.gmane.org&gt;wrote: </pre> Mike Metcalfe 2011-12-07T11:31:38 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/897 <pre>On Fri, Dec 2, 2011 at 10:33 AM, Maurits van Rees &lt; m.van.rees-1kr/fGE7kR33Vop2t1AMdg&lt; at &gt;public.gmane.org&gt; wrote: Fantastic - thanks for looking out for Products.remember. Ok. Ok - I won't worry that I was missing something obvious. Similar for http://plone.org/products/remember/releases/1.9b1: I have just Good - sounds like the whole release situation is a bit tidier, now. Thanks again! PloneSoftwareCenter is still too much geared towards the old manual way of Truly. (I tried to see whether jarn.mkrelease would make things easier, but could find no more instructions for it than I could for plone.org product releases, in general.) Ken -- Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2011/12/1323014531182 To unsubscribe send an email with subject "unsubscribe" to remember&lt; at &gt;lists.coactivate.org. Please contact remember-manager-81qHHgoATdGNjXQcXLqYpGD2FQJk+8+b&lt; at &gt;public.gmane.org for questions. </pre> ken manheimer 2011-12-04T16:01:51 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/896 <pre>Op 02-12-11 16:19, ken manheimer schreef: I've seen it. I have now made the releases on plone.org as well. Sharing tab is fine. When I want to give colleagues access, I usually check all the boxes there. No idea, I've seen this on other products as well. I don't have access to the error log so I don't know what is wrong or if we could fix it ourselves. I think that is the box that tries to display some experimental releases actually; usually that means it show a beta from five years ago... Similar for http://plone.org/products/remember/releases/1.9b1: I have just now hidden that release as it ended up in the releases list above the final 1.9. After that I immediately got an error viewing that 1.9b1 page and I don't know what it is. For 1.9b2 I have retracted the release and now marked it as beta. PloneSoftwareCenter is still too much geared towards the old manual way of doing releases instead of the new automated PyPI-like way and it is showing. It needs more love. :-) Thanks, </pre> Maurits van Rees 2011-12-02T15:33:24 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/895 <pre>Thanks to Richard and Maurits for taking care of this issue! Clayton </pre> Clayton Parker 2011-12-02T14:17:58 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/894 <pre>Hi list, In the wake of the security release of Products.membrane from yesterday I fixed a similar problem in Products.remember, also indicated by Richard Mitchell, thanks. The security problem is this: anonymous users could get the password hash of a remember member. It is not an immediate problem, but it sure makes it easier to crack passwords. I have made three releases with this fix on PyPI, 1.1, 1.2, 1.9, all listed here: http://pypi.python.org/pypi/Products.remember 1.1 is the old 1.1b3 release from 2009 with the security fix added. Use this when you were using that release and do not want a big upgrade. Compatible with Plone 3.x and Products.membrane 1.1. Definitely NOT with Plone 4 or Products.membrane 2.x. 1.2 has more changes; see the changelog. It has the changes that were done on trunk before Ken started doing bigger changes leading to the 1.9 series. Compatible with Plone 3 and Products.membrane 1.1 or 2.x (2.1.1 recommended). Might work on Plone 4 but the automated tests </pre> Maurits van Rees 2011-12-02T14:00:16 http://permalink.gmane.org/gmane.comp.web.zope.plone.remember/893 <pre>Op 02-12-11 02:22, ken manheimer schreef: One of *those* days eh? No problem, those things happen. I see that Ross Patterson has meanwhile granted me rights on PyPI, thanks. Rights on plone.org would still be good to have, but those are less urgent. PyPI releases have been made: 1.1, 1.2, 1.9. I will make a separate mail for that announcement. Thanks, </pre> Maurits van Rees 2011-12-02T12:24:11 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.remember