From dirk at haun-online.de Wed Dec 2 07:25:10 2009 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 02 Dec 2009 13:25:10 +0100 Subject: [geeklog-devel] That "social" thing Message-ID: <20091202132510.19754feju87r7hq8@webmail.df.eu> So we have this vague idea for a GSoC project: "Add Social Networking Features"[1]. And because it is so vague, we didn't get any good student applications for it. After all, if we don't know what it should do, how are students supposed to come up with a decent application for it? I was thinking that maybe before adding friends and stuff, we should be starting with something more basic (and useful). Like giving users more control over their profile page. Here are some ideas: Some services (e.g. mixxt, SlideShare) have a feature called a "wall" where users can leave messages on other user's profile pages. Instead of reinventing the wheel, how about allowing comments on a user's profile? Badges. Many services are offering badges that you can embed into your homepage. I'd like to have a Dopplr badge on my profile, for example. Others may prefer a Flickr badge to show off their latest photos, and so on. In a similar vein: RSS feeds. Why not allow embedding your favorite RSS feed on your profile? Overall, we should give users more control over what is displayed on their profile page. Let them hide the PGP key and the latest stories but let them allow comments on profiles, etc. Once the profile feels more like a user's "home page", we can think about adding friends and such. There are probably other things we can come up with. Is anybody interested to take on coordinating such an effort? There seems to be some interest in these sort of things. Also, at least some of these features are probably better implemented as plugins, which may require new / updated / fixed plugin API functions (there was a related forum discussion recently). bye, Dirk [1] http://wiki.geeklog.net/index.php/SoC_socialnetworking -- http://www.flickr.com/photos/dhaun/ From websitemaster at cogeco.net Sat Dec 5 14:03:31 2009 From: websitemaster at cogeco.net (Tom) Date: Sat, 5 Dec 2009 14:03:31 -0500 Subject: [geeklog-devel] Geeklog 1.6.2 In-Reply-To: <20091202132510.19754feju87r7hq8@webmail.df.eu> References: <20091202132510.19754feju87r7hq8@webmail.df.eu> Message-ID: <008301ca75dd$a3097a50$e91c6ef0$@net> What is the proposed timeline for releasing Geeklog 1.6.2? I want to make sure I give myself enough time to contribute a few features. Tom From dirk at haun-online.de Sat Dec 5 16:59:48 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 5 Dec 2009 22:59:48 +0100 Subject: [geeklog-devel] Geeklog 1.6.2 In-Reply-To: <008301ca75dd$a3097a50$e91c6ef0$@net> References: <20091202132510.19754feju87r7hq8@webmail.df.eu> <008301ca75dd$a3097a50$e91c6ef0$@net> Message-ID: <20091205215948.1895444830@smtp.haun-online.de> Tom wrote: >What is the proposed timeline for releasing Geeklog 1.6.2? I haven't given it too much thought yet, actually. Certainly not before February, I'd say. Maybe this would be a good opportunity to talk about a fixed release schedule again? While I'm with Dries[1] on detailed roadmaps, a fixed released schedule does have its advantages: It would make it clear until when a feature has to be completed to make it into the next release and would avoid discussions about squeezing in things at the last minute. What would be a good schedule? A release every 6 months, maybe? 3 months is probably too short. Mercurial chose a 4-month cycle[2], for example. Assuming a 6-month cycle and taking GSoC into account (insert standard disclaimers about acceptance here), this could be April and October. Do we want to pin it down further (like April 1st or "first weekend in April")? A feature freeze would happen, say, 4 weeks before the scheduled release date and would be followed by a beta and release candidates. After a release, we could allow for a short window (4-6 weeks or so) for a bugfix release, if necessary. After that, any further fixes would have to wait for the next release. Security fixes would still be rolled out ASAP, as usual. Thoughts? bye, Dirk [1] "Screw Roadmaps" - Dries Buytaert [2] -- http://www.geeklog.net/ http://geeklog.info/ From websitemaster at cogeco.net Mon Dec 7 08:51:15 2009 From: websitemaster at cogeco.net (Tom) Date: Mon, 7 Dec 2009 08:51:15 -0500 Subject: [geeklog-devel] Geeklog 1.6.2 In-Reply-To: <20091205215948.1895444830@smtp.haun-online.de> References: <20091202132510.19754feju87r7hq8@webmail.df.eu> <008301ca75dd$a3097a50$e91c6ef0$@net> <20091205215948.1895444830@smtp.haun-online.de> Message-ID: <015f01ca7744$582d0f70$08872e50$@net> Probably a release every 6 months would be best, than at least the features that are done can get out the door sooner. We do need a roadmap for at least the major features proposed. http://wiki.geeklog.net/index.php/Proposed_Roadmap Then it can at least guide us in a general direction of what new features will be implemented and when, and possibly by who. For example, I know we talked about and decided to implement a JavaScript library and it looks like it may be jQuery?? Blaine - you mentioned you hacked the Geeklog core to implement some JavaScript libraries. Has this code been developed enough that it can be useful to us? Other items that need to be added to the Roadmap - Implementing the Plugin Repository - "Add Social Networking Features" - ??? Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: December-05-09 5:00 PM To: geeklog-devel Subject: Re: [geeklog-devel] Geeklog 1.6.2 Tom wrote: >What is the proposed timeline for releasing Geeklog 1.6.2? I haven't given it too much thought yet, actually. Certainly not before February, I'd say. Maybe this would be a good opportunity to talk about a fixed release schedule again? While I'm with Dries[1] on detailed roadmaps, a fixed released schedule does have its advantages: It would make it clear until when a feature has to be completed to make it into the next release and would avoid discussions about squeezing in things at the last minute. What would be a good schedule? A release every 6 months, maybe? 3 months is probably too short. Mercurial chose a 4-month cycle[2], for example. Assuming a 6-month cycle and taking GSoC into account (insert standard disclaimers about acceptance here), this could be April and October. Do we want to pin it down further (like April 1st or "first weekend in April")? A feature freeze would happen, say, 4 weeks before the scheduled release date and would be followed by a beta and release candidates. After a release, we could allow for a short window (4-6 weeks or so) for a bugfix release, if necessary. After that, any further fixes would have to wait for the next release. Security fixes would still be rolled out ASAP, as usual. Thoughts? bye, Dirk [1] "Screw Roadmaps" - Dries Buytaert [2] -- http://www.geeklog.net/ http://geeklog.info/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 4663 (20091205) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From dirk at haun-online.de Mon Dec 7 14:23:58 2009 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 7 Dec 2009 20:23:58 +0100 Subject: [geeklog-devel] Geeklog 1.6.2 In-Reply-To: <015f01ca7744$582d0f70$08872e50$@net> References: <20091202132510.19754feju87r7hq8@webmail.df.eu> <008301ca75dd$a3097a50$e91c6e f0$@net> <20091205215948.1895444830@smtp.haun-online.de> <015f01ca7744$582d0f70$08872e50$@net> Message-ID: <20091207192358.375852224@smtp.haun-online.de> Tom wrote: >Then it can at least guide us in a general direction of what new features >will be implemented and when, and possibly by who. Right. >Other items that need to be added to the Roadmap >- Implementing the Plugin Repository I do have the Geeklog side of things in a local Mercurial repository, all merged with the current development version (including SQL updates etc.). I haven't pushed it since I ran into a few issues with the actual Repository plugin. I've talked to Tim briefly to see if he would be available to either work on it or help us with it. The Plugin Repository is an important next step in our ongoing quest to make installation and upgrades easier, so it should definitively be on the list. >- "Add Social Networking Features" Well, there wasn't a lot of enthusiasm for my last post, to put it mildly. So unless that changes, all that "social" stuff is off the list. >For example, I know we talked about and decided to implement a JavaScript >library and it looks like it may be jQuery?? We do have 2 or 3 issues in our bugtracker that could be solved with a few lines of JavaScript. They wouldn't exactly require a JS library, though. But how about a search function for the Configuration? That would be an interesting project and a good test for a JS library. There's also an unresolved issue with numbered items, e.g. Miscellaneous > Miscellaneous > Notifications: When you have 2 or more entries and remove an entry other than the last, the remaining entries should be renumbered or any additional entry will now get a duplicate number. That's all JS code there. Other "big" items? OpenID 2.0 and Postgres support would come to mind, but I haven't heard anything from Choplair or Stan recently (hey guys). Other than those, I can't think of any right now, but there will no doubt be a gazillion smaller ones (not to mention the 150 open issues in the bugtracker). All of these possible roadmap items are looking for a volunteer / coordinator / champion (however you want to call it). bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Mon Dec 14 14:16:18 2009 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 14 Dec 2009 20:16:18 +0100 Subject: [geeklog-devel] Why the 403 code after spam detected? IIS7 doesn't like it In-Reply-To: <024701ca5731$4ca97b30$e5fc7190$@net> References: <955159C0-6143-4B90-B50C-63CC555CFE07@griffsweb.com> <01b001ca4f82$ca508da0$5ef1a8e0$@net> <024701ca5731$4ca97b30$e5fc7190$@net> Message-ID: <20091214191618.1915371006@smtp.haun-online.de> Tom wrote: >Is there any reason we should be generating this 403 error here? This >doesn't play nice with IIS7 which by default returns a custom summary error >page. Hmm, this sounds familiar: bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From websitemaster at cogeco.net Mon Dec 14 18:04:33 2009 From: websitemaster at cogeco.net (Tom) Date: Mon, 14 Dec 2009 18:04:33 -0500 Subject: [geeklog-devel] Why the 403 code after spam detected? IIS7 doesn't like it In-Reply-To: <20091214191618.1915371006@smtp.haun-online.de> References: <955159C0-6143-4B90-B50C-63CC555CFE07@griffsweb.com> <01b001ca4f82$ca508da0$5ef1a8e0$@net> <024701ca5731$4ca97b30$e5fc7190$@net> <20091214191618.1915371006@smtp.haun-online.de> Message-ID: <01a201ca7d11$cc8d9fb0$65a8df10$@net> Thanks, I don't think the author likes IIS 7 ;-) Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: December-14-09 2:16 PM To: geeklog-devel Subject: Re: [geeklog-devel] Why the 403 code after spam detected? IIS7 doesn't like it Tom wrote: >Is there any reason we should be generating this 403 error here? This >doesn't play nice with IIS7 which by default returns a custom summary error >page. Hmm, this sounds familiar: bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 4687 (20091214) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From dirk at haun-online.de Tue Dec 15 15:55:21 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 15 Dec 2009 21:55:21 +0100 Subject: [geeklog-devel] Meetups In-Reply-To: <20091110210325.920524853@smtp.haun-online.de> References: <20091110210325.920524853@smtp.haun-online.de> Message-ID: <20091215205521.635206086@smtp.haun-online.de> Is anyone considering going to FOSDEM (Brussels, Feb 6-7, 2010)? http://fosdem.org/2010/ I've never been there before but heard good things about it. Just need a good reason (like, someone else I know being there) ... bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From dirk at haun-online.de Sun Dec 20 14:16:39 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 20 Dec 2009 20:16:39 +0100 Subject: [geeklog-devel] Prototype fix for expiring security tokens (was: geeklog: Experimental: Give the user an idea how long they have ...) In-Reply-To: <20091030153855.753786748@smtp.haun-online.de> References: <20091029173541.1055943830@smtp.haun-online.de> <20091030153855.753786748@smtp.haun-online.de> Message-ID: <20091220191639.1127372422@smtp.haun-online.de> Dirk Haun wrote: >>and, if it expires, make them submit their password again. > >Yes, that's the best solution to the problem I've heard so far and >should be the final goal. But, as I said, this message is meant as an >intermediate step. Fixing the editors, including the password check, >etc. is a lot of (tedious) work and I don't see it happening anytime >soon. Well, I think I found a nice solution to the problem of expiring security tokens that doesn't require rewriting all the editors: Let SEC_checkToken() do all the work. Attached is a prototype implementation that contains 3 drop-in replacement files for Geeklog 1.6.1 (admin/configuration.php is only included since it didn't use SEC_checkToken() correctly). How does it work? When SEC_checkToken() finds that the token isn't valid, it displays a form asking the user to authenticate again. If that is successful, the original request is recreated and sent again with a new token. Known limitations: - prototype code includes hard-coded text strings - doesn't work with OpenID (but should work with other remote auth modules) - haven't tested with file uploads - probably loses them To test: Copy the 3 files over their 1.6.1 equivalents. Call up any editor (e.g. story editor), wait until token expires (or empty the gl_tokens table), try to save. Follow the instructions and rejoice :) Feedback welcome. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ -------------- next part -------------- A non-text attachment was scrubbed... Name: prototype.tar.gz Type: application/x-gzip Size: 25222 bytes Desc: not available URL: From joe at ThrowingDice.com Sun Dec 20 15:04:59 2009 From: joe at ThrowingDice.com (Joe Mucchiello) Date: Sun, 20 Dec 2009 15:04:59 -0500 Subject: [geeklog-devel] Prototype fix for expiring security tokens (was: geeklog: Experimental: Give the user an idea how long they have ...) In-Reply-To: <20091220191639.1127372422@smtp.haun-online.de> References: <20091029173541.1055943830@smtp.haun-online.de> <20091030153855.753786748@smtp.haun-online.de> <20091220191639.1127372422@smtp.haun-online.de> Message-ID: <0KUY0047JVP29790@mta3.srv.hcvlny.cv.net> At 02:16 PM 12/20/2009, you wrote: >Feedback welcome. The urlencode() of the post and get data should actually call htmlspecialchars(). There aren't being placed in a url. They are being placed in html. Personally, I base64 then so you know there are no special chars but that's just me. It would be nice if there were a parameter to SEC_checkToken which would bypass the builtin security check. A plugin author might have reason to disallow the relogin. (Why? Who knows? But it doesn't hurt to allow it.) function SEC_checkToken($handle_relogin = true) { global $LANG20; if (SECINT_checkToken()) { return true; } else if (!$handle_relogin) { return false; } ... If you saved the post/get data to the database you could support OpenID. But that code would probably be a bit convoluted. ---- Joe Mucchiello Throwing Dice Games http://www.throwingdice.com From dirk at haun-online.de Sun Dec 20 16:47:31 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 20 Dec 2009 22:47:31 +0100 Subject: [geeklog-devel] Prototype fix for expiring security tokens (was: geeklog: Experimental: Give the user an idea how long they have ...) In-Reply-To: <20091220191639.1127372422@smtp.haun-online.de> References: <20091029173541.1055943830@smtp.haun-online.de> <20091030153855.753786748@smtp.haun-online.de> <20091220191639.1127372422@smtp.haun-online.de> Message-ID: <20091220214731.1665907779@smtp.haun-online.de> Dirk Haun wrote: >Known limitations: Forgot to mention: Won't work as localhost on a Mac. The IP address in your session will be recorded as ::1 but the re-created request will come in with 127.0.0.1 for some reason. As a result, the session will not be recognized. bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From dirk at haun-online.de Wed Dec 30 05:05:26 2009 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 30 Dec 2009 11:05:26 +0100 Subject: [geeklog-devel] Prototype fix for expiring security tokens In-Reply-To: <20091220191639.1127372422@smtp.haun-online.de> References: <20091029173541.1055943830@smtp.haun-online.de> <20091030153855.753786748@smtp.haun-online.de> <20091220191639.1127372422@smtp.haun-online.de> Message-ID: <20091230100526.169642810@smtp.haun-online.de> >Feedback welcome. Anyone? The code is now in our Mercurial repository. I've managed to make things fully transparent, including file uploads. As an added bonus, using the browser's back button will now also work with forms that have an embedded token - you will simply be asked to authenticate when you go back and send the form again. Pretty much the only requirement is that you use SEC_checkToken() correctly, i.e. really only call it when you need to check for a token. See for more information. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From websitemaster at cogeco.net Wed Dec 30 09:14:04 2009 From: websitemaster at cogeco.net (Tom) Date: Wed, 30 Dec 2009 09:14:04 -0500 Subject: [geeklog-devel] Prototype fix for expiring security tokens In-Reply-To: <20091230100526.169642810@smtp.haun-online.de> References: <20091029173541.1055943830@smtp.haun-online.de> <20091030153855.753786748@smtp.haun-online.de> <20091220191639.1127372422@smtp.haun-online.de> <20091230100526.169642810@smtp.haun-online.de> Message-ID: <004001ca895a$578ed1c0$06ac7540$@net> This will be a welcome addition. I have lost more than a few stories by not realizing my token had expired. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: December-30-09 5:05 AM To: geeklog-devel Subject: Re: [geeklog-devel] Prototype fix for expiring security tokens >Feedback welcome. Anyone? The code is now in our Mercurial repository. I've managed to make things fully transparent, including file uploads. As an added bonus, using the browser's back button will now also work with forms that have an embedded token - you will simply be asked to authenticate when you go back and send the form again. Pretty much the only requirement is that you use SEC_checkToken() correctly, i.e. really only call it when you need to check for a token. See for more information. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 4729 (20091230) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From joe at ThrowingDice.com Wed Dec 30 20:32:55 2009 From: joe at ThrowingDice.com (Joe Mucchiello) Date: Wed, 30 Dec 2009 20:32:55 -0500 Subject: [geeklog-devel] Prototype fix for expiring security tokens In-Reply-To: <20091230100526.169642810@smtp.haun-online.de> References: <20091029173541.1055943830@smtp.haun-online.de> <20091030153855.753786748@smtp.haun-online.de> <20091220191639.1127372422@smtp.haun-online.de> <20091230100526.169642810@smtp.haun-online.de> Message-ID: <0KVH00EVTTMZDW10@mta3.srv.hcvlny.cv.net> At 05:05 AM 12/30/2009, Dirk Haun wrote: > >Feedback welcome. > >Anyone? I haven't tried the code so this may be nothing. Passing the $_FILES array back to the client feels wrong from a security point of view. I don't know what the attack vector would be but it just sounds like a bad idea. I know the code cleans out the path information from the "real file location" but are you sure you are not providing any configuration information to the client that it would not normally have? Just something you might want to double check twice. ---- Joe Mucchiello Throwing Dice Games http://www.throwingdice.com From dirk at haun-online.de Thu Dec 31 05:25:21 2009 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 31 Dec 2009 11:25:21 +0100 Subject: [geeklog-devel] editor=std Message-ID: <20091231102521.440279423@smtp.haun-online.de> Can anyone remember what the parameter editor=std in the story editor was supposed to do? E.g. in .../admin/story.php?mode=edit&editor=std&sid=20091231110958284 It is passed to the storyeditor() function as the fifth parameter - but that function only takes four parameters. It doesn't seem to have anything to do with the advanced editor mode, since that works without this parameter (obviously). So either this is something that was never implemented or it's for a feature that got lost along the way ... bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Thu Dec 31 09:48:08 2009 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 31 Dec 2009 15:48:08 +0100 Subject: [geeklog-devel] Cancel selects topic Message-ID: <20091231144808.815111349@smtp.haun-online.de> Here's another oddity in the Story Editor: When you hit the Cancel button, you are taken back to the list of stories - and there, the last story's topic is selected. So instead of the list of all stories, you only see those from this topic. Bug or feature? If it's considered a feature, hitting the Save button should result in the same behavior. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From websitemaster at cogeco.net Thu Dec 31 10:27:54 2009 From: websitemaster at cogeco.net (Tom) Date: Thu, 31 Dec 2009 10:27:54 -0500 Subject: [geeklog-devel] Cancel selects topic In-Reply-To: <20091231144808.815111349@smtp.haun-online.de> References: <20091231144808.815111349@smtp.haun-online.de> Message-ID: <00de01ca8a2d$d2d11680$78734380$@net> I would call that a bug. The way it should work if you hit cancel or save is either return to the first page of the list with everything set to the default or return to the last page the user was on in the list of stories with whatever he had the Topic, Search and limit Results set at. BTW, If you are currently looking at the stories did we every get this issue resolved? http://eight.pairlist.net/pipermail/geeklog-devel/2009-October/004390.html Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: December-31-09 9:48 AM To: geeklog-devel Subject: [geeklog-devel] Cancel selects topic Here's another oddity in the Story Editor: When you hit the Cancel button, you are taken back to the list of stories - and there, the last story's topic is selected. So instead of the list of all stories, you only see those from this topic. Bug or feature? If it's considered a feature, hitting the Save button should result in the same behavior. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 4732 (20091231) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From dirk at haun-online.de Thu Dec 31 11:02:04 2009 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 31 Dec 2009 17:02:04 +0100 Subject: [geeklog-devel] Cancel selects topic In-Reply-To: <00de01ca8a2d$d2d11680$78734380$@net> References: <20091231144808.815111349@smtp.haun-online.de> <00de01ca8a2d$d2d11680$78734380$@net> Message-ID: <20091231160204.993596017@smtp.haun-online.de> Tom wrote: >The way it should work if you hit cancel or save is either return to the >first page of the list with everything set to the default or > >return to the last page the user was on in the list of stories with whatever >he had the Topic, Search and limit Results set at. Personally, I would prefer the latter, but that's tricky to implement. Also see >BTW, If you are currently looking at the stories did we every get this issue >resolved? > >http://eight.pairlist.net/pipermail/geeklog-devel/2009-October/004390.html That would be So: No. LWC mentioned a patch in the comments and asked him to check with Rob. Haven't heard back from either of them. bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From robg at griffsweb.com Thu Dec 31 11:47:35 2009 From: robg at griffsweb.com (Rob Griffiths) Date: Thu, 31 Dec 2009 08:47:35 -0800 Subject: [geeklog-devel] Cancel selects topic In-Reply-To: <20091231160204.993596017@smtp.haun-online.de> References: <20091231144808.815111349@smtp.haun-online.de> <00de01ca8a2d$d2d11680$78734380$@net> <20091231160204.993596017@smtp.haun-online.de> Message-ID: <662A8166-AF9D-4B63-B8C4-0B6584293D81@griffsweb.com> On Dec 31, 2009, at 8:02 AM, Dirk Haun wrote: > That would be > > So: No. LWC mentioned a patch in the comments and asked him to check > with Rob. Haven't heard back from either of them. I haven't received anything directly from anyone that I recall. I saw the comment about the patched autotag, but that's all I've seen. If someone wants to give me basic directions -- assuming I have no knowledge of versioning systems -- I can install it locally and test. -rob. From websitemaster at cogeco.net Thu Dec 31 12:51:02 2009 From: websitemaster at cogeco.net (Tom) Date: Thu, 31 Dec 2009 12:51:02 -0500 Subject: [geeklog-devel] Cancel selects topic In-Reply-To: <662A8166-AF9D-4B63-B8C4-0B6584293D81@griffsweb.com> References: <20091231144808.815111349@smtp.haun-online.de> <00de01ca8a2d$d2d11680$78734380$@net> <20091231160204.993596017@smtp.haun-online.de> <662A8166-AF9D-4B63-B8C4-0B6584293D81@griffsweb.com> Message-ID: <00e901ca8a41$d13aa7f0$73aff7d0$@net> I will email LWC and see if he can pass along the code. I should have some time this weekend to take a look at this issue. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rob Griffiths Sent: December-31-09 11:48 AM To: Geeklog Development Subject: Re: [geeklog-devel] Cancel selects topic On Dec 31, 2009, at 8:02 AM, Dirk Haun wrote: > That would be > > So: No. LWC mentioned a patch in the comments and asked him to check > with Rob. Haven't heard back from either of them. I haven't received anything directly from anyone that I recall. I saw the comment about the patched autotag, but that's all I've seen. If someone wants to give me basic directions -- assuming I have no knowledge of versioning systems -- I can install it locally and test. -rob. _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 4732 (20091231) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com