From dirk at haun-online.de Sat Oct 4 17:30:50 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 4 Oct 2008 23:30:50 +0200 Subject: [geeklog-devel] Interesting bug - path collision In-Reply-To: <7b42e7470809160621v34a21d47m36e24151b9749a61@mail.gmail.com> References: <7b42e7470809022337i4aa001f0k6a5ddeff772e44b2@mail.gmail.com> <20080903175222.1719231789@smtp.haun-online.de> <8319e2d60809031057p6fc2db4br8d123687bc094836@mail.gmail.com> <20080904181548.134249445@smtp.haun-online.de> <7b42e7470809160621v34a21d47m36e24151b9749a61@mail.gmail.com> Message-ID: <20081004213050.1633150875@smtp.haun-online.de> Michael Jervis wrote: >Got a good answer their, since we include our own files with full >path, shove PEAR up the list. And in future, check for name conflicts. Only that we do already put the path to PEAR first: if( ini_set( 'include_path', $_CONF['path_pear'] . $separator . $curPHPIncludePath ) === false ) Using ini_set instead of set_include_path, but that's only because the latter is PHP >= 5.3 only ... Can somebody check please if the above code works as expected on Windows? And if using set_include_path would make a difference? bye, Dirk -- http://www.haun-online.de/accu/ From mjervis at gmail.com Sun Oct 5 04:00:33 2008 From: mjervis at gmail.com (Michael Jervis) Date: Sun, 5 Oct 2008 09:00:33 +0100 Subject: [geeklog-devel] Interesting bug - path collision In-Reply-To: <20081004213050.1633150875@smtp.haun-online.de> References: <7b42e7470809022337i4aa001f0k6a5ddeff772e44b2@mail.gmail.com> <20080903175222.1719231789@smtp.haun-online.de> <8319e2d60809031057p6fc2db4br8d123687bc094836@mail.gmail.com> <20080904181548.134249445@smtp.haun-online.de> <7b42e7470809160621v34a21d47m36e24151b9749a61@mail.gmail.com> <20081004213050.1633150875@smtp.haun-online.de> Message-ID: <7b42e7470810050100v461e6122vd6ad8fa26b65940@mail.gmail.com> > Can somebody check please if the above code works as expected on > Windows? And if using set_include_path would make a difference? Assuming that we haven't changed it, since I first reported the issue it doesn't work. I'll try and re-test it tomorrow. Mike From dirk at haun-online.de Sun Oct 5 04:55:52 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 5 Oct 2008 10:55:52 +0200 Subject: [geeklog-devel] Interesting bug - path collision In-Reply-To: <7b42e7470810050100v461e6122vd6ad8fa26b65940@mail.gmail.com> References: <7b42e7470809022337i4aa001f0k6a5ddeff772e44b2@mail.gmail.com> <20080903175222.1719231789@smtp.haun-online.de> <8319e2d60809031057p6fc2db4br8d123687bc094836@mail.gmail.com> <20080904181548.134249445@smtp.haun-online.de> <7b42e7470809160621v34a21d47m36e24151b9749a61@mail.gmail.com> <20081004213050.1633150875@smtp.haun-online.de> <7b42e7470810050100v461e6122vd6ad8fa26b65940@mail.gmail.com> Message-ID: <20081005085552.831703199@smtp.haun-online.de> Michael Jervis wrote: >Assuming that we haven't changed it, since I first reported the issue >it doesn't work. Badly worded, sorry. The code hasn't changed in a while and it obviously doesn't work. But does it manage to change the include path (which would mean that the problem is elsewhere) or is it failing to do that? In the latter case, does using set_include_path help? bye, Dirk -- http://www.haun-online.de/accu/ From dirk at haun-online.de Sun Oct 5 16:10:47 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 5 Oct 2008 22:10:47 +0200 Subject: [geeklog-devel] Porting over the GSoC install script changes Message-ID: <20081005201047.865162473@smtp.haun-online.de> So I've started looking into porting over the GSoC results into the main repository. Specifically Matt's work, since that's what I'm familiar with. In this case, I came to the conclusion that, as far as the actual install script is concerned, it's probably best to backport the changes that happened in 1.5.1 to the gsoc-2008 repository and then bring the whole thing back from there once that's done. For the moment, can I ask everyone to refrain from making changes that require database updates, please? As that would make things even more complicated. Thanks. Matt, are you around? bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From mjervis at gmail.com Mon Oct 6 14:44:59 2008 From: mjervis at gmail.com (Michael Jervis) Date: Mon, 6 Oct 2008 19:44:59 +0100 Subject: [geeklog-devel] Porting over the GSoC install script changes In-Reply-To: <20081005201047.865162473@smtp.haun-online.de> References: <20081005201047.865162473@smtp.haun-online.de> Message-ID: <7b42e7470810061144o22d8a8b4q57d26aed22478f8e@mail.gmail.com> > For the moment, can I ask everyone to refrain from making changes that > require database updates, please? As that would make things even more > complicated. Thanks. I was working on merging over the comments features, which have a couple of DB changes. I'll hold off on a commit until you are done. Mike. From dirk at haun-online.de Mon Oct 6 15:39:36 2008 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 6 Oct 2008 21:39:36 +0200 Subject: [geeklog-devel] Porting over the GSoC install script changes In-Reply-To: <7b42e7470810061144o22d8a8b4q57d26aed22478f8e@mail.gmail.com> References: <20081005201047.865162473@smtp.haun-online.de> <7b42e7470810061144o22d8a8b4q57d26aed22478f8e@mail.gmail.com> Message-ID: <20081006193936.375161851@smtp.haun-online.de> Michael Jervis wrote: >I'll hold off on a commit until you are done. If it's holding you off and you're sitting there twiddling your thumbs, please say so. Looks like I won't be getting anything done before the weekend anyway. bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From dirk at haun-online.de Sat Oct 11 13:30:32 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 11 Oct 2008 19:30:32 +0200 Subject: [geeklog-devel] Porting over the GSoC install script changes In-Reply-To: <7b42e7470810061144o22d8a8b4q57d26aed22478f8e@mail.gmail.com> References: <20081005201047.865162473@smtp.haun-online.de> <7b42e7470810061144o22d8a8b4q57d26aed22478f8e@mail.gmail.com> Message-ID: <20081011173032.1787580758@smtp.haun-online.de> Michael Jervis wrote: >I'll hold off on a commit until you are done. Okay, I've ported the code changes back and forth between the two repositories. No guarantees that anything other than a full fresh install works at this point. I could have started a new branch for this but I figured I'd rather not confuse everybody (including myself) with branches at this point. Consider the repository open for any commits again. To do: The plugin tables and permissions need to be ripped out of the main MySQL / MS SQL files and handled by the plugins. Matt, let's continue working on the main repository from now on. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Sun Oct 12 10:44:43 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 12 Oct 2008 16:44:43 +0200 Subject: [geeklog-devel] Porting over the GSoC install script changes In-Reply-To: <20081011173032.1787580758@smtp.haun-online.de> References: <20081005201047.865162473@smtp.haun-online.de> <7b42e7470810061144o22d8a8b4q57d26aed22478f8e@mail.gmail.com> <20081011173032.1787580758@smtp.haun-online.de> Message-ID: <20081012144443.1750738978@smtp.haun-online.de> >To do: The plugin tables and permissions need to be ripped out of the >main MySQL / MS SQL files and handled by the plugins. The "ripping out" part is done - currently, plugins are _not_ installed when you run the install script. bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From dirk at haun-online.de Sun Oct 19 15:34:44 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 19 Oct 2008 21:34:44 +0200 Subject: [geeklog-devel] Question about comment notifications Message-ID: <20081019193444.1422631290@smtp.haun-online.de> Jared, Mike (et al.), just checking: Comment notification (by email) was only implemented for registered users, right? The reason why I'm asking: Apparently, a WordPress plugin as well as Serendipity allow subscribing to comments simply by leaving an email address. And because of that, some German websites have now received cease and desist letters - since, according to German law, that functionality would require a confirmed opt-in (aka double opt-in). Not sure I follow that argument, but I can see the potential for abuse. If comment notifications require a valid account, we should be fine, though. bye, Dirk P.S. Two German articles: -- http://www.geeklog.net/ http://geeklog.info/ From mjervis at gmail.com Mon Oct 20 09:20:49 2008 From: mjervis at gmail.com (mjervis at gmail.com) Date: Mon, 20 Oct 2008 06:20:49 -0700 Subject: [geeklog-devel] Question about comment notifications Message-ID: <0015174c123cfa5d150459af2e0b@google.com> > just checking: Comment notification (by email) was only implemented for > > registered users, right? I beleive so, and if it turns out the world is flat, then I shall ensure it is made round... -------------- next part -------------- An HTML attachment was scrubbed... URL: From cordiste at free.fr Mon Oct 20 16:36:19 2008 From: cordiste at free.fr (cordiste) Date: Mon, 20 Oct 2008 22:36:19 +0200 Subject: [geeklog-devel] Link to description of plugin option Message-ID: <364575ed0810201336m4e671ca4j8a7c3ca5914afad2@mail.gmail.com> Hello devel team, In the Geeklog core config there is links to file docs/config.html Would a link to description of plugin option be implement soon? ::Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: