From websitemaster at cogeco.net Wed Jan 2 15:06:20 2013 From: websitemaster at cogeco.net (Tom) Date: Wed, 2 Jan 2013 15:06:20 -0500 Subject: [geeklog-devel] Geeklog 2.0.0 - Comments, Captcha and Plugins Message-ID: <001501cde924$a2bde1e0$e839a5a0$@cogeco.net> A note to all plugin developers: If your plugin uses comments and you have the Captcha plugin installed you will need to update your code slightly for the function plugin_savecomment_foo You will now need to take into account the constant COMMENT_ON_SAME_PAGE. If the attempt to save a comment by a user errors out (ie due to an incorrect captcha code), if the comment is on the same page as your plugin content then you need to only return the comment form, if it is not then you need to return the whole document. You can see the Staticpage and polls plugin in the repository for an example or see the code below: function plugin_savecomment_polls($title, $comment, $id, $pid, $postmode) { global $_CONF, $_TABLES, $LANG03, $_USER; $retval = ''; $commentcode = DB_getItem ($_TABLES['polltopics'], 'commentcode', "pid = '$id'"); if ($commentcode != 0) { return COM_refresh ($_CONF['site_url'] . '/index.php'); } $ret = CMT_saveComment ($title, $comment, $id, $pid, 'polls', $postmode); if ($ret > 0) { // failure //FIXME: some failures should not return to comment form $retval .= CMT_commentForm ($title, $comment, $id, $pid, 'polls', $LANG03[14], $postmode); if (!defined('COMMENT_ON_SAME_PAGE')) { $retval = COM_createHTMLDocument($retval, array('pagetitle' => $LANG03[1])); } else { if (!COMMENT_ON_SAME_PAGE) { $retval = COM_createHTMLDocument($retval, array('pagetitle' => $LANG03[1])); } } } else { // success $retval = COM_refresh ($_CONF['site_url'] . "/polls/index.php?pid=$id"); } return $retval; } From dirk at haun-online.de Thu Jan 3 02:21:44 2013 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 3 Jan 2013 08:21:44 +0100 Subject: [geeklog-devel] Drupal goes from Aloha to CKEditor Message-ID: <4B7EA521-E285-4C77-AEE3-769E38EB701F@haun-online.de> I found this interesting: Apparently Drupal had originally planned to use Aloha as their WYSIWYG editor but have now made a decision to use CKEditor instead: http://buytaert.net/from-aloha-to-ckeditor I've mentioned Aloha[1] before. There's two things I like about it: The in-place editing and the ties with the IKS community. In-place editing is something that I often wish we had when I find a typo in a post and then have to make the round-trip through the story editor just to fix it. Sounds like CKEditor is now offering something similar. The IKS stuff would offer us a way to get a bit of the semantic web into Geeklog. I don't see anything about this in the above announcement. Technically, CKEditor is the easier option for us since we already have an integration with its predecessor, FCKEditor. Aloha and in-place editing may require some radical changes here and there (I did actually whip up an Aloha "integration" of sorts back at that IKS workshop[2] in Amsterdam, but it couldn't save changes - it was more of a proof of concept, and a weak one at that). Anyway, it should be interesting to see how things work out for Drupal and what (if any) conclusions we can draw from this for Geeklog. bye, Dirk [1] http://aloha-editor.org/ [2] http://www.geeklog.net/article.php/iks-workshop-amsterdam -- http://www.themobilepresenter.com/ From cordiste at free.fr Thu Jan 3 08:17:14 2013 From: cordiste at free.fr (cordiste) Date: Thu, 3 Jan 2013 14:17:14 +0100 Subject: [geeklog-devel] Geeklog 2.0.0 - Comments, Captcha and Plugins In-Reply-To: <001501cde924$a2bde1e0$e839a5a0$@cogeco.net> References: <001501cde924$a2bde1e0$e839a5a0$@cogeco.net> Message-ID: Thanks for the note. Mediagallery, dowloads, and filemgmt plugins are concerned. Ben 2013/1/2 Tom : > A note to all plugin developers: > > If your plugin uses comments and you have the Captcha plugin installed you > will need to update your code slightly for the function > plugin_savecomment_foo > > You will now need to take into account the constant COMMENT_ON_SAME_PAGE. If > the attempt to save a comment by a user errors out (ie due to an incorrect > captcha code), if the comment is on the same page as your plugin content > then you need to only return the comment form, if it is not then you need to > return the whole document. You can see the Staticpage and polls plugin in > the repository for an example or see the code below: > > function plugin_savecomment_polls($title, $comment, $id, $pid, $postmode) > { > global $_CONF, $_TABLES, $LANG03, $_USER; > > $retval = ''; > > $commentcode = DB_getItem ($_TABLES['polltopics'], 'commentcode', > "pid = '$id'"); > if ($commentcode != 0) { > return COM_refresh ($_CONF['site_url'] . '/index.php'); > } > > $ret = CMT_saveComment ($title, $comment, $id, $pid, 'polls', > $postmode); > if ($ret > 0) { // failure //FIXME: some failures should not return to > comment form > $retval .= CMT_commentForm ($title, $comment, $id, $pid, 'polls', > $LANG03[14], $postmode); > > if (!defined('COMMENT_ON_SAME_PAGE')) { > $retval = COM_createHTMLDocument($retval, array('pagetitle' => > $LANG03[1])); > } else { > if (!COMMENT_ON_SAME_PAGE) { > $retval = COM_createHTMLDocument($retval, array('pagetitle' > => $LANG03[1])); > } > } > } else { // success > $retval = COM_refresh ($_CONF['site_url'] > . "/polls/index.php?pid=$id"); > } > > return $retval; > } > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From cordiste at free.fr Thu Jan 3 11:12:40 2013 From: cordiste at free.fr (cordiste) Date: Thu, 3 Jan 2013 17:12:40 +0100 Subject: [geeklog-devel] Drupal goes from Aloha to CKEditor In-Reply-To: <4B7EA521-E285-4C77-AEE3-769E38EB701F@haun-online.de> References: <4B7EA521-E285-4C77-AEE3-769E38EB701F@haun-online.de> Message-ID: ckeditor is still available for Geeklog with last jQuery plugin but I will remote it in the next release. Today, there is some very helpfull plugins for fckeditor (media gallery browser, google map, images manager with resize, crop, rotate, watermark and preview image tools, videos embed...) I'm not ready to change. Ben 2013/1/3 Dirk Haun : > I found this interesting: Apparently Drupal had originally planned to use Aloha as their WYSIWYG editor but have now made a decision to use CKEditor instead: > > http://buytaert.net/from-aloha-to-ckeditor > > I've mentioned Aloha[1] before. There's two things I like about it: The in-place editing and the ties with the IKS community. > > In-place editing is something that I often wish we had when I find a typo in a post and then have to make the round-trip through the story editor just to fix it. Sounds like CKEditor is now offering something similar. > > The IKS stuff would offer us a way to get a bit of the semantic web into Geeklog. I don't see anything about this in the above announcement. > > Technically, CKEditor is the easier option for us since we already have an integration with its predecessor, FCKEditor. Aloha and in-place editing may require some radical changes here and there (I did actually whip up an Aloha "integration" of sorts back at that IKS workshop[2] in Amsterdam, but it couldn't save changes - it was more of a proof of concept, and a weak one at that). > > Anyway, it should be interesting to see how things work out for Drupal and what (if any) conclusions we can draw from this for Geeklog. > > bye, Dirk > > [1] http://aloha-editor.org/ > [2] http://www.geeklog.net/article.php/iks-workshop-amsterdam > > > -- > http://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From websitemaster at cogeco.net Fri Jan 4 10:13:59 2013 From: websitemaster at cogeco.net (Tom) Date: Fri, 4 Jan 2013 10:13:59 -0500 Subject: [geeklog-devel] Geeklog and 404 Errors Message-ID: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> I notice that Google bot was crawling pages of one of my plugins that do not exist (ie ...&page=2813). I am not sure how Google found them (as the site didn't create a link to them) but never less Google did crawl a bunch of these pages. I checked on a few webmaster forums to figure out what was the right way to handle this. For example: 1) Return just the last page 2) return a 404 3) do a redirect (301) to the last page My first thought was option 3 was the best but after a few discussions most people suggested a 404 error since Google is picky about things like this. Anyways I thought I would double check on how Geeklog handles an non existing page number for articles, topic, comments, etc... A) For non-existing Articles we redirect back to the homepage. B) For non-existing Topic page numbers and topic ids we display a No News to Display Message C) For non-existing comment pages we just show the item with no comments but with comment page numbers Item C needs to be fixed and I would think a 404 should be returned. I also wonder if we should do the same for items A and B? Geeklog also has a 404.php page which as far as I can tell is not used. It also doesn't seem to return a 404 error code but just contains a nice message to the user with a few link options. I am wondering if we should ditch this page but create a lib-common function that shows something similar that also includes the correct 404 header so search engines know not to visit. This way we would have a constant 404 error message across the site. Ideas, Thoughts? Tom PS This would be implemented in Geeklog 2.0.1 since we are on a feature freeze for 2.0.0 From dirk at haun-online.de Fri Jan 4 10:37:15 2013 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 4 Jan 2013 16:37:15 +0100 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> Message-ID: Tom wrote: > Geeklog also has a 404.php page which as far as I can tell is not used. You're supposed to configure your webserver to display it in case of a 404. E.g. for Apache: ErrorDocument 404 /404.php > It > also doesn't seem to return a 404 error code but just contains a nice > message to the user with a few link options. I am wondering if we should > ditch this page but create a lib-common function that shows something > similar that also includes the correct 404 header so search engines know not > to visit. This way we would have a constant 404 error message across the > site. I can't remember the details, but the code that display the 404 page should not itself send a 404 - I think it was because the webserver already does it, if configured as shown above. Check some non-existing URL on geeklog.net - you'll see that it correctly returns a 404. We should obviously explain somewhere how to use the 404.php, but other than that I don't see anything wrong with it as such. bye, Dirk -- http://www.themobilepresenter.com/ From rouslan at placella.com Fri Jan 4 11:14:37 2013 From: rouslan at placella.com (Rouslan Placella) Date: Fri, 04 Jan 2013 16:14:37 +0000 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> Message-ID: <50E6FFED.9050003@placella.com> On 01/04/2013 03:37 PM, Dirk Haun wrote: > Tom wrote: > >> Geeklog also has a 404.php page which as far as I can tell is not used. > > You're supposed to configure your webserver to display it in case of a 404. E.g. for Apache: > > ErrorDocument 404 /404.php > > >> It >> also doesn't seem to return a 404 error code but just contains a nice >> message to the user with a few link options. I am wondering if we should >> ditch this page but create a lib-common function that shows something >> similar that also includes the correct 404 header so search engines know not >> to visit. This way we would have a constant 404 error message across the >> site. > > > I can't remember the details, but the code that display the 404 page should not itself send a 404 - I think it was because the webserver already does it, if configured as shown above. Check some non-existing URL on geeklog.net - you'll see that it correctly returns a 404. > > We should obviously explain somewhere how to use the 404.php, but other than that I don't see anything wrong with it as such. Dirk, that's physically missing pages you're talking about (e.g: http://geeklog.net/nonexistent.php). For logically missing pages, Tom is right about sending the 404 header from gl (http://geeklog.net/article.php?id=nonexistent), the webserver won't send an error, since the page does actually exist... Bye, Rouslan From komma at ivywe.co.jp Fri Jan 4 11:47:01 2013 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEI=?=) Date: Sat, 5 Jan 2013 01:47:01 +0900 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: <50E6FFED.9050003@placella.com> References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> <50E6FFED.9050003@placella.com> Message-ID: Tom, Static Page plugin display error message. I would think a 404 should be returned in this plugin, too. Dirk, I want wiki document about 404.php, too. 404.php is customized in our site. http://www.geeklog.jp/nonexistent .htaccess (as Dirk said) ErrorDocument 404 /404.php Feature request: Configuration set staticpage id (e.g. "_404") for 404 error. -- Ivy 2013/1/5 Rouslan Placella : > On 01/04/2013 03:37 PM, Dirk Haun wrote: >> >> Tom wrote: >> >>> Geeklog also has a 404.php page which as far as I can tell is not used. >> >> >> You're supposed to configure your webserver to display it in case of a >> 404. E.g. for Apache: >> >> ErrorDocument 404 /404.php >> >> >>> It >>> also doesn't seem to return a 404 error code but just contains a nice >>> message to the user with a few link options. I am wondering if we should >>> ditch this page but create a lib-common function that shows something >>> similar that also includes the correct 404 header so search engines know >>> not >>> to visit. This way we would have a constant 404 error message across the >>> site. >> >> >> >> I can't remember the details, but the code that display the 404 page >> should > > not itself send a 404 - I think it was because the webserver already does > it, > if configured as shown above. Check some non-existing URL on geeklog.net - > you'll see that it correctly returns a 404. >> >> >> We should obviously explain somewhere how to use the 404.php, but other >> than > > that I don't see anything wrong with it as such. > > Dirk, that's physically missing pages you're talking about (e.g: > http://geeklog.net/nonexistent.php). For logically missing pages, Tom is > right about sending the 404 header from gl > (http://geeklog.net/article.php?id=nonexistent), the webserver won't send an > error, since the page does actually exist... > > Bye, > Rouslan > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Fri Jan 4 12:50:02 2013 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 4 Jan 2013 18:50:02 +0100 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: <50E6FFED.9050003@placella.com> References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> <50E6FFED.9050003@placella.com> Message-ID: <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> Rouslan Placella wrote: > Dirk, that's physically missing pages you're talking about (e.g: http://geeklog.net/nonexistent.php). For logically missing pages, Tom is right about sending the 404 header from gl (http://geeklog.net/article.php?id=nonexistent), the webserver won't send an error, since the page does actually exist? Right. I was only addressing the question about the 404.php - hadn't really thought through the other aspect yet. Geeklog already sends the proper HTTP status codes where appropriate (e.g. 403, 500), so sending a 404 when calling up an item that does not exist sounds sensible. I think the main reason why we're not doing it yet was the concern that it may give away information. Strictly speaking, if you don't have the rights to read an article, you should get a 403 but if it does not exist, you should get a 404. In both cases, we currently redirect the user to the front page so as not to give away the information "this article exists but you are not allowed to read it". Given that we're The Secure CMS, we should at least think this through before we change it. bye, Dirk -- http://www.themobilepresenter.com/ From cordiste at free.fr Fri Jan 4 14:55:40 2013 From: cordiste at free.fr (cordiste) Date: Fri, 4 Jan 2013 20:55:40 +0100 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> <50E6FFED.9050003@placella.com> <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> Message-ID: We also use the 404.php script on geeklog.fr http://www.geeklog.fr/nonexistent.php As Ivy say a configuration set for a staticpage id (e.g. "_404") for a 404 error will be a nioce feature. Ben 2013/1/4 Dirk Haun : > Rouslan Placella wrote: > >> Dirk, that's physically missing pages you're talking about (e.g: http://geeklog.net/nonexistent.php). For logically missing pages, Tom is right about sending the 404 header from gl (http://geeklog.net/article.php?id=nonexistent), the webserver won't send an error, since the page does actually exist? > > Right. I was only addressing the question about the 404.php - hadn't really thought through the other aspect yet. > > Geeklog already sends the proper HTTP status codes where appropriate (e.g. 403, 500), so sending a 404 when calling up an item that does not exist sounds sensible. > > I think the main reason why we're not doing it yet was the concern that it may give away information. Strictly speaking, if you don't have the rights to read an article, you should get a 403 but if it does not exist, you should get a 404. In both cases, we currently redirect the user to the front page so as not to give away the information "this article exists but you are not allowed to read it". > > Given that we're The Secure CMS, we should at least think this through before we change it. > > bye, Dirk > > > -- > http://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From websitemaster at cogeco.net Fri Jan 4 15:38:55 2013 From: websitemaster at cogeco.net (Tom) Date: Fri, 4 Jan 2013 15:38:55 -0500 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> <50E6FFED.9050003@placella.com> <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> Message-ID: <00ff01cdeabb$8397f3d0$8ac7db70$@cogeco.net> >> we should at least think this through before we change it. That's why I started this thread. ;-) The only other thing I thought of is comment paging can be different per user depending on what the comment page limit is set at. So a comment page 5 could display for one user but not another (like anonymous) if his comments per page is set higher. This could create a situation if that user put a link to page 5 on his website or whatever for someone to visit. This situation isn't really too important in my opinion as I doubt it would happen too often but I thought I would bring it up. I guess we have 2 main things to think about. 1) If the id of the item exists or not (staticpage, article, topic, comment, etc) and if they have access to it or not. Right now the message tells the user the item either doesn't exist or they do not have access. Basically we are telling them it is a 404 or 403. The problem is when search engines find these type of links they do not realize it is a 404 or 403 and proceed to index the page. I still think we should set a 404 error and have a general message (like how 404.php works) stating that the page doesn't exist or that they may not have access and then point them to the home page or search page. A 404 error gives them less information that a 403 error. 2) Going over the page limits for things like comments and topics. I think this one is relatively straight forward and we should return a 404. I also would want to add some logging for this just so you can find out who is trying to find what non-existent page. 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: January-04-13 12:50 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog and 404 Errors Rouslan Placella wrote: > Dirk, that's physically missing pages you're talking about (e.g: http://geeklog.net/nonexistent.php). For logically missing pages, Tom is right about sending the 404 header from gl (http://geeklog.net/article.php?id=nonexistent), the webserver won't send an error, since the page does actually exist. Right. I was only addressing the question about the 404.php - hadn't really thought through the other aspect yet. Geeklog already sends the proper HTTP status codes where appropriate (e.g. 403, 500), so sending a 404 when calling up an item that does not exist sounds sensible. I think the main reason why we're not doing it yet was the concern that it may give away information. Strictly speaking, if you don't have the rights to read an article, you should get a 403 but if it does not exist, you should get a 404. In both cases, we currently redirect the user to the front page so as not to give away the information "this article exists but you are not allowed to read it". Given that we're The Secure CMS, we should at least think this through before we change it. bye, Dirk -- http://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From vfuria at gmail.com Fri Jan 4 15:56:49 2013 From: vfuria at gmail.com (Vincent Furia) Date: Fri, 4 Jan 2013 13:56:49 -0700 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: <00ff01cdeabb$8397f3d0$8ac7db70$@cogeco.net> References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> <50E6FFED.9050003@placella.com> <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> <00ff01cdeabb$8397f3d0$8ac7db70$@cogeco.net> Message-ID: On Fri, Jan 4, 2013 at 1:38 PM, Tom wrote: > 2) Going over the page limits for things like comments and topics. I think > this one is relatively straight forward and we should return a 404. > I agree completely. When implemented, it would be nice if both 404.php and any logically missing pages returning 404 both looked the same (and used the same code) for consistency and maintainability. -Vinny -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Fri Jan 4 16:53:14 2013 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 4 Jan 2013 22:53:14 +0100 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: <00ff01cdeabb$8397f3d0$8ac7db70$@cogeco.net> References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> <50E6FFED.9050003@placella.com> <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> <00ff01cdeabb$8397f3d0$8ac7db70$@cogeco.net> Message-ID: Tom wrote: > 1) If the id of the item exists or not (staticpage, article, topic, > comment, etc) and if they have access to it or not. Right now the message > tells the user the item either doesn't exist or they do not have access. > Basically we are telling them it is a 404 or 403. The problem is when search > engines find these type of links they do not realize it is a 404 or 403 and > proceed to index the page. I still think we should set a 404 error and have > a general message (like how 404.php works) stating that the page doesn't > exist or that they may not have access and then point them to the home page > or search page. A 404 error gives them less information that a 403 error. Let's see: A 404 would be an improvement over the current situation. And that includes the situations where a 403 would be more appropriate. A malicious user trying to gather whatever information that way would still not be able to tell the difference between "doesn't exist" and "not allowed". A bot would never be able to access a 403'd page anyway, so we might as well tell them that the page doesn't exist. In other words, if we always send a 404 instead of always redirecting to the front page (for non-existing items), we would improve things and still not give any information away. Right? > 2) Going over the page limits for things like comments and topics. I think > this one is relatively straight forward and we should return a 404. I had a quick look through the list of HTTP status codes to see if there's anything that would be more appropriate but I don't see anything (some come close, but refer to specific HTTP header fields which we don't use). So: What Vinny said. bye, Dirk -- http://www.themobilepresenter.com/ From websitemaster at cogeco.net Fri Jan 4 20:37:57 2013 From: websitemaster at cogeco.net (Tom) Date: Fri, 4 Jan 2013 20:37:57 -0500 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> <50E6FFED.9050003@placella.com> <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> <00ff01cdeabb$8397f3d0$8ac7db70$@cogeco.net> Message-ID: <012701cdeae5$4a51af10$def50d30$@cogeco.net> Sounds good. I will wait a few days to see if anyone else has anything to add before putting in the feature request. As Vinny said the 404.php page should use much of the same code as possible with the new function. I will also mention in the request to add a config option to enable a 404.log file (or should this go in the error log?) since it would be nice to know if anyone is trying to access pages that do not exist. 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: January-04-13 4:53 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog and 404 Errors Tom wrote: > 1) If the id of the item exists or not (staticpage, article, topic, > comment, etc) and if they have access to it or not. Right now the > message tells the user the item either doesn't exist or they do not have access. > Basically we are telling them it is a 404 or 403. The problem is when > search engines find these type of links they do not realize it is a > 404 or 403 and proceed to index the page. I still think we should set > a 404 error and have a general message (like how 404.php works) > stating that the page doesn't exist or that they may not have access > and then point them to the home page or search page. A 404 error gives them less information that a 403 error. Let's see: A 404 would be an improvement over the current situation. And that includes the situations where a 403 would be more appropriate. A malicious user trying to gather whatever information that way would still not be able to tell the difference between "doesn't exist" and "not allowed". A bot would never be able to access a 403'd page anyway, so we might as well tell them that the page doesn't exist. In other words, if we always send a 404 instead of always redirecting to the front page (for non-existing items), we would improve things and still not give any information away. Right? > 2) Going over the page limits for things like comments and topics. I > think this one is relatively straight forward and we should return a 404. I had a quick look through the list of HTTP status codes to see if there's anything that would be more appropriate but I don't see anything (some come close, but refer to specific HTTP header fields which we don't use). So: What Vinny said. bye, Dirk -- http://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From vfuria at gmail.com Sat Jan 5 01:27:20 2013 From: vfuria at gmail.com (Vincent Furia) Date: Fri, 4 Jan 2013 23:27:20 -0700 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: <012701cdeae5$4a51af10$def50d30$@cogeco.net> References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> <50E6FFED.9050003@placella.com> <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> <00ff01cdeabb$8397f3d0$8ac7db70$@cogeco.net> <012701cdeae5$4a51af10$def50d30$@cogeco.net> Message-ID: On Fri, Jan 4, 2013 at 6:37 PM, Tom wrote: > I will also mention in the request to add a config > option to enable a 404.log file > Isn't that kind of redundant? The web server (if configured to) will already record 404s. -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Sat Jan 5 09:26:21 2013 From: websitemaster at cogeco.net (Tom) Date: Sat, 5 Jan 2013 09:26:21 -0500 Subject: [geeklog-devel] Geeklog and 404 Errors In-Reply-To: References: <00ed01cdea8e$1f676da0$5e3648e0$@cogeco.net> <50E6FFED.9050003@placella.com> <36F6902C-9706-43AE-AFC7-A0568E65E039@haun-online.de> <00ff01cdeabb$8397f3d0$8ac7db70$@cogeco.net> <012701cdeae5$4a51af10$def50d30$@cogeco.net> Message-ID: <013701cdeb50$a255b790$e70126b0$@cogeco.net> Yeah I know. I guess I like things easy to access since most times I would have to remote admin into the server to find out. Tom From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Vincent Furia Sent: January-05-13 1:27 AM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog and 404 Errors On Fri, Jan 4, 2013 at 6:37 PM, Tom wrote: I will also mention in the request to add a config option to enable a 404.log file Isn't that kind of redundant? The web server (if configured to) will already record 404s. -------------- next part -------------- An HTML attachment was scrubbed... URL: From komma at ivywe.co.jp Sat Jan 5 13:21:54 2013 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEI=?=) Date: Sun, 6 Jan 2013 03:21:54 +0900 Subject: [geeklog-devel] Postgres and MS SQL? In-Reply-To: <006101cde046$176b8f70$4642ae50$@cogeco.net> References: <006101cde046$176b8f70$4642ae50$@cogeco.net> Message-ID: Now Japanese member is working for Postgres in Geeklog 2.0.0rc1. -- Ivy 2012/12/22 Tom : > Maybe with 1.8.2 mark as unsupported. We should put an article up on > Geeklog.net with the release stating that these db options will be dropped > eventually if no one wants to step up and help out with testing, etc.. for > MSSQL and Postgres > > For 2.0.0 we can leave the code in but disable the 2 options in the install. > > If by near the end of the release for 2.0.1 no one has helped out we pull > the code. > > Just an idea... > > 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-22-12 4:58 AM > To: Geeklog Development > Subject: [geeklog-devel] Postgres and MS SQL? > > What do we do with Postgres and MS SQL support in 2.0.0? Both are pretty > much broken (or at least Postgres is broken and I assume MS SQL isn't > working either - can't test it). > > At the very least, we should mark them as "unsupported". > > bye, Dirk > > > -- > http://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Sat Jan 5 15:24:57 2013 From: websitemaster at cogeco.net (Tom) Date: Sat, 5 Jan 2013 15:24:57 -0500 Subject: [geeklog-devel] Postgres and MS SQL? In-Reply-To: References: <006101cde046$176b8f70$4642ae50$@cogeco.net> Message-ID: <014b01cdeb82$bab54490$301fcdb0$@cogeco.net> Let us know how it goes. If it works out he can submit a patch so we can update the repository here. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? Sent: January-05-13 1:22 PM To: Geeklog Development Subject: Re: [geeklog-devel] Postgres and MS SQL? Now Japanese member is working for Postgres in Geeklog 2.0.0rc1. -- Ivy 2012/12/22 Tom : > Maybe with 1.8.2 mark as unsupported. We should put an article up on > Geeklog.net with the release stating that these db options will be > dropped eventually if no one wants to step up and help out with > testing, etc.. for MSSQL and Postgres > > For 2.0.0 we can leave the code in but disable the 2 options in the install. > > If by near the end of the release for 2.0.1 no one has helped out we > pull the code. > > Just an idea... > > 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-22-12 4:58 AM > To: Geeklog Development > Subject: [geeklog-devel] Postgres and MS SQL? > > What do we do with Postgres and MS SQL support in 2.0.0? Both are > pretty much broken (or at least Postgres is broken and I assume MS SQL > isn't working either - can't test it). > > At the very least, we should mark them as "unsupported". > > bye, Dirk > > > -- > http://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From komma at ivywe.co.jp Sat Jan 5 21:00:02 2013 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEIgR2Vla2xvZyBJdnlXZQ==?=) Date: Sun, 6 Jan 2013 11:00:02 +0900 Subject: [geeklog-devel] Postgres and MS SQL? In-Reply-To: <014b01cdeb82$bab54490$301fcdb0$@cogeco.net> References: <006101cde046$176b8f70$4642ae50$@cogeco.net> <014b01cdeb82$bab54490$301fcdb0$@cogeco.net> Message-ID: It works fine now! Errors are in setting block title "what's new" sql and others. He will submit a patch today. Ivy 2013/1/6 Tom : > Let us know how it goes. If it works out he can submit a patch so we can > update the repository here. > > Tom > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? > Sent: January-05-13 1:22 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Postgres and MS SQL? > > Now Japanese member is working for Postgres in Geeklog 2.0.0rc1. > > -- > Ivy > > > 2012/12/22 Tom : >> Maybe with 1.8.2 mark as unsupported. We should put an article up on >> Geeklog.net with the release stating that these db options will be >> dropped eventually if no one wants to step up and help out with >> testing, etc.. for MSSQL and Postgres >> >> For 2.0.0 we can leave the code in but disable the 2 options in the > install. >> >> If by near the end of the release for 2.0.1 no one has helped out we >> pull the code. >> >> Just an idea... >> >> 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-22-12 4:58 AM >> To: Geeklog Development >> Subject: [geeklog-devel] Postgres and MS SQL? >> >> What do we do with Postgres and MS SQL support in 2.0.0? Both are >> pretty much broken (or at least Postgres is broken and I assume MS SQL >> isn't working either - can't test it). >> >> At the very least, we should mark them as "unsupported". >> >> bye, Dirk >> >> >> -- >> http://www.themobilepresenter.com/ >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Sun Jan 6 09:47:04 2013 From: websitemaster at cogeco.net (Tom) Date: Sun, 6 Jan 2013 09:47:04 -0500 Subject: [geeklog-devel] Postgres and MS SQL? In-Reply-To: References: <006101cde046$176b8f70$4642ae50$@cogeco.net> <014b01cdeb82$bab54490$301fcdb0$@cogeco.net> Message-ID: <016d01cdec1c$b1800910$14801b30$@cogeco.net> I see the patch. Is this patch for the latest in the repository or for Geeklog 1.8.2? Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? Geeklog IvyWe Sent: January-05-13 9:00 PM To: Geeklog Development Subject: Re: [geeklog-devel] Postgres and MS SQL? It works fine now! Errors are in setting block title "what's new" sql and others. He will submit a patch today. Ivy 2013/1/6 Tom : > Let us know how it goes. If it works out he can submit a patch so we > can update the repository here. > > Tom > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? > Sent: January-05-13 1:22 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Postgres and MS SQL? > > Now Japanese member is working for Postgres in Geeklog 2.0.0rc1. > > -- > Ivy > > > 2012/12/22 Tom : >> Maybe with 1.8.2 mark as unsupported. We should put an article up on >> Geeklog.net with the release stating that these db options will be >> dropped eventually if no one wants to step up and help out with >> testing, etc.. for MSSQL and Postgres >> >> For 2.0.0 we can leave the code in but disable the 2 options in the > install. >> >> If by near the end of the release for 2.0.1 no one has helped out we >> pull the code. >> >> Just an idea... >> >> 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-22-12 4:58 AM >> To: Geeklog Development >> Subject: [geeklog-devel] Postgres and MS SQL? >> >> What do we do with Postgres and MS SQL support in 2.0.0? Both are >> pretty much broken (or at least Postgres is broken and I assume MS >> SQL isn't working either - can't test it). >> >> At the very least, we should mark them as "unsupported". >> >> bye, Dirk >> >> >> -- >> http://www.themobilepresenter.com/ >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From komma at ivywe.co.jp Sun Jan 6 11:58:45 2013 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEI=?=) Date: Mon, 7 Jan 2013 01:58:45 +0900 Subject: [geeklog-devel] Postgres and MS SQL? In-Reply-To: <016d01cdec1c$b1800910$14801b30$@cogeco.net> References: <006101cde046$176b8f70$4642ae50$@cogeco.net> <014b01cdeb82$bab54490$301fcdb0$@cogeco.net> <016d01cdec1c$b1800910$14801b30$@cogeco.net> Message-ID: Probably 1.8.2. It seems that he thought that 1.8.2 was requested. I requested 2.0.0 again. Ivy 2013/1/6 Tom > I see the patch. Is this patch for the latest in the repository or for > Geeklog 1.8.2? > > Tom > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? Geeklog > IvyWe > Sent: January-05-13 9:00 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Postgres and MS SQL? > > It works fine now! > Errors are in setting block title "what's new" sql and others. > He will submit a patch today. > > Ivy > > > 2013/1/6 Tom : > > Let us know how it goes. If it works out he can submit a patch so we > > can update the repository here. > > > > Tom > > > > -----Original Message----- > > From: geeklog-devel-bounces at lists.geeklog.net > > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? > > Sent: January-05-13 1:22 PM > > To: Geeklog Development > > Subject: Re: [geeklog-devel] Postgres and MS SQL? > > > > Now Japanese member is working for Postgres in Geeklog 2.0.0rc1. > > > > -- > > Ivy > > > > > > 2012/12/22 Tom : > >> Maybe with 1.8.2 mark as unsupported. We should put an article up on > >> Geeklog.net with the release stating that these db options will be > >> dropped eventually if no one wants to step up and help out with > >> testing, etc.. for MSSQL and Postgres > >> > >> For 2.0.0 we can leave the code in but disable the 2 options in the > > install. > >> > >> If by near the end of the release for 2.0.1 no one has helped out we > >> pull the code. > >> > >> Just an idea... > >> > >> 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-22-12 4:58 AM > >> To: Geeklog Development > >> Subject: [geeklog-devel] Postgres and MS SQL? > >> > >> What do we do with Postgres and MS SQL support in 2.0.0? Both are > >> pretty much broken (or at least Postgres is broken and I assume MS > >> SQL isn't working either - can't test it). > >> > >> At the very least, we should mark them as "unsupported". > >> > >> bye, Dirk > >> > >> > >> -- > >> http://www.themobilepresenter.com/ > >> > >> _______________________________________________ > >> geeklog-devel mailing list > >> geeklog-devel at lists.geeklog.net > >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > >> > >> _______________________________________________ > >> geeklog-devel mailing list > >> geeklog-devel at lists.geeklog.net > >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > > geeklog-devel mailing list > > geeklog-devel at lists.geeklog.net > > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > > > _______________________________________________ > > geeklog-devel mailing list > > geeklog-devel at lists.geeklog.net > > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Sun Jan 6 12:43:30 2013 From: websitemaster at cogeco.net (Tom) Date: Sun, 6 Jan 2013 12:43:30 -0500 Subject: [geeklog-devel] Postgres and MS SQL? In-Reply-To: References: <006101cde046$176b8f70$4642ae50$@cogeco.net> <014b01cdeb82$bab54490$301fcdb0$@cogeco.net> <016d01cdec1c$b1800910$14801b30$@cogeco.net> Message-ID: <017c01cdec35$57213bb0$0563b310$@cogeco.net> Did you know if he tested any of the parts of Geeklog 2.0.0 or just the install? Tom From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? Sent: January-06-13 11:59 AM To: Geeklog Development Subject: Re: [geeklog-devel] Postgres and MS SQL? Probably 1.8.2. It seems that he thought that 1.8.2 was requested. I requested 2.0.0 again. Ivy 2013/1/6 Tom I see the patch. Is this patch for the latest in the repository or for Geeklog 1.8.2? Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? Geeklog IvyWe Sent: January-05-13 9:00 PM To: Geeklog Development Subject: Re: [geeklog-devel] Postgres and MS SQL? It works fine now! Errors are in setting block title "what's new" sql and others. He will submit a patch today. Ivy 2013/1/6 Tom : > Let us know how it goes. If it works out he can submit a patch so we > can update the repository here. > > Tom > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? > Sent: January-05-13 1:22 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Postgres and MS SQL? > > Now Japanese member is working for Postgres in Geeklog 2.0.0rc1. > > -- > Ivy > > > 2012/12/22 Tom : >> Maybe with 1.8.2 mark as unsupported. We should put an article up on >> Geeklog.net with the release stating that these db options will be >> dropped eventually if no one wants to step up and help out with >> testing, etc.. for MSSQL and Postgres >> >> For 2.0.0 we can leave the code in but disable the 2 options in the > install. >> >> If by near the end of the release for 2.0.1 no one has helped out we >> pull the code. >> >> Just an idea... >> >> 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-22-12 4:58 AM >> To: Geeklog Development >> Subject: [geeklog-devel] Postgres and MS SQL? >> >> What do we do with Postgres and MS SQL support in 2.0.0? Both are >> pretty much broken (or at least Postgres is broken and I assume MS >> SQL isn't working either - can't test it). >> >> At the very least, we should mark them as "unsupported". >> >> bye, Dirk >> >> >> -- >> http://www.themobilepresenter.com/ >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From komma at ivywe.co.jp Sun Jan 6 12:52:23 2013 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEI=?=) Date: Mon, 7 Jan 2013 02:52:23 +0900 Subject: [geeklog-devel] Postgres and MS SQL? In-Reply-To: <017c01cdec35$57213bb0$0563b310$@cogeco.net> References: <006101cde046$176b8f70$4642ae50$@cogeco.net> <014b01cdeb82$bab54490$301fcdb0$@cogeco.net> <016d01cdec1c$b1800910$14801b30$@cogeco.net> <017c01cdec35$57213bb0$0563b310$@cogeco.net> Message-ID: Just install, I guess. Next time, I will test at the site. 2013/1/7 Tom > Did you know if he tested any of the parts of Geeklog 2.0.0 or just the > install?**** > > ** ** > > Tom**** > > ** ** > > *From:* geeklog-devel-bounces at lists.geeklog.net [mailto: > geeklog-devel-bounces at lists.geeklog.net] *On Behalf Of *???? > *Sent:* January-06-13 11:59 AM > *To:* Geeklog Development > > *Subject:* Re: [geeklog-devel] Postgres and MS SQL?**** > > ** ** > > Probably 1.8.2.**** > > It seems that he thought that 1.8.2 was requested. **** > > I requested 2.0.0 again.**** > > ** ** > > Ivy**** > > ** ** > > ** ** > > 2013/1/6 Tom **** > > I see the patch. Is this patch for the latest in the repository or for > Geeklog 1.8.2?**** > > > Tom > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net**** > > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? Geeklog > IvyWe > Sent: January-05-13 9:00 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Postgres and MS SQL? > > It works fine now! > Errors are in setting block title "what's new" sql and others. > He will submit a patch today. > > Ivy > > > 2013/1/6 Tom : > > Let us know how it goes. If it works out he can submit a patch so we > > can update the repository here. > > > > Tom > > > > -----Original Message----- > > From: geeklog-devel-bounces at lists.geeklog.net > > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ???? > > Sent: January-05-13 1:22 PM > > To: Geeklog Development > > Subject: Re: [geeklog-devel] Postgres and MS SQL? > > > > Now Japanese member is working for Postgres in Geeklog 2.0.0rc1. > > > > -- > > Ivy > > > > > > 2012/12/22 Tom : > >> Maybe with 1.8.2 mark as unsupported. We should put an article up on > >> Geeklog.net with the release stating that these db options will be > >> dropped eventually if no one wants to step up and help out with > >> testing, etc.. for MSSQL and Postgres > >> > >> For 2.0.0 we can leave the code in but disable the 2 options in the > > install. > >> > >> If by near the end of the release for 2.0.1 no one has helped out we > >> pull the code. > >> > >> Just an idea... > >> > >> 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-22-12 4:58 AM > >> To: Geeklog Development > >> Subject: [geeklog-devel] Postgres and MS SQL? > >> > >> What do we do with Postgres and MS SQL support in 2.0.0? Both are > >> pretty much broken (or at least Postgres is broken and I assume MS > >> SQL isn't working either - can't test it). > >> > >> At the very least, we should mark them as "unsupported". > >> > >> bye, Dirk > >> > >> > >> -- > >> http://www.themobilepresenter.com/ > >> > >> _______________________________________________ > >> geeklog-devel mailing list > >> geeklog-devel at lists.geeklog.net > >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > >> > >> _______________________________________________ > >> geeklog-devel mailing list > >> geeklog-devel at lists.geeklog.net > >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > > geeklog-devel mailing list > > geeklog-devel at lists.geeklog.net > > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > > > _______________________________________________ > > geeklog-devel mailing list > > geeklog-devel at lists.geeklog.net > > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel**** > > ** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Sun Jan 6 13:02:09 2013 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 6 Jan 2013 19:02:09 +0100 Subject: [geeklog-devel] Postgres and MS SQL? In-Reply-To: References: <006101cde046$176b8f70$4642ae50$@cogeco.net> <014b01cdeb82$bab54490$301fcdb0$@cogeco.net> <016d01cdec1c$b1800910$14801b30$@cogeco.net> Message-ID: <2F37D231-4815-44A8-8414-79B67E363704@haun-online.de> > Probably 1.8.2. > It seems that he thought that 1.8.2 was requested. > I requested 2.0.0 again. Postgres may behave differently in 1.8.2 and 2.0.0. I made some attempts to fix it a few months ago and last time I checked, at least the install went through (in 2.0.0, but not in 1.8.2). bye, Dirk -- http://www.themobilepresenter.com/ From komma at ivywe.co.jp Mon Jan 7 12:04:11 2013 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEI=?=) Date: Tue, 8 Jan 2013 02:04:11 +0900 Subject: [geeklog-devel] Postgres and MS SQL? In-Reply-To: <2F37D231-4815-44A8-8414-79B67E363704@haun-online.de> References: <006101cde046$176b8f70$4642ae50$@cogeco.net> <014b01cdeb82$bab54490$301fcdb0$@cogeco.net> <016d01cdec1c$b1800910$14801b30$@cogeco.net> <2F37D231-4815-44A8-8414-79B67E363704@haun-online.de> Message-ID: intrajp submitted a patch for Geeklog 2.0.0rc1 today. http://project.geeklog.net/tracking/view.php?id=1547 This patch is only remove ' from insert db sql. But now Geeklog works on PostgreSQL. He said that Geeklog 1.8.2 was install error on PostgreSQL, too. So yesterday's patch is needed. Only install test. Ivy 2013/1/7 Dirk Haun : >> Probably 1.8.2. >> It seems that he thought that 1.8.2 was requested. >> I requested 2.0.0 again. > > Postgres may behave differently in 1.8.2 and 2.0.0. I made some attempts to fix it a few months ago and last time I checked, at least the install went through (in 2.0.0, but not in 1.8.2). > > bye, Dirk > > > -- > http://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From shintaro.fujiwara at gmail.com Mon Jan 7 12:04:41 2013 From: shintaro.fujiwara at gmail.com (Shintaro Fujiwara) Date: Tue, 8 Jan 2013 02:04:41 +0900 Subject: [geeklog-devel] Rewriting Geeklog in a pohp5 way Message-ID: Hi, I'm proposing rewriting Geeklog in a php5 way totaly. In doing so, we can attract much attention to geeks, and more efficiently throwing modules and checking them. What do you say ? From websitemaster at cogeco.net Wed Jan 9 09:35:43 2013 From: websitemaster at cogeco.net (Tom) Date: Wed, 9 Jan 2013 09:35:43 -0500 Subject: [geeklog-devel] Geeklog UTF-8 Install bug Message-ID: <02d901cdee76$9ae912d0$d0bb3870$@cogeco.net> A couple of people are having problems with the install not creating utf-8 tables when the option is selected. http://project.geeklog.net/tracking/view.php?id=1540 I cannot reproduce the error. Can anyone else? Tom From websitemaster at cogeco.net Wed Jan 9 09:41:04 2013 From: websitemaster at cogeco.net (Tom) Date: Wed, 9 Jan 2013 09:41:04 -0500 Subject: [geeklog-devel] Geeklog.net UTF-8 Message-ID: <02da01cdee77$5a7be3c0$0f73ab40$@cogeco.net> I never notice before that the Geeklog.net database and tables are using the latin1_swedish_ci collation. Is there any reason why we never made the switch? If not I will add the change to the Geeklog.net redesign wiki page. Tom From websitemaster at cogeco.net Wed Jan 9 10:35:37 2013 From: websitemaster at cogeco.net (Tom) Date: Wed, 9 Jan 2013 10:35:37 -0500 Subject: [geeklog-devel] Geeklog Comment Notifications Message-ID: <02f001cdee7e$f915ae10$eb410a30$@cogeco.net> I would like some feedback on this bug report on Comment Notifications http://project.geeklog.net/tracking/view.php?id=1528 At first I thought it was a bug where no notifications was being sent out but after looking at the code I realize it was a misunderstanding on how comment notification works. I still see this is a bug though since things are not clear. A comment notification only gets sent out if a user replies directly to your comment and if you are not replying to your own comment. I thought when I clicked "Notify me of new replies" anyone replying to my comment or any replies of comments on my comments (or their comments, etc..) would generate a notification. I have missed out on a number of Geeklog comment questions because most people tend to reply to the last comment in the comment branch rather than on my first comment where I had notify enabled. This problem has also become more prevalent now in 2.0.0 since people do not have to click on a link to reply to a comment directly since the comment form is displayed right on the page (if configured this way) I see 4 options for when someone can receive comment notifications. Currently Geeklog uses option 1 1) someone replies directly to your specific comment, 2) someone replies directly to your comment or any comment reply in your particular comment branch 3) someone replies to any comment attached to the article, 4) someone replies to a comment or posts a new comment for the article I think we should at least use option 2 or even option 3. Thoughts... Tom From shintaro.fujiwara at gmail.com Wed Jan 9 10:30:37 2013 From: shintaro.fujiwara at gmail.com (Shintaro Fujiwara) Date: Thu, 10 Jan 2013 00:30:37 +0900 Subject: [geeklog-devel] Applying SELinux module to Geeklog Message-ID: Hi, during the Fedora install test, I disabled SELinx disabled. But I can write a SELinux module and shell script to install on Fedora. That will enhance Geeklog's status. Any comments? From danstoner at gmail.com Wed Jan 9 10:54:18 2013 From: danstoner at gmail.com (Dan Stoner) Date: Wed, 9 Jan 2013 10:54:18 -0500 Subject: [geeklog-devel] Applying SELinux module to Geeklog In-Reply-To: References: Message-ID: Does geeklog not function correctly in stock configuration of SELinux on "current" Fedora? - Dan Stoner On Wed, Jan 9, 2013 at 10:30 AM, Shintaro Fujiwara wrote: > Hi, during the Fedora install test, I disabled SELinx disabled. > > But I can write a SELinux module and shell script to install on Fedora. > > That will enhance Geeklog's status. > > Any comments? > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From vfuria at gmail.com Wed Jan 9 11:35:08 2013 From: vfuria at gmail.com (Vincent Furia) Date: Wed, 9 Jan 2013 09:35:08 -0700 Subject: [geeklog-devel] Geeklog Comment Notifications In-Reply-To: <02f001cdee7e$f915ae10$eb410a30$@cogeco.net> References: <02f001cdee7e$f915ae10$eb410a30$@cogeco.net> Message-ID: Number 2 should be fairly easy (and efficient) to implement given the comment algorithm (http://wiki.geeklog.net/index.php/CommentAlgorithm) I developed years ago. I think the "Notify me of new replies" check box should do your suggestion #2. I think having an option on the article to be notified of all replies (i.e. your suggestion #4) would make sense. This could be a button on the comment bar that says "notify me of all future comments" (or something). I think suggestions 1 and 3 can be ignored without loss if the above is implemented. Vinny On Wed, Jan 9, 2013 at 8:35 AM, Tom wrote: > I would like some feedback on this bug report on Comment Notifications > > http://project.geeklog.net/tracking/view.php?id=1528 > > At first I thought it was a bug where no notifications was being sent out > but after looking at the code I realize it was a misunderstanding on how > comment notification works. I still see this is a bug though since things > are not clear. > > A comment notification only gets sent out if a user replies directly to > your > comment and if you are not replying to your own comment. > > I thought when I clicked "Notify me of new replies" anyone replying to my > comment or any replies of comments on my comments (or their comments, > etc..) > would generate a notification. I have missed out on a number of Geeklog > comment questions because most people tend to reply to the last comment in > the comment branch rather than on my first comment where I had notify > enabled. This problem has also become more prevalent now in 2.0.0 since > people do not have to click on a link to reply to a comment directly since > the comment form is displayed right on the page (if configured this way) > > I see 4 options for when someone can receive comment notifications. > Currently Geeklog uses option 1 > > 1) someone replies directly to your specific comment, > 2) someone replies directly to your comment or any comment reply in your > particular comment branch > 3) someone replies to any comment attached to the article, > 4) someone replies to a comment or posts a new comment for the article > > I think we should at least use option 2 or even option 3. > > Thoughts... > > Tom > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shintaro.fujiwara at gmail.com Wed Jan 9 14:18:48 2013 From: shintaro.fujiwara at gmail.com (Shintaro Fujiwara) Date: Thu, 10 Jan 2013 04:18:48 +0900 Subject: [geeklog-devel] Applying SELinux module to Geeklog In-Reply-To: References: Message-ID: Firstly, if you use SELinux enforced, no. Secondly, if you use PostgreSQL, no. But, the problem itself is not a Geeklog's fault but settings of httpd in SELinux. This problem can be solved with making SELinux module and installing it. So that you can enforce SELinux and if there were vulnerable flaws in httpd the system will be safe. Second problem is solved by a patch I throw to buglist. It just convert ' to ' . Well, I am proposing fist one now. 2013/1/10 Dan Stoner : > Does geeklog not function correctly in stock configuration of SELinux > on "current" Fedora? > > - Dan Stoner > > > On Wed, Jan 9, 2013 at 10:30 AM, Shintaro Fujiwara > wrote: >> Hi, during the Fedora install test, I disabled SELinx disabled. >> >> But I can write a SELinux module and shell script to install on Fedora. >> >> That will enhance Geeklog's status. >> >> Any comments? >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel -- http://intrajp.no-ip.com/ Home Page From cordiste at free.fr Thu Jan 10 04:49:49 2013 From: cordiste at free.fr (cordiste) Date: Thu, 10 Jan 2013 10:49:49 +0100 Subject: [geeklog-devel] Geeklog Comment Notifications In-Reply-To: References: <02f001cdee7e$f915ae10$eb410a30$@cogeco.net> Message-ID: An author or an owner should be able by default to receive any comment to article or item he created. Also users should be able to subcribe to new comments (all comments, by topic, by item) like on the the forum plugin. But this is another feature request. We also need a comments list for admins http://project.geeklog.net/tracking/view.php?id=1443 Ben 2013/1/9 Vincent Furia : > Number 2 should be fairly easy (and efficient) to implement given the > comment algorithm (http://wiki.geeklog.net/index.php/CommentAlgorithm) I > developed years ago. > > I think the "Notify me of new replies" check box should do your suggestion > #2. > > I think having an option on the article to be notified of all replies (i.e. > your suggestion #4) would make sense. This could be a button on the comment > bar that says "notify me of all future comments" (or something). > > I think suggestions 1 and 3 can be ignored without loss if the above is > implemented. > > Vinny > > > On Wed, Jan 9, 2013 at 8:35 AM, Tom wrote: >> >> I would like some feedback on this bug report on Comment Notifications >> >> http://project.geeklog.net/tracking/view.php?id=1528 >> >> At first I thought it was a bug where no notifications was being sent out >> but after looking at the code I realize it was a misunderstanding on how >> comment notification works. I still see this is a bug though since things >> are not clear. >> >> A comment notification only gets sent out if a user replies directly to >> your >> comment and if you are not replying to your own comment. >> >> I thought when I clicked "Notify me of new replies" anyone replying to my >> comment or any replies of comments on my comments (or their comments, >> etc..) >> would generate a notification. I have missed out on a number of Geeklog >> comment questions because most people tend to reply to the last comment in >> the comment branch rather than on my first comment where I had notify >> enabled. This problem has also become more prevalent now in 2.0.0 since >> people do not have to click on a link to reply to a comment directly since >> the comment form is displayed right on the page (if configured this way) >> >> I see 4 options for when someone can receive comment notifications. >> Currently Geeklog uses option 1 >> >> 1) someone replies directly to your specific comment, >> 2) someone replies directly to your comment or any comment reply in your >> particular comment branch >> 3) someone replies to any comment attached to the article, >> 4) someone replies to a comment or posts a new comment for the article >> >> I think we should at least use option 2 or even option 3. >> >> Thoughts... >> >> Tom >> >> >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From websitemaster at cogeco.net Thu Jan 10 09:21:26 2013 From: websitemaster at cogeco.net (Tom) Date: Thu, 10 Jan 2013 09:21:26 -0500 Subject: [geeklog-devel] Geeklog Comment Notifications In-Reply-To: References: <02f001cdee7e$f915ae10$eb410a30$@cogeco.net> Message-ID: <006001cdef3d$c72051c0$5560f540$@cogeco.net> I agree all that would be nice. While I could hack some of the extra features to use the comment notifications table I think this is the wrong approach. We should really try to at least start to implement the ideas in the SOC Core notification project which includes all of these nice features. I will turn the bug into a feature request for 2.0.1 to include item 2. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: January-10-13 4:50 AM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog Comment Notifications An author or an owner should be able by default to receive any comment to article or item he created. Also users should be able to subcribe to new comments (all comments, by topic, by item) like on the the forum plugin. But this is another feature request. We also need a comments list for admins http://project.geeklog.net/tracking/view.php?id=1443 Ben 2013/1/9 Vincent Furia : > Number 2 should be fairly easy (and efficient) to implement given the > comment algorithm (http://wiki.geeklog.net/index.php/CommentAlgorithm) > I developed years ago. > > I think the "Notify me of new replies" check box should do your > suggestion #2. > > I think having an option on the article to be notified of all replies (i.e. > your suggestion #4) would make sense. This could be a button on the > comment bar that says "notify me of all future comments" (or something). > > I think suggestions 1 and 3 can be ignored without loss if the above > is implemented. > > Vinny > > > On Wed, Jan 9, 2013 at 8:35 AM, Tom wrote: >> >> I would like some feedback on this bug report on Comment >> Notifications >> >> http://project.geeklog.net/tracking/view.php?id=1528 >> >> At first I thought it was a bug where no notifications was being sent >> out but after looking at the code I realize it was a misunderstanding >> on how comment notification works. I still see this is a bug though >> since things are not clear. >> >> A comment notification only gets sent out if a user replies directly >> to your comment and if you are not replying to your own comment. >> >> I thought when I clicked "Notify me of new replies" anyone replying >> to my comment or any replies of comments on my comments (or their >> comments, >> etc..) >> would generate a notification. I have missed out on a number of >> Geeklog comment questions because most people tend to reply to the >> last comment in the comment branch rather than on my first comment >> where I had notify enabled. This problem has also become more >> prevalent now in 2.0.0 since people do not have to click on a link to >> reply to a comment directly since the comment form is displayed right >> on the page (if configured this way) >> >> I see 4 options for when someone can receive comment notifications. >> Currently Geeklog uses option 1 >> >> 1) someone replies directly to your specific comment, >> 2) someone replies directly to your comment or any comment reply in >> your particular comment branch >> 3) someone replies to any comment attached to the article, >> 4) someone replies to a comment or posts a new comment for the >> article >> >> I think we should at least use option 2 or even option 3. >> >> Thoughts... >> >> Tom >> >> >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Fri Jan 18 10:50:25 2013 From: websitemaster at cogeco.net (Tom) Date: Fri, 18 Jan 2013 10:50:25 -0500 Subject: [geeklog-devel] Geeklog 2.0.0 Articles and Multiple Topics Message-ID: <03f801cdf593$87d91180$978b3480$@cogeco.net> Okay my latest push to the repository has fixed the issue called "For articles with 2 or more topics the incorrect topic icon may display in the parent topic". I thought this was important enough to review on the mailing list so everyone understands. http://project.geeklog.net/tracking/view.php?id=1509 There are 2 issues here. We need to make sure the right topic icon is displaying for the article in the topic and when you click on the article title to read the full article you are sent to the right topic. This can get a little crazy since articles can belong to more than one topic and in any level of the topic tree. For example if you are viewing topic B that has a number of topics below it (on 1 or more levels) and an article is inherited up to topic B from 2 or more topics then the topic icon that is displayed for that article will be first the current topic (if that topic assignment exists). If it doesn't then it is the default topic if it exists in that topic tree branch. If not then the next topic used will be the based on the topic id in ascending order. Articles displayed on the front page do not need to worry about which topic is inherited so the default topic for that article will be used. Tom From websitemaster at cogeco.net Sun Jan 20 20:20:03 2013 From: websitemaster at cogeco.net (Tom) Date: Sun, 20 Jan 2013 20:20:03 -0500 Subject: [geeklog-devel] Geeklog 2.0.0 RC2 Release Schedule Message-ID: <000b01cdf775$705e8790$511b96b0$@cogeco.net> So I think there has been enough bug fixes to warrant we release Geeklog 2.0.0 Release Candidate 2. I have targeted a few bug fixes that I want to see in this release that I plan to work on. If you have any bugs that you want to work on let us know and I will update the target version. I want to get this bug list finished up soon so we could hopefully get a release out sometime late February. Does this sound good to everyone? Thanks Tom From shintaro.fujiwara at gmail.com Mon Jan 21 05:35:58 2013 From: shintaro.fujiwara at gmail.com (Shintaro Fujiwara) Date: Mon, 21 Jan 2013 19:35:58 +0900 Subject: [geeklog-devel] Geeklog 2.0.0 RC2 Release Schedule In-Reply-To: <000b01cdf775$705e8790$511b96b0$@cogeco.net> References: <000b01cdf775$705e8790$511b96b0$@cogeco.net> Message-ID: Hello, I threw a patch which enables Geeklog to work on PostgreSQL with no problem. As long as I tested with Fedora, I could not install Geeklog in PostgreSQL without my patch. It's nothing but converting \ to & and it will be converted ' . http://project.geeklog.net/tracking/view.php?id=1547 I think it's good for everyone and please evaluate it. Thank you. 2013/1/21 Tom : > So I think there has been enough bug fixes to warrant we release Geeklog > 2.0.0 Release Candidate 2. > > I have targeted a few bug fixes that I want to see in this release that I > plan to work on. If you have any bugs that you want to work on let us know > and I will update the target version. > > I want to get this bug list finished up soon so we could hopefully get a > release out sometime late February. > > Does this sound good to everyone? > > Thanks > > Tom > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel -- http://intrajp.no-ip.com/ Home Page From geeklog at mystral-kk.net Mon Jan 21 09:02:54 2013 From: geeklog at mystral-kk.net (geeklog at mystral-kk.net) Date: Mon, 21 Jan 2013 23:02:54 +0900 (JST) Subject: [geeklog-devel] Geeklog 2.0.0 RC2 Release Schedule In-Reply-To: <000b01cdf775$705e8790$511b96b0$@cogeco.net> References: <000b01cdf775$705e8790$511b96b0$@cogeco.net> Message-ID: <45605.203.189.105.202.1358776974.squirrel@www.s215.xrea.com> Tom wrote: > So I think there has been enough bug fixes to warrant we release Geeklog > 2.0.0 Release Candidate 2. > > I have targeted a few bug fixes that I want to see in this release that I > plan to work on. If you have any bugs that you want to work on let us > know > and I will update the target version. > > I want to get this bug list finished up soon so we could hopefully get a > release out sometime late February. > > Does this sound good to everyone? Sounds good to me. -- Kenji ITO http://mystral-kk.net/ From websitemaster at cogeco.net Mon Jan 21 09:13:46 2013 From: websitemaster at cogeco.net (Tom) Date: Mon, 21 Jan 2013 09:13:46 -0500 Subject: [geeklog-devel] Geeklog 2.0.0 RC2 Release Schedule In-Reply-To: References: <000b01cdf775$705e8790$511b96b0$@cogeco.net> Message-ID: <003601cdf7e1$86cbae10$94630a30$@cogeco.net> Thanks for your hard work Shintaro. I see Dirk has assigned himself that patch to take a look at it. I am not a PosqgreSQL user so if anyone else who is and has a chance to take a look at the bug and feedback, maybe they can offer their opinion on the matter (which seems to deal with handling of the single quote in sql statements for those interested). Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Shintaro Fujiwara Sent: January-21-13 5:36 AM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 2.0.0 RC2 Release Schedule Hello, I threw a patch which enables Geeklog to work on PostgreSQL with no problem. As long as I tested with Fedora, I could not install Geeklog in PostgreSQL without my patch. It's nothing but converting \ to & and it will be converted ' . http://project.geeklog.net/tracking/view.php?id=1547 I think it's good for everyone and please evaluate it. Thank you. 2013/1/21 Tom : > So I think there has been enough bug fixes to warrant we release > Geeklog > 2.0.0 Release Candidate 2. > > I have targeted a few bug fixes that I want to see in this release > that I plan to work on. If you have any bugs that you want to work on > let us know and I will update the target version. > > I want to get this bug list finished up soon so we could hopefully get > a release out sometime late February. > > Does this sound good to everyone? > > Thanks > > Tom > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel -- http://intrajp.no-ip.com/ Home Page _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Mon Jan 21 15:13:01 2013 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 21 Jan 2013 21:13:01 +0100 Subject: [geeklog-devel] Geeklog 2.0.0 RC2 Release Schedule In-Reply-To: <003601cdf7e1$86cbae10$94630a30$@cogeco.net> References: <000b01cdf775$705e8790$511b96b0$@cogeco.net> <003601cdf7e1$86cbae10$94630a30$@cogeco.net> Message-ID: <626164F2-1048-49B4-A70B-C196B30C2E3D@haun-online.de> Tom wrote: > I see Dirk has assigned himself that patch to take a look at it. I am not a > PosqgreSQL user so if anyone else who is and has a chance to take a look at > the bug and feedback, maybe they can offer their opinion on the matter > (which seems to deal with handling of the single quote in sql statements for > those interested). I'm not a Postgres expert (at all). Both Shintaro and myself seem to run the same version of Postgres. I can install rc1 just fine, he can't. So to me this looks like a setup issue. Shintaro, can you send me your postgresql.conf file so that I can compare it with mine? For now, I guess that once we figured out what the setting is, we'll have to document that Geeklog only works with that option being set to whatever. The proper solution then, as mentioned in the comments in the bug, would be to use two single quotes instead of backslash + quote to escape quotes for Postgres. But that would require changing all of Geeklog to call the new DB_escapeString() function. And that's not something that can be done with a simple search&replace operation, since we're using addslashes() in, erm, creative ways in some places. Btw, the patch doesn't help us here. In fact, it's not correct, since it would replace single quotes with an HTML ' entity - in text strings that are not HTML but plain text. bye, Dirk -- http://www.themobilepresenter.com/ From geeklog at mystral-kk.net Sat Jan 26 06:53:07 2013 From: geeklog at mystral-kk.net (Kenji ITO) Date: Sat, 26 Jan 2013 20:53:07 +0900 (JST) Subject: [geeklog-devel] Test failed Message-ID: <56761.203.189.105.202.1359201187.squirrel@www.s215.xrea.com> After I committed to fix a PostgreSQL error, the unit test #597 failed. It seems that DB_escapeString() function is missing in the test code. Would anyone please update system/lib-database.php, system/databases/*.php? -- Kenji ITO http://mystral-kk.net From websitemaster at cogeco.net Sat Jan 26 17:17:44 2013 From: websitemaster at cogeco.net (Tom) Date: Sat, 26 Jan 2013 17:17:44 -0500 Subject: [geeklog-devel] Test failed In-Reply-To: <56761.203.189.105.202.1359201187.squirrel@www.s215.xrea.com> References: <56761.203.189.105.202.1359201187.squirrel@www.s215.xrea.com> Message-ID: <002401cdfc12$f6e16570$e4a43050$@cogeco.net> There are a few problems with the story tests http://project.geeklog.net:8080/job/test-framework/lastFailedBuild/console I removed test testGetSidForDb and testGetSidForDbWithSlashes from tests since the story class function getSid now requires lib-database because of DB_escapeString. For the tests to run correctly they cannot require outside files. The problem is I can't seem to push my commit to http://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ Dirk I use the same username and password as the main Geeklog repository right? Here is my error log: % hg --repository T:\GeeklogTestFrameWork push ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ pushing to ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ remote: abort: There is no Mercurial repository here (.hg not found)! no suitable response from remote hg [command returned code 255 Sat Jan 26 17:12:17 2013] Any ideas why it is not working Dirk? Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Kenji ITO Sent: January-26-13 6:53 AM To: geeklog-devel at lists.geeklog.net Subject: [geeklog-devel] Test failed After I committed to fix a PostgreSQL error, the unit test #597 failed. It seems that DB_escapeString() function is missing in the test code. Would anyone please update system/lib-database.php, system/databases/*.php? -- Kenji ITO http://mystral-kk.net _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Sat Jan 26 17:26:34 2013 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 26 Jan 2013 23:26:34 +0100 Subject: [geeklog-devel] Test failed In-Reply-To: <002401cdfc12$f6e16570$e4a43050$@cogeco.net> References: <56761.203.189.105.202.1359201187.squirrel@www.s215.xrea.com> <002401cdfc12$f6e16570$e4a43050$@cogeco.net> Message-ID: Tom wrote: > % hg --repository T:\GeeklogTestFrameWork push > ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ > pushing to ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ > remote: abort: There is no Mercurial repository here (.hg not found)! > no suitable response from remote hg > [command returned code 255 Sat Jan 26 17:12:17 2013] > > Any ideas why it is not working Dirk? You're pushing to the web interface - that's not supported. Looks like you check the repository out via the web interface instead of using ssh. Check the .hg/hgrc file in your repository. It should have an entry like default = ssh://username at cvs.geeklog.net//cvsroot/hg/test-framework (replacing "username" with your username, of course) You can simply edit that url. The push should work then. bye, Dirk -- http://www.themobilepresenter.com/ From geeklog at mystral-kk.net Sun Jan 27 03:36:51 2013 From: geeklog at mystral-kk.net (Kenji ITO) Date: Sun, 27 Jan 2013 17:36:51 +0900 (JST) Subject: [geeklog-devel] Test failed In-Reply-To: <002401cdfc12$f6e16570$e4a43050$@cogeco.net> References: <56761.203.189.105.202.1359201187.squirrel@www.s215.xrea.com> <002401cdfc12$f6e16570$e4a43050$@cogeco.net> Message-ID: <34811.203.189.105.202.1359275811.squirrel@www.s215.xrea.com> Tom wrote: > There are a few problems with the story tests > http://project.geeklog.net:8080/job/test-framework/lastFailedBuild/console > > I removed test testGetSidForDb and testGetSidForDbWithSlashes from tests > since the story class function getSid now requires lib-database because of > DB_escapeString. For the tests to run correctly they cannot require > outside > files. > > The problem is I can't seem to push my commit to > http://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ > > Dirk I use the same username and password as the main Geeklog repository > right? > > Here is my error log: > > % hg --repository T:\GeeklogTestFrameWork push > ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ > pushing to ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ > remote: abort: There is no Mercurial repository here (.hg not found)! > no suitable response from remote hg > [command returned code 255 Sat Jan 26 17:12:17 2013] > > Any ideas why it is not working Dirk? > > Tom Thanks Tom. I fixed two other bugs in "lib-mbyteNoMBTest.php" and "lib-mbyteWithMBTest.php". -- Kenji ITO http://mystral-kk.net From dirk at haun-online.de Sun Jan 27 04:25:50 2013 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 27 Jan 2013 10:25:50 +0100 Subject: [geeklog-devel] FOSDEM Message-ID: Is anyone going to FOSDEM in Brussels next weekend? https://fosdem.org/2013/ I've met Vlad and Rouslan there in previous years. Who's going to continue the tradition this year? I'll be giving a lightning talk in the Testing and Automation devroom on Saturday, https://fosdem.org/2013/schedule/event/status_of_visualizing_status/ Other than that, I have not made any plans yet. I'll probably drop in to the PHP and legal issues devrooms, but will decide what to attend on a whim. Find me on Twitter if you want to hook up. bye, Dirk -- http://www.themobilepresenter.com/ From websitemaster at cogeco.net Sun Jan 27 09:33:57 2013 From: websitemaster at cogeco.net (Tom) Date: Sun, 27 Jan 2013 09:33:57 -0500 Subject: [geeklog-devel] Test failed In-Reply-To: References: <56761.203.189.105.202.1359201187.squirrel@www.s215.xrea.com> <002401cdfc12$f6e16570$e4a43050$@cogeco.net> Message-ID: <003d01cdfc9b$56de92d0$049bb870$@cogeco.net> Thanks Dirk I was trying ssh at one point but I was missing a slash :-) I got it to work. Thanks 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: January-26-13 5:27 PM To: Geeklog Development Subject: Re: [geeklog-devel] Test failed Tom wrote: > % hg --repository T:\GeeklogTestFrameWork push > ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ > pushing to > ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ > remote: abort: There is no Mercurial repository here (.hg not found)! > no suitable response from remote hg > [command returned code 255 Sat Jan 26 17:12:17 2013] > > Any ideas why it is not working Dirk? You're pushing to the web interface - that's not supported. Looks like you check the repository out via the web interface instead of using ssh. Check the .hg/hgrc file in your repository. It should have an entry like default = ssh://username at cvs.geeklog.net//cvsroot/hg/test-framework (replacing "username" with your username, of course) You can simply edit that url. The push should work then. bye, Dirk -- http://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Sun Jan 27 09:34:31 2013 From: websitemaster at cogeco.net (Tom) Date: Sun, 27 Jan 2013 09:34:31 -0500 Subject: [geeklog-devel] FOSDEM In-Reply-To: References: Message-ID: <003e01cdfc9b$6b3bbd20$41b33760$@cogeco.net> Have fun. Let us know if you find anything interesting. 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: January-27-13 4:26 AM To: geeklog-devel at lists.geeklog.net Subject: [geeklog-devel] FOSDEM Is anyone going to FOSDEM in Brussels next weekend? https://fosdem.org/2013/ I've met Vlad and Rouslan there in previous years. Who's going to continue the tradition this year? I'll be giving a lightning talk in the Testing and Automation devroom on Saturday, https://fosdem.org/2013/schedule/event/status_of_visualizing_status/ Other than that, I have not made any plans yet. I'll probably drop in to the PHP and legal issues devrooms, but will decide what to attend on a whim. Find me on Twitter if you want to hook up. bye, Dirk -- http://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Sun Jan 27 20:05:14 2013 From: websitemaster at cogeco.net (Tom) Date: Sun, 27 Jan 2013 20:05:14 -0500 Subject: [geeklog-devel] Test failed In-Reply-To: References: <56761.203.189.105.202.1359201187.squirrel@www.s215.xrea.com> <002401cdfc12$f6e16570$e4a43050$@cogeco.net> Message-ID: <006401cdfcf3$87c0bba0$974232e0$@cogeco.net> Dirk, How do I get Jenkins to rerun the tests after I make a change? (besides pushing something to the Geeklog repository) 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: January-26-13 5:27 PM To: Geeklog Development Subject: Re: [geeklog-devel] Test failed Tom wrote: > % hg --repository T:\GeeklogTestFrameWork push > ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ > pushing to > ssh://project.geeklog.net/cgi-bin/hgwebdir.cgi/test-framework/ > remote: abort: There is no Mercurial repository here (.hg not found)! > no suitable response from remote hg > [command returned code 255 Sat Jan 26 17:12:17 2013] > > Any ideas why it is not working Dirk? You're pushing to the web interface - that's not supported. Looks like you check the repository out via the web interface instead of using ssh. Check the .hg/hgrc file in your repository. It should have an entry like default = ssh://username at cvs.geeklog.net//cvsroot/hg/test-framework (replacing "username" with your username, of course) You can simply edit that url. The push should work then. bye, Dirk -- http://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Mon Jan 28 16:21:07 2013 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 28 Jan 2013 22:21:07 +0100 Subject: [geeklog-devel] Test failed In-Reply-To: <006401cdfcf3$87c0bba0$974232e0$@cogeco.net> References: <56761.203.189.105.202.1359201187.squirrel@www.s215.xrea.com> <002401cdfc12$f6e16570$e4a43050$@cogeco.net> <006401cdfcf3$87c0bba0$974232e0$@cogeco.net> Message-ID: <6DCCE27D-52AC-4DBA-8632-10B6474FB8A8@haun-online.de> Tom wrote: > How do I get Jenkins to rerun the tests after I make a change? (besides > pushing something to the Geeklog repository) It's not set up to poll on a regular basis - it'll only poll when being triggered by an update of the geeklog repository. I simply didn't expect a lot of activity on the test-framework repository. I'd happily change that if we had some volunteers for writing more tests ;-) Did you create an account in Jenkins yet? Tell me the username and I can give you the rights to start builds manually. bye, Dirk -- http://www.themobilepresenter.com/ From websitemaster at cogeco.net Wed Jan 30 10:55:20 2013 From: websitemaster at cogeco.net (Tom) Date: Wed, 30 Jan 2013 10:55:20 -0500 Subject: [geeklog-devel] Geeklog and jQuery 1.9.0 - Important! Message-ID: <00ea01cdff02$34fd10b0$9ef73210$@cogeco.net> So jQuery and jQuery UI have gone through a number of updates since we last updated it around September 2012. http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-f inal-released/ The current release jQuery 1.9.0 has a few major changes from the version we use (1.7.2). For one thing there are several deprecated features such as $.browser and .menu which affects the Geeklog configuration (tab and search auto complete controls). See the upgrade guide for more information: http://jquery.com/upgrade-guide/1.9/ Before we release Geeklog 2.0.0rc2 we should update Geeklog's jQuery. There is a jQuery Migrate Plugin that I can include which may fix our issues (Haven't tested it yet) but I think the best route to go would be to just update the Configuration to support jQuery 1.9.0 jQuery UI has also been updated to 1.10.0 (we currently use 1.8.20). There are a number of new widgets included: Menu - Creates nestable menus. Spinner - Displays buttons to easily input numbers via the keyboard or mouse. Tooltip - Shows additional information for any element on hover or focus. (IN Geeklog 2.0.1 we should maybe look into using this instead of our own tooltips) The other thing that has changed is the effect files has been renamed from jquery.effects.xxx To jquery.ui.effect-xxx I have update the effect names to the current naming structure but this means it changes the name we use to include the effect js. I don't think this will be an issue for anybody as I don't think anyone calls them directly. So I have updated all the jQuery and jQuery UI files along with the theme files and scripts class to update everything to the latest version. Right now in the configuration the tab control works but throws js errors (the tabs will become 2 lines if to many tabs instead of using a menu item at the end). The autocomplete search box for the configuration doesn't work at all (partially works if you use the CDN-hosted copy). I am going to be busy over the next 2 weeks. Just to get things tested and hopefully ready by the end of February what I was hoping to is push to the repository what I have updated and have someone else fix the configuration search and tabs. Is anyone willing to do this? Let me know and I will commit and push the changes. Thanks Tom From websitemaster at cogeco.net Thu Jan 31 17:57:51 2013 From: websitemaster at cogeco.net (Tom) Date: Thu, 31 Jan 2013 17:57:51 -0500 Subject: [geeklog-devel] Geeklog and jQuery 1.9.0 - Important! In-Reply-To: <00ea01cdff02$34fd10b0$9ef73210$@cogeco.net> References: <00ea01cdff02$34fd10b0$9ef73210$@cogeco.net> Message-ID: <015401ce0006$65ae5250$310af6f0$@cogeco.net> Okay so I pushed the changes. There are 3 java script issues that need fixing and they all deal with the Geeklog Configuration. - Search Auto Complete - Tabs - Configuration Tooltips Hopefully someone can tackle this. Most of the fixes will probably take place in the admin.configuration.js file. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom Sent: January-30-13 10:55 AM To: 'Geeklog Development' Subject: [geeklog-devel] Geeklog and jQuery 1.9.0 - Important! So jQuery and jQuery UI have gone through a number of updates since we last updated it around September 2012. http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-f inal-released/ The current release jQuery 1.9.0 has a few major changes from the version we use (1.7.2). For one thing there are several deprecated features such as $.browser and .menu which affects the Geeklog configuration (tab and search auto complete controls). See the upgrade guide for more information: http://jquery.com/upgrade-guide/1.9/ Before we release Geeklog 2.0.0rc2 we should update Geeklog's jQuery. There is a jQuery Migrate Plugin that I can include which may fix our issues (Haven't tested it yet) but I think the best route to go would be to just update the Configuration to support jQuery 1.9.0 jQuery UI has also been updated to 1.10.0 (we currently use 1.8.20). There are a number of new widgets included: Menu - Creates nestable menus. Spinner - Displays buttons to easily input numbers via the keyboard or mouse. Tooltip - Shows additional information for any element on hover or focus. (IN Geeklog 2.0.1 we should maybe look into using this instead of our own tooltips) The other thing that has changed is the effect files has been renamed from jquery.effects.xxx To jquery.ui.effect-xxx I have update the effect names to the current naming structure but this means it changes the name we use to include the effect js. I don't think this will be an issue for anybody as I don't think anyone calls them directly. So I have updated all the jQuery and jQuery UI files along with the theme files and scripts class to update everything to the latest version. Right now in the configuration the tab control works but throws js errors (the tabs will become 2 lines if to many tabs instead of using a menu item at the end). The autocomplete search box for the configuration doesn't work at all (partially works if you use the CDN-hosted copy). I am going to be busy over the next 2 weeks. Just to get things tested and hopefully ready by the end of February what I was hoping to is push to the repository what I have updated and have someone else fix the configuration search and tabs. Is anyone willing to do this? Let me know and I will commit and push the changes. Thanks Tom _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Thu Jan 31 18:00:12 2013 From: websitemaster at cogeco.net (Tom) Date: Thu, 31 Jan 2013 18:00:12 -0500 Subject: [geeklog-devel] Geeklog and jQuery 1.9.0 - Important! In-Reply-To: <015401ce0006$65ae5250$310af6f0$@cogeco.net> References: <00ea01cdff02$34fd10b0$9ef73210$@cogeco.net> <015401ce0006$65ae5250$310af6f0$@cogeco.net> Message-ID: <015501ce0006$b9c5e100$2d51a300$@cogeco.net> Okay so I pushed the changes. (For some reason the changeset info wasn't mailed to the cvs mailing list but it is there :-) There are 3 java script issues that need fixing and they all deal with the Geeklog Configuration. - Search Auto Complete - Tabs - Configuration Tooltips Hopefully someone can tackle this. Most of the fixes will probably take place in the admin.configuration.js file. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom Sent: January-30-13 10:55 AM To: 'Geeklog Development' Subject: [geeklog-devel] Geeklog and jQuery 1.9.0 - Important! So jQuery and jQuery UI have gone through a number of updates since we last updated it around September 2012. http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-f inal-released/ The current release jQuery 1.9.0 has a few major changes from the version we use (1.7.2). For one thing there are several deprecated features such as $.browser and .menu which affects the Geeklog configuration (tab and search auto complete controls). See the upgrade guide for more information: http://jquery.com/upgrade-guide/1.9/ Before we release Geeklog 2.0.0rc2 we should update Geeklog's jQuery. There is a jQuery Migrate Plugin that I can include which may fix our issues (Haven't tested it yet) but I think the best route to go would be to just update the Configuration to support jQuery 1.9.0 jQuery UI has also been updated to 1.10.0 (we currently use 1.8.20). There are a number of new widgets included: Menu - Creates nestable menus. Spinner - Displays buttons to easily input numbers via the keyboard or mouse. Tooltip - Shows additional information for any element on hover or focus. (IN Geeklog 2.0.1 we should maybe look into using this instead of our own tooltips) The other thing that has changed is the effect files has been renamed from jquery.effects.xxx To jquery.ui.effect-xxx I have update the effect names to the current naming structure but this means it changes the name we use to include the effect js. I don't think this will be an issue for anybody as I don't think anyone calls them directly. So I have updated all the jQuery and jQuery UI files along with the theme files and scripts class to update everything to the latest version. Right now in the configuration the tab control works but throws js errors (the tabs will become 2 lines if to many tabs instead of using a menu item at the end). The autocomplete search box for the configuration doesn't work at all (partially works if you use the CDN-hosted copy). I am going to be busy over the next 2 weeks. Just to get things tested and hopefully ready by the end of February what I was hoping to is push to the repository what I have updated and have someone else fix the configuration search and tabs. Is anyone willing to do this? Let me know and I will commit and push the changes. Thanks Tom _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel