. Now everything seems to work - but verification is never done. Trying to modify validateComment.py gave an error when trying to import CaptchasDotNet (authorization failure??). I do not understand why validation does not call validation of the captcha code "automatically". Am I missing something? Has anybody else tried to solve this problem? From nyusuke at nagosui.org Sun Jun 4 21:06:00 2006 From: nyusuke at nagosui.org (Yusuke NAKAI) Date: Mon, 05 Jun 2006 04:06:00 +0900 Subject: [COREblog-en] comment spam In-Reply-To: <1149442620.120956754.30609.sendItem@bloglines.com> References: <1149442620.120956754.30609.sendItem@bloglines.com> Message-ID: <44832F18.7070009@nagosui.org> Hi. I'm using PloneCaptcha on Plone+COREBlog2 and it works well. > . Now everything > seems to work - but verification is never done. Trying to modify validateComment.py > gave an error when trying to import CaptchasDotNet (authorization failure??). > > I do not understand why validation does not call validation of the captcha > code "automatically". Am I missing something? Has anybody else tried to solve > this problem? Did you set 'name' and 'secret key' at 'Zope-instance/Products/PloneCaptcha/config.py'? Here is a procedure to use PloneCaptcha on Plone+COREBlog2. 1. Get account of captchas.net -> http://captchas.net/registration/ After registration completed, you'll get 'name' and 'secret key' by e-mail. 2. Download and extract PloneCaptcha, and put it in 'Products' folder of Zope-instance. 3. Edit 'name' and 'secret key' settings in 'Zope-instance/Products/PloneCaptcha/config.py'. 4. Restart zope and install PloneCaptcha from portal_quickinstaller(site settings -> add/remove products). Now you can use captcha on plone. But to use it on COREBlog2, further settings are needed. 5. Edit 'portal_skins/COREBlog2/cbcomment_form' on ZMI. Simply add this code to just before 'remember cookie' code.

Or more completely, add these code. -------------------------------------------------------------

Verification Code

This helps us prevent automated spamming.

Validation error output

------------------------------------------------------------- 6. Edit validator on 'cbentry_view' and 'cbcomment_preview'. Go to 'portal_skins/COREBlog2/cbentry_view' on ZMI, and click 'Validation' tab. Add validator like this: Context type: Any Button : (empty) Validators : validate_captcha Repeat for 'portal_skins/COREBlog2/cbcomment_preview'. Now you can use captcha on Plone+COREBlog2. Regards, -- NO LEARNING, NO MEANING. Yusuke NAKAI mail: nyusuke at nagosui.org web : http://nagosui.org From klockerh.27875151 at bloglines.com Mon Jun 5 08:30:58 2006 From: klockerh.27875151 at bloglines.com (klockerh.27875151 at bloglines.com) Date: 5 Jun 2006 06:30:58 -0000 Subject: [COREblog-en] comment spam Message-ID: <1149489058.2399601700.9862.sendItem@bloglines.com> --- Coreblog \(English\)" > 6. Edit validator on 'cbentry_view' and 'cbcomment_preview'. > Go to 'portal_skins/COREBlog2/cbentry_view' on ZMI, and click > 'Validation' tab. Add validator like this: > > Context type: Any > Button : (empty) > Validators : validate_captcha > > Repeat for 'portal_skins/COREBlog2/cbcomment_preview'. > Thanks a lot - your recipe worked very well - my error was in the last step: didn't know of a validation tab... Now everything works fine for comments (I get only trackback spam :( Hermann From mlarreategi at codesyntax.com Mon Jun 5 08:49:25 2006 From: mlarreategi at codesyntax.com (Mikel Larreategi) Date: Mon, 05 Jun 2006 08:49:25 +0200 Subject: [COREblog-en] Trackback spam In-Reply-To: <200606022014.07775.pupeno@pupeno.com> References: <200606011741.51139.pupeno@pupeno.com> <447FDBE5.3060809@codesyntax.com> <200606022014.07775.pupeno@pupeno.com> Message-ID: <4483D3F5.7060802@codesyntax.com> Pupeno(e)k dio: > On Friday, 2 de June de 2006 06:34, Mikel Larreategi wrote: >> Pupeno(e)k dio: >>> Am I the only one receiving more that 100 trackback spams a day ? >> No, we are also receiving a lot of spam in our COREBlog communities, but >> we have some scripts to do the "bad job" of deleting this spam. >> >> You can also close the tracbacks in your post to avoid spam. > > Can you share does scripts ? Are they for coreblog ? Those scripts were already discussed here, you'll find a reference here: http://www.eibar.org/blogak/luistxo/en/298 We just adapted those scripts with some common spamwords (viagra, casino, ...) to check them automatically instead of calling the script each time with a new keyword. Regards, Mikel -- Mikel Larreategi mlarreategi at codesyntax.com CodeSyntax Azitaingo Industrialdea 3 K E-20600 Eibar Tel: (+34) 943 82 17 80 From nekstrand at gmail.com Fri Jun 9 23:44:06 2006 From: nekstrand at gmail.com (Niklas) Date: Fri, 9 Jun 2006 23:44:06 +0200 Subject: [COREblog-en] Problem with Plone 2.1.3 ? Message-ID: Hi, I upgraded zope 2.8.5 to 2.8.7 and that worked great, but when i tried to upgrade Plone 2.1.2 to 2.1.3 everything seems to work except CoreBlog-2. Am I the one doing anything wrong or is there a problem? With best regards Niklas From shibata at webcore.co.jp Sat Jun 10 09:21:37 2006 From: shibata at webcore.co.jp (Atsushi Shibata) Date: Sat, 10 Jun 2006 16:21:37 +0900 Subject: [COREblog-en] Problem with Plone 2.1.3 ? In-Reply-To: References: Message-ID: <20060610162137.509537.512f4d5f@webcore.co.jp> Hi :-). On Fri, 9 Jun 2006 23:44:06 +0200, wrote: > I upgraded zope 2.8.5 to 2.8.7 and that worked great, but when i tried > to upgrade Plone 2.1.2 to 2.1.3 everything seems to work except > CoreBlog-2. > > Am I the one doing anything wrong or is there a problem? More details, please :-). ---------------------------------------- Atsushi Shibata (Webcore Corp.) shibata at webcore.co.jp http://www.webcore.co.jp/ ---------------------------------------- From pupeno at pupeno.com Sat Jun 10 19:47:52 2006 From: pupeno at pupeno.com (Pupeno) Date: Sat, 10 Jun 2006 19:47:52 +0200 Subject: [COREblog-en] [OT] About Atsushi Shibata (was Re: Problem with Plone 2.1.3 ?) In-Reply-To: <20060610162137.509537.512f4d5f@webcore.co.jp> References: <20060610162137.509537.512f4d5f@webcore.co.jp> Message-ID: <1149961672.11065.26.camel@ulab.pupeno.com> Atsushi Shibata dedication to help everybody is admirable. Most of us coders prefers to be codding than figuring out why the heck a particular installation is not working, yet Atsushi Shibata takes the time to help us all, the users. Atsushi Shibata, a big _____ _ _ |_ _| |__ __ _ _ __ | | __ _ _ ___ _ _ | | | '_ \ / _` | '_ \| |/ / | | | |/ _ \| | | | | | | | | | (_| | | | | < | |_| | (_) | |_| | |_| |_| |_|\__,_|_| |_|_|\_\ \__, |\___/ \__,_| |___/ to you! On Sat, 2006-06-10 at 16:21 +0900, Atsushi Shibata wrote: > Hi :-). > > On Fri, 9 Jun 2006 23:44:06 +0200, wrote: > > I upgraded zope 2.8.5 to 2.8.7 and that worked great, but when i tried > > to upgrade Plone 2.1.2 to 2.1.3 everything seems to work except > > CoreBlog-2. > > > > Am I the one doing anything wrong or is there a problem? > > More details, please :-). > > ---------------------------------------- > Atsushi Shibata (Webcore Corp.) > shibata at webcore.co.jp > http://www.webcore.co.jp/ > ---------------------------------------- > _______________________________________________ > COREblog-en mailing list > COREblog-en at postaria.com > http://postaria.com/mailman/listinfo/coreblog-en > Unsubscription writing to coreblog-en-leave at postaria.com -- Pupeno http://pupeno.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part Url : http://postaria.com/pipermail/coreblog-en/attachments/20060610/4ebe0234/attachment.pgp From nekstrand at gmail.com Sat Jun 10 21:00:24 2006 From: nekstrand at gmail.com (Niklas) Date: Sat, 10 Jun 2006 21:00:24 +0200 Subject: [COREblog-en] Problem with Plone 2.1.3 ? In-Reply-To: <20060610162137.509537.512f4d5f@webcore.co.jp> References: <20060610162137.509537.512f4d5f@webcore.co.jp> Message-ID: Hi, This is the error i get an as i understand it it's some kind of problem with the recent portlet, so i tried to disable that one and then i got the second error: With best regards Niklas Site Error An error was encountered while publishing this resource. AttributeError Sorry, a site error occurred. Traceback (innermost last): Module ZPublisher.Publish, line 188, in publish_module_standard Module Products.PlacelessTranslationService.PatchStringIO, line 34, in new_publish Module ZPublisher.Publish, line 145, in publish Module Zope2.App.startup, line 216, in zpublisher_exception_hook Module ZPublisher.Publish, line 114, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 40, in call_object Module Shared.DC.Scripts.Bindings, line 311, in __call__ Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec Module Products.CMFCore.FSPageTemplate, line 195, in _exec Module Products.CMFCore.FSPageTemplate, line 134, in pt_render Module Products.PageTemplates.PageTemplate, line 104, in pt_render Module TAL.TALInterpreter, line 206, in __call__ Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 711, in do_useMacro Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 426, in do_optTag_tal Module TAL.TALInterpreter, line 411, in do_optTag Module TAL.TALInterpreter, line 406, in no_tag Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 742, in do_defineSlot Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 677, in do_condition Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 742, in do_defineSlot Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 426, in do_optTag_tal Module TAL.TALInterpreter, line 411, in do_optTag Module TAL.TALInterpreter, line 406, in no_tag Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 711, in do_useMacro Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 677, in do_condition Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 426, in do_optTag_tal Module TAL.TALInterpreter, line 411, in do_optTag Module TAL.TALInterpreter, line 406, in no_tag Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 653, in do_loop_tal Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 426, in do_optTag_tal Module TAL.TALInterpreter, line 411, in do_optTag Module TAL.TALInterpreter, line 406, in no_tag Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 426, in do_optTag_tal Module TAL.TALInterpreter, line 411, in do_optTag Module TAL.TALInterpreter, line 406, in no_tag Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 677, in do_condition Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 426, in do_optTag_tal Module TAL.TALInterpreter, line 411, in do_optTag Module TAL.TALInterpreter, line 406, in no_tag Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 711, in do_useMacro Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 677, in do_condition Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 653, in do_loop_tal Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 426, in do_optTag_tal Module TAL.TALInterpreter, line 411, in do_optTag Module TAL.TALInterpreter, line 406, in no_tag Module TAL.TALInterpreter, line 250, in interpret Module TAL.TALInterpreter, line 308, in do_startTag Module TAL.TALInterpreter, line 374, in attrAction_tal Module Products.PageTemplates.TALES, line 227, in evaluateText Module Products.PageTemplates.TALES, line 221, in evaluate URL: file:COREBlog2/skins/COREBlog2/portlet_recent_comment.pt Line 27, Column 12 Expression: standard:'entry/absolute_url' Names: {'container': , 'context': , 'default': , 'here': , 'loop': , 'modules': , 'nothing': None, 'options': {'args': ()}, 'repeat': , 'request': , 'root': , 'template': , 'traverse_subpath': [], 'user': Anonymous User} Module Products.PageTemplates.Expressions, line 185, in __call__ Module Products.PageTemplates.Expressions, line 173, in _eval Module Products.PageTemplates.Expressions, line 127, in _eval __traceback_info__: entry Module Products.PageTemplates.Expressions, line 334, in restrictedTraverse __traceback_info__: {'path': ['absolute_url'], 'TraversalRequestNameStack': []} AttributeError: 'NoneType' object has no attribute 'absolute_url' (Also, the following error occurred while attempting to render the standard error message, please see the event log for full details: 'NoneType' object has no attribute 'absolute_url') -------------------------------------------------------------------------------- Troubleshooting Suggestions The URL may be incorrect. The parameters passed to this resource may be incorrect. A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to error log. If the error persists please contact the site maintainer. Thank you for your patience. Site Error An error was encountered while publishing this resource. *CompilerError* Sorry, a site error occurred. Traceback (innermost last): - Module ZPublisher.Publish, line 188, in publish_module_standard - Module Products.PlacelessTranslationService.PatchStringIO, line 34, in new_publish - Module ZPublisher.Publish, line 145, in publish - Module Zope2.App.startup, line 216, in zpublisher_exception_hook - Module ZPublisher.Publish, line 114, in publish - Module ZPublisher.mapply, line 88, in mapply - Module ZPublisher.Publish, line 40, in call_object - Module Shared.DC.Scripts.Bindings, line 311, in __call__ - Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec - Module Products.CMFCore.FSPageTemplate, line 195, in _exec - Module Products.CMFCore.FSPageTemplate, line 134, in pt_render - Module Products.PageTemplates.PageTemplate, line 104, in pt_render ** - Module TAL.TALInterpreter, line 206, in __call__ - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 711, in do_useMacro - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 426, in do_optTag_tal - Module TAL.TALInterpreter, line 411, in do_optTag - Module TAL.TALInterpreter, line 406, in no_tag - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 742, in do_defineSlot - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 677, in do_condition - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 742, in do_defineSlot - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 426, in do_optTag_tal - Module TAL.TALInterpreter, line 411, in do_optTag - Module TAL.TALInterpreter, line 406, in no_tag - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 711, in do_useMacro - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 677, in do_condition - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 426, in do_optTag_tal - Module TAL.TALInterpreter, line 411, in do_optTag - Module TAL.TALInterpreter, line 406, in no_tag - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 653, in do_loop_tal - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 426, in do_optTag_tal - Module TAL.TALInterpreter, line 411, in do_optTag - Module TAL.TALInterpreter, line 406, in no_tag - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 426, in do_optTag_tal - Module TAL.TALInterpreter, line 411, in do_optTag - Module TAL.TALInterpreter, line 406, in no_tag - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 677, in do_condition - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 426, in do_optTag_tal - Module TAL.TALInterpreter, line 411, in do_optTag - Module TAL.TALInterpreter, line 406, in no_tag - Module TAL.TALInterpreter, line 250, in interpret - Module TAL.TALInterpreter, line 697, in do_useMacro - Module Products.PageTemplates.TALES, line 221, in evaluate *URL: file:CMFPlone/skins/plone_templates/portlets_fetcher.pt* *Line 17, Column 12* *Expression: * *Names:* {'container': , 'context': , 'default': , 'here': , 'loop': , 'modules': , 'nothing': None, 'options': {'args': ()}, 'repeat': , 'request': , 'root': , 'template': , 'traverse_subpath': [], 'user': Anonymous User} - Module Products.PageTemplates.ZRPythonExpr, line 47, in __call__ __traceback_info__: path(pathexpr) - Module Python expression "path(pathexpr)", line 1, in - Module Products.PageTemplates.PythonExpr, line 85, in __call__ - Module Products.PageTemplates.Expressions, line 146, in __init__ - Module Products.PageTemplates.Expressions, line 96, in __init__ CompilerError: Invalid variable name "# here" (Also, the following error occurred while attempting to render the standard error message, please see the event log for full details: Invalid variable name "# here") ------------------------------ Troubleshooting Suggestions - The URL may be incorrect. - The parameters passed to this resource may be incorrect. - A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to error log. If the error persists please contact the site maintainer. Thank you for your patience. On 6/10/06, Atsushi Shibata wrote: > Hi :-). > > On Fri, 9 Jun 2006 23:44:06 +0200, wrote: > > I upgraded zope 2.8.5 to 2.8.7 and that worked great, but when i tried > > to upgrade Plone 2.1.2 to 2.1.3 everything seems to work except > > CoreBlog-2. > > > > Am I the one doing anything wrong or is there a problem? > > More details, please :-). > > ---------------------------------------- > Atsushi Shibata (Webcore Corp.) > shibata at webcore.co.jp > http://www.webcore.co.jp/ > ---------------------------------------- > _______________________________________________ > COREblog-en mailing list > COREblog-en at postaria.com > http://postaria.com/mailman/listinfo/coreblog-en > Unsubscription writing to coreblog-en-leave at postaria.com > -- With best regards / med v?nlig h?lsning Niklas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://postaria.com/pipermail/coreblog-en/attachments/20060610/c715bb4f/attachment.htm From brian at zopeworld.com Sat Jun 10 23:36:26 2006 From: brian at zopeworld.com (Brian Davis) Date: Sat, 10 Jun 2006 17:36:26 -0400 Subject: [COREblog-en] Simpleblog -> COREBlog migration script Message-ID: <448B3B5A.6040808@zopeworld.com> Anybody have one of these? I've got some old blogs to switch over and I'm not sure which is the easiest way to move the content. Any help is greatly appreciated. Thanks, Brian Davis From shibata at webcore.co.jp Mon Jun 12 02:12:18 2006 From: shibata at webcore.co.jp (Atsushi Shibata) Date: Mon, 12 Jun 2006 09:12:18 +0900 Subject: [COREblog-en] [OT] About Atsushi Shibata (was Re: Problem with Plone 2.1.3 ?) In-Reply-To: <1149961672.11065.26.camel@ulab.pupeno.com> References: <20060610162137.509537.512f4d5f@webcore.co.jp> <1149961672.11065.26.camel@ulab.pupeno.com> Message-ID: <20060612091218.228601.0cda6b52@webcore.co.jp> Hi :-). On Sat, 10 Jun 2006 19:47:52 +0200, wrote: > Atsushi Shibata, a big > _____ _ _ > |_ _| |__ __ _ _ __ | | __ _ _ ___ _ _ > | | | '_ \ / _` | '_ \| |/ / | | | |/ _ \| | | | > | | | | | | (_| | | | | < | |_| | (_) | |_| | > |_| |_| |_|\__,_|_| |_|_|\_\ \__, |\___/ \__,_| > |___/ > to you! Wow ! Fantastic ! Thanks to pupeno-san, and all of you, for using COREBlog2/COREBlog :-). ---------------------------------------- Atsushi Shibata (Webcore Corp.) shibata at webcore.co.jp http://www.webcore.co.jp/ ---------------------------------------- From shibata at webcore.co.jp Mon Jun 12 02:14:26 2006 From: shibata at webcore.co.jp (Atsushi Shibata) Date: Mon, 12 Jun 2006 09:14:26 +0900 Subject: [COREblog-en] Problem with Plone 2.1.3 ? In-Reply-To: References: <20060610162137.509537.512f4d5f@webcore.co.jp> Message-ID: <20060612091426.757423.aca35117@webcore.co.jp> Hi :-). On Sat, 10 Jun 2006 21:00:24 +0200, wrote: > Hi, > > This is the error i get an as i understand it it's some kind of > problem with the recent portlet, so i tried to disable that one and > then i got the second error: Did you obey right upgrade procedure ? Or, recatalog may help you, I think. Regards. ---------------------------------------- Atsushi Shibata (Webcore Corp.) shibata at webcore.co.jp http://www.webcore.co.jp/ ---------------------------------------- From shibata at webcore.co.jp Mon Jun 12 02:18:31 2006 From: shibata at webcore.co.jp (Atsushi Shibata) Date: Mon, 12 Jun 2006 09:18:31 +0900 Subject: [COREblog-en] Simpleblog -> COREBlog migration script In-Reply-To: <448B3B5A.6040808@zopeworld.com> References: <448B3B5A.6040808@zopeworld.com> Message-ID: <20060612091831.315275.e580b1d4@webcore.co.jp> Hi :-). On Sat, 10 Jun 2006 17:36:26 -0400, wrote: > Anybody have one of these? I've got some old blogs to switch over and > I'm not sure which is the easiest way to move the content. I hadn't heard know those kins of thing. If you know much about Plone/Zope API and Python, migration script will be of some help. See migration/port.py in COREBlog2's source directory. This script is to port entries in COREBlog, to COREBlog2. Regards. ---------------------------------------- Atsushi Shibata (Webcore Corp.) shibata at webcore.co.jp http://www.webcore.co.jp/ ---------------------------------------- From nekstrand at gmail.com Mon Jun 12 07:03:46 2006 From: nekstrand at gmail.com (Niklas) Date: Mon, 12 Jun 2006 07:03:46 +0200 Subject: [COREblog-en] Problem with Plone 2.1.3 ? In-Reply-To: <20060612091426.757423.aca35117@webcore.co.jp> References: <20060610162137.509537.512f4d5f@webcore.co.jp> <20060612091426.757423.aca35117@webcore.co.jp> Message-ID: Hi, thanx for your answer, I think i did, i will check it again. /Niklas On 6/12/06, Atsushi Shibata wrote: > > Hi :-). > > On Sat, 10 Jun 2006 21:00:24 +0200, wrote: > > Hi, > > > > This is the error i get an as i understand it it's some kind of > > problem with the recent portlet, so i tried to disable that one and > > then i got the second error: > > Did you obey right upgrade procedure ? > Or, recatalog may help you, I think. > > Regards. > > ---------------------------------------- > Atsushi Shibata (Webcore Corp.) > shibata at webcore.co.jp > http://www.webcore.co.jp/ > ---------------------------------------- > _______________________________________________ > COREblog-en mailing list > COREblog-en at postaria.com > http://postaria.com/mailman/listinfo/coreblog-en > Unsubscription writing to coreblog-en-leave at postaria.com > -- With best regards / med v?nlig h?lsning Niklas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://postaria.com/pipermail/coreblog-en/attachments/20060612/91e4f0d4/attachment.htm From ben.nospam at smoothify.com Mon Jun 12 12:37:30 2006 From: ben.nospam at smoothify.com (Ben Osman) Date: Mon, 12 Jun 2006 12:37:30 +0200 Subject: [COREblog-en] how to disable trackback? In-Reply-To: <20060604003747.579715.b34b1991@webcore.co.jp> References: <47990AB7-4A84-4E46-B773-D5D87CE9849E@gmail.com> <20060603235611.487450.3c098797@webcore.co.jp> <20060604003747.579715.b34b1991@webcore.co.jp> Message-ID: Atsushi Shibata wrote: > Hi :-). > > How about customizing "portal_skins/coreblog2/tbping" ? > Put floowing code after if block, so you can avoid trackback including > "buzz words" string. > > if excerpt.lower().find("buzz words") == -1: > return > > If you use Python 2.3, you can also write like this. > > if "buzz words" in excerpt.lower(): > return > > I think you should learn more about Python ;-). > > Have fun :-) > I've been getting spam too - so i used Atsushi's suggestion and extended it. Ideally should load the spamwords list from another file. You should add more words to the list (do a search for something like trackback spam word list) In "portal_skins/coreblog2/tbping" add following code after "excerpt = cbtool.convert_charcode(excerpt)": spamWords = [ 'casino', 'prilosec', 'viagra', ] words = excerpt.split(' ') for word in words: if word.lower() in spamWords: return From nachtigall at web.de Mon Jun 12 14:29:18 2006 From: nachtigall at web.de (Jens Nachtigall) Date: Mon, 12 Jun 2006 14:29:18 +0200 Subject: [COREblog-en] issue: long trackback urls do not wrap Message-ID: <200606121429.24217.nachtigall@web.de> Hi, I do report this issue here because on trac it seems not to be possible to add issues atm I do have blog entries with trackback urls like this http://freifunk.net/blog/produktion-des-meshcubes-offensichtlich-eingestellt-2013-suche-nach-alternativgeraeten-fuer-freifunk-netze/tbping Since this does not wrap at all, the middle slot gets very wide and the layout looks strange. I changed cbentry_view.cpt to

Die URL f??r den Trackback dieses Eintrags lautet:: http://trackback.url/entryid/tbping; http://trackback.url/entryid/tbping

Look at http://freifunk.net/blog/produktion-des-meshcubes-offensichtlich-eingestellt-2013-suche-nach-alternativgeraeten-fuer-freifunk-netze for how this works Ideally the trackback would use some kind of id to have a short url like in this case http://my-plone.org/blog/123/tbping Jens -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://postaria.com/pipermail/coreblog-en/attachments/20060612/f31a75ca/attachment.pgp From shibata at webcore.co.jp Mon Jun 12 15:52:15 2006 From: shibata at webcore.co.jp (Atsushi Shibata) Date: Mon, 12 Jun 2006 22:52:15 +0900 Subject: [COREblog-en] issue: long trackback urls do not wrap In-Reply-To: <200606121429.24217.nachtigall@web.de> References: <200606121429.24217.nachtigall@web.de> Message-ID: <20060612225215.926670.8d4eff5a@webcore.co.jp> Hi :-). On Mon, 12 Jun 2006 14:29:18 +0200, wrote: > Hi, > > I do report this issue here because on trac it seems not to be > possible to add issues atm > > I do have blog entries with trackback urls like this > > http://freifunk.net/blog/produktion-des-meshcubes-offensichtlich-eingestellt-2013-suche-nach-alternativgeraeten-fuer-freifunk-netze/tbping I think this is the sort of "implementation dependant". How about customizing portal_skins/COREBlog2/cbentry_view. :

http://trackback.url/entryid/tbping

: Like this.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi fellow COREBlog users! A short while ago we discussed trackback spam in here. Myself I get very few legitimate trackbacks, and too much trackback spam (even if it's less than what some people get). COREBlog is incredible great software. It already includes code that checks the trackback originator for a link to our own blog - this is discussed in some places as a measure against trackback spam. One big blogging platform has a plugin for this. See, COREBlog is already at the top of the development :-) To enable this, one checks the "Moderate No-Reference Trackback" option in the "Comment,Trackback" settings. This will turn on moderation for such trackbacks that have no reference to "our" blog. This still means that I get trackback notification mails and I will have to delete the trackbacks from the blog (even though they never show). I don't like that, so I patched my COREBlog to reject those trackbacks right away. The patch is changing only one line. You can find it here: http://betabug.ch/blogs/ch-athens/385 Regards, Sascha -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEkniqpYOq9ODq/IoRAipRAKDEmNwuIZ2/+JsjdqzK7YAUyhJZDgCgrQlA UsGS+/eX+oojge/4WJ1t8v8= =MBkS -----END PGP SIGNATURE----- From nekstrand at gmail.com Fri Jun 16 16:54:21 2006 From: nekstrand at gmail.com (Niklas) Date: Fri, 16 Jun 2006 16:54:21 +0200 Subject: [COREblog-en] Patch for Trackback rejection In-Reply-To: <20060616092548.GA16162@betabug.ch> References: <20060616092548.GA16162@betabug.ch> Message-ID: Hi, Nice, I for one would realy love to have that function on the CoreBlog2 as well. Regards, Niklas On 6/16/06, Sascha Welter wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi fellow COREBlog users! > > A short while ago we discussed trackback spam in here. Myself I get very > few legitimate trackbacks, and too much trackback spam (even if it's > less than what some people get). > > COREBlog is incredible great software. It already includes code that > checks the trackback originator for a link to our own blog - this is > discussed in some places as a measure against trackback spam. One big > blogging platform has a plugin for this. See, COREBlog is already at the > top of the development :-) > > To enable this, one checks the "Moderate No-Reference Trackback" option > in the "Comment,Trackback" settings. This will turn on moderation for > such trackbacks that have no reference to "our" blog. > > This still means that I get trackback notification mails and I will have > to delete the trackbacks from the blog (even though they never show). I > don't like that, so I patched my COREBlog to reject those trackbacks > right away. > > The patch is changing only one line. You can find it here: > http://betabug.ch/blogs/ch-athens/385 > > Regards, > > Sascha > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (Darwin) > > iD8DBQFEkniqpYOq9ODq/IoRAipRAKDEmNwuIZ2/+JsjdqzK7YAUyhJZDgCgrQlA > UsGS+/eX+oojge/4WJ1t8v8= > =MBkS > -----END PGP SIGNATURE----- > > _______________________________________________ > COREblog-en mailing list > COREblog-en at postaria.com > http://postaria.com/mailman/listinfo/coreblog-en > Unsubscription writing to coreblog-en-leave at postaria.com > -- With best regards / med v?nlig h?lsning Niklas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://postaria.com/pipermail/coreblog-en/attachments/20060616/d8293d56/attachment.htm From dsoutar at gmail.com Sat Jun 17 19:25:40 2006 From: dsoutar at gmail.com (David Soutar) Date: Sat, 17 Jun 2006 12:25:40 -0500 Subject: [COREblog-en] External Editors and Coreblog Message-ID: Has anyone had any success with using external editors via XML-RPC and the various API's? I'm using the flock browser's blog editor as well as 0.9b but still no luck getting it to connect. Is there a specific entry point i should use? or any changes i need to make within Coreblog? or any other settings at all i should keep an eye out for. many thanks - David -------------- next part -------------- An HTML attachment was scrubbed... URL: http://postaria.com/pipermail/coreblog-en/attachments/20060617/73727db6/attachment.htm From owen.nick at gmail.com Thu Jun 15 16:26:29 2006 From: owen.nick at gmail.com (Nick Owen) Date: Thu, 15 Jun 2006 10:26:29 -0400 Subject: [COREblog-en] how to disable trackback? In-Reply-To: References: <47990AB7-4A84-4E46-B773-D5D87CE9849E@gmail.com> <20060603235611.487450.3c098797@webcore.co.jp> <20060604003747.579715.b34b1991@webcore.co.jp> Message-ID: <415a28910606150726u1868ebcby23b4384d66103de0@mail.gmail.com> On 6/12/06, Ben Osman wrote: > > Atsushi Shibata wrote: > > Hi :-). > > > > How about customizing "portal_skins/coreblog2/tbping" ? > > > Put floowing code after if block, so you can avoid trackback including > > "buzz words" string. > > > > if excerpt.lower().find("buzz words") == -1: > > return > > > > If you use Python 2.3, you can also write like this. > > > > if "buzz words" in excerpt.lower(): > > return > > > > I think you should learn more about Python ;-). > > > > Have fun :-) > > > > I've been getting spam too - so i used Atsushi's suggestion and extended > it. Ideally should load the spamwords list from another file. > > You should add more words to the list (do a search for something like > trackback spam word list) > > In "portal_skins/coreblog2/tbping" add following code after > "excerpt = cbtool.convert_charcode(excerpt)": > > spamWords = [ > 'casino', > 'prilosec', > 'viagra', > ] > > words = excerpt.split(' ') > > for word in words: > if word.lower() in spamWords: > return This (plus mod_security for apache) works pretty effectively, Unfortunately, there seems to be a never-ended supply of spammable words (I don't even know what "retin" is ;). I'm back to requiring authentication for trackbacks, effecitvely turning them off. I think moderation is the answer, combined with preventitive measures. Just me .02, nick -- Nick Owen WiKID Systems, Inc. 404.962.8983 (desk) 404.542.9453 (cell) http://www.wikidsystems.com At last, two-factor authentication, without the hassle factor Now open source: http://sourceforge.net/projects/wikid-twofactor/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://postaria.com/pipermail/coreblog-en/attachments/20060615/d5b3b558/attachment.htm From bigmanjer at gmail.com Wed Jun 21 17:30:21 2006 From: bigmanjer at gmail.com (Jeremy Keiper) Date: Wed, 21 Jun 2006 11:30:21 -0400 Subject: [COREblog-en] Using local roles to hide blogs Message-ID: All - I've tried to hide blogs from particular users via local roles, but it seems that blog_header, blog_title, etc will not allow View unless Anonymous is checked. For private blogs, this provides a bit of a problem. Has anyone worked around this? - Jer -------------- next part -------------- An HTML attachment was scrubbed... URL: http://postaria.com/pipermail/coreblog-en/attachments/20060621/b2882ed7/attachment.htm From donnamsnow at gmail.com Thu Jun 22 02:06:48 2006 From: donnamsnow at gmail.com (Donna M. Snow) Date: Wed, 21 Jun 2006 17:06:48 -0700 Subject: [COREblog-en] Migration of COREBlog to COREBlog2 Message-ID: <4499DF18.4050604@gmail.com> Hi, I have a client whose site resides on at Zope 2.7.4-0 instance with COREBlog 1.0 installed. He has 300+ blog entries we need to migrate to a Zope 2.9/Plone 2.5/COREBlog2 setup. I tried the following (read the read me.. installed the files.. added the port at the end of the url) http://coreblog.org/trac/coreblog2/browser/trunk/migration I get: start! {} and nothing else..anyone successfully exported entries from COREBlog 1.0 and imported into COREBlog2? It's important that I'm able to migrate the former entries as intact as possible. any suggestions? maybe something I need to do on the new instance side?? Donna M. Snow From owen.nick at gmail.com Thu Jun 22 17:07:10 2006 From: owen.nick at gmail.com (Nick Owen) Date: Thu, 22 Jun 2006 11:07:10 -0400 Subject: [COREblog-en] Migration of COREBlog to COREBlog2 In-Reply-To: <4499DF18.4050604@gmail.com> References: <4499DF18.4050604@gmail.com> Message-ID: <415a28910606220807vbcc5453kc6ebc712549090b5@mail.gmail.com> On 6/21/06, Donna M. Snow wrote: > > Hi, > > I have a client whose site resides on at Zope 2.7.4-0 instance with > COREBlog 1.0 installed. He has 300+ blog entries we need to migrate to a > Zope 2.9/Plone 2.5/COREBlog2 setup. > > I tried the following (read the read me.. installed the files.. added > the port at the end of the url) > http://coreblog.org/trac/coreblog2/browser/trunk/migration > > I get: > > start! > {} > > and nothing else..anyone successfully exported entries from COREBlog 1.0and imported into COREBlog2? > > It's important that I'm able to migrate the former entries as intact as > possible. > > any suggestions? maybe something I need to do on the new instance side?? > > > Donna M. Snow I had the same problem. It was awhile ago, though and my memory is dull. IIRC make sure the port script is to be "Script(Python)" , not "Controler Python Script". Here are some random notes I dug up: port - the migration script - is in portal_skins/custom - COREBlog_Export - the exported text data - is also in portal_skins/custom Be sure not to include ".txt" extension in ID. - Your COREBlog2 URL might be http://localhost:8080/test212/ - Then access http://localhost:8080/test212/port with web browser. And I think the thing that really got for me was that I was using the export button on the old blog, and not the custom export script: You need to export using another export script. It is in migration directory, named 'coreblogexport.dtml.txt'. HTH, nick -- Nick Owen WiKID Systems, Inc. 404.962.8983 (desk) 404.542.9453 (cell) http://www.wikidsystems.com At last, two-factor authentication, without the hassle factor Now open source: http://sourceforge.net/projects/wikid-twofactor/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://postaria.com/pipermail/coreblog-en/attachments/20060622/7989253f/attachment.htm From donnamsnow at gmail.com Thu Jun 22 20:14:42 2006 From: donnamsnow at gmail.com (Donna M. Snow) Date: Thu, 22 Jun 2006 11:14:42 -0700 Subject: [COREblog-en] Migration of COREBlog to COREBlog2 In-Reply-To: <415a28910606220807vbcc5453kc6ebc712549090b5@mail.gmail.com> References: <4499DF18.4050604@gmail.com> <415a28910606220807vbcc5453kc6ebc712549090b5@mail.gmail.com> Message-ID: <449ADE12.5020105@gmail.com> Hi Nick (and others who might be interested), So I got a bit further yesterday... This is the original site.. http://www.digitalmusicnews.com .. but I hope to before we launch. More concerned about getting 2 years worth of articles and blogs migrated to Plone (look & feel is not a priority at this point) Here is the one entry that actually made it through... http://demo1.csquaredtech.com/import-test/78 and when I run a port I get the following... Error Type BadRequest Error Value The id "78" is invalid - it is already in use. Request made at 2006/06/22 10:54:01.238 GMT-7 Which I'm guessing means that two blogs got assigned id "78"? Taking a look at that today .. seems like a minor fix.. so now I need to figure out how to get the author and comments to migrate (last modified date would be good too ..but I'm not sure that's feasible) Do I need to setup the bloggers with user ids/membership before I port so it won't assign "admin" (which is me). Also, can I set up a blog per blogger.. at the moment my client has four bloggers.. I know Quills allows for multiple blogs (I've used it for clients before) but wonder if it's ok to have more than one blog with COREBlog2 is ok. BTW, I used the right export script the first time.. didn't get past "start!".. and then tried using the export entries button in the zmi (orig site) and it didn't work either.. BUT I actually have the export working and I'm THIS close to getting this migration script working! Thanks for the tips Nick! Donna M. Snow Nick Owen wrote: > On 6/21/06, *Donna M. Snow* > wrote: > > Hi, > > I have a client whose site resides on at Zope 2.7.4-0 instance with > COREBlog 1.0 installed. He has 300+ blog entries we need to > migrate to a > Zope 2.9/Plone 2.5/COREBlog2 setup. > > I tried the following (read the read me.. installed the files.. added > the port at the end of the url) > http://coreblog.org/trac/coreblog2/browser/trunk/migration > > I get: > > start! > {} > > and nothing else..anyone successfully exported entries from > COREBlog 1.0 and imported into COREBlog2? > > It's important that I'm able to migrate the former entries as > intact as possible. > > any suggestions? maybe something I need to do on the new instance > side?? > > > Donna M. Snow > > > > I had the same problem. It was awhile ago, though and my memory is > dull. IIRC make sure the port script is to be "Script(Python)" , not > "Controler Python Script". Here are some random notes I dug up: > > port - the migration script - is in portal_skins/custom > > - COREBlog_Export - the exported text data - is also in > portal_skins/custom > Be sure not to include ".txt" extension in ID. > > - Your COREBlog2 URL might be http://localhost:8080/test212/ > > - Then access http://localhost:8080/test212/port with web browser. > > And I think the thing that really got for me was that I was using the > export button on the old blog, and not the custom export script: > > You need to export using another export script. It is in migration > directory, named 'coreblogexport.dtml.txt'. > > HTH, > > nick > > -- > Nick Owen > WiKID Systems, Inc. > 404.962.8983 (desk) > 404.542.9453 (cell) > http://www.wikidsystems.com > At last, two-factor authentication, without the hassle factor > Now open source: http://sourceforge.net/projects/wikid-twofactor/ > ------------------------------------------------------------------------ > > _______________________________________________ > COREblog-en mailing list > COREblog-en at postaria.com > http://postaria.com/mailman/listinfo/coreblog-en > Unsubscription writing to coreblog-en-leave at postaria.com From steven at aboutpwd.com Tue Jun 27 08:49:33 2006 From: steven at aboutpwd.com (Steven =?utf-8?b?KFNoYWRkby1YKQ==?=) Date: Tue, 27 Jun 2006 06:49:33 +0000 (UTC) Subject: [COREblog-en] COREBlog2 0.9b not displaying right language Message-ID: I recently upgraded from Plone 2.1.1 and COREBlog 0.8b to Plone 2.1.3 / Plone 2.5 with COREBlog 0.9b. I am looking forward to trying out the ATVideo integration (still have to figure out how). Anyway, the reason for the post is that I have had problems with the language my blog menus, portlets, and instructions are being displayed in. It seems that instead of showing the default English language (which I have also gone and set in -> Properties -> Language and in my Plone site's settings) I am instead getting everything in Spanish. I have even tried deleting the es.po file inside COREBlog2/i18n/ on the filesystem with no results. Any advice is greatly appreciated. I cannot seem to figure out why the blog would magically change its language used from upgrading and why there is NO way that I can find to easily change that property? Thanks, Shaddo-X From steven at aboutpwd.com Tue Jun 27 09:00:27 2006 From: steven at aboutpwd.com (Steven =?utf-8?b?KFNoYWRkby1YKQ==?=) Date: Tue, 27 Jun 2006 07:00:27 +0000 (UTC) Subject: [COREblog-en] Migration of COREBlog to COREBlog2 References: <4499DF18.4050604@gmail.com> <415a28910606220807vbcc5453kc6ebc712549090b5@mail.gmail.com> <449ADE12.5020105@gmail.com> Message-ID: Donna M. Snow writes: > Also, can I set up a blog per blogger.. at the moment my client has four > bloggers.. I know Quills allows for multiple blogs (I've used it for > clients before) but wonder if it's ok to have more than one blog with > COREBlog2 is ok. You can have multiple blogs with COREBlog2 within the same Plone instance. I do not think they are able to trackback to each other (at least as of 0.8b I hadn't gotten that to work) but everything else should work just fine. Sorry I can't help out with the rest of your situation :( Shaddo-X From steven at aboutpwd.com Tue Jun 27 10:09:43 2006 From: steven at aboutpwd.com (Steven =?utf-8?b?KFNoYWRkby1YKQ==?=) Date: Tue, 27 Jun 2006 08:09:43 +0000 (UTC) Subject: [COREblog-en] COREBlog2 0.9b not displaying right language References: Message-ID: Steven (Shaddo-X writes: > Anyway, the reason for the post is > that I have had problems with the language my blog menus, portlets, and > instructions are being displayed in Spanish instead of English. I think I found the problem to this - I can't customize this while I'm at work, but the file /COREBlog2/i18n/es.po has the following lines: 11 "Language-Code: en\n" 12 "Language-Name: English\n" 13 "Preferred-Encodings: utf-8\n" 14 "Domain: plone\n" 15 "X-Is-Fallback-For: en-au en-bz en-ca en-ie en-jm en-nz en-ph en-za en-tt en-gb en-us en-zw\n" 16 17 # 18 # Portal Types 19 # 20 21 #. Default: "COREBlog2" 22 #: portal type title of COREBlog2 folder 23 msgid "COREBlog2" 24 msgstr "COREBlog2" 25 26 #. Default: "Entry" 27 #: portal type title of COREBlog2 entry 28 msgid "COREBlog Entry" 29 msgstr "Entrada" 30 31 #. Default: "Category" 32 #: portal type title of COREBlog2 category 33 msgid "COREBlog Category" 34 msgstr "Categor?a" Note that this says it is the English language name file on line 12: 12 "Language-Name: English\n" But on lines 29, 34, etc. it seems there is a Spanish msgstr translation. I think this is conflicting with the en.po file and is overriding it? I am assuming that changing line 12 to the appropriate language and possibly removing the X-Is-Fallback to the appropriate scenarios will fix this bug? Thoughts & feedback still appreciated as I've never dealt with i18n before so I may be completely off? Shaddo-X From steven at aboutpwd.com Tue Jun 27 13:06:28 2006 From: steven at aboutpwd.com (Steven =?utf-8?b?KFNoYWRkby1YKQ==?=) Date: Tue, 27 Jun 2006 11:06:28 +0000 (UTC) Subject: [COREblog-en] COREBlog2 0.9b not displaying right language References:

Message-ID: > I think I found the problem to this - I can't customize this while I'm at work, > but the file /COREBlog2/i18n/es.po has the following lines: > [omitted code] I just downloaded directly from COREBlog's website and noticed that the es.po file has already been updated. Apparently my download from Plone.org last week was not the most recent. Anyway, no bug to fix anymore - keep up the great work COREBlog! Shaddo-X From rrichieri at yahoo.com.br Wed Jun 28 23:52:55 2006 From: rrichieri at yahoo.com.br (Ronaldo Richieri) Date: Wed, 28 Jun 2006 18:52:55 -0300 (ART) Subject: [COREblog-en] COREBlog2 API Message-ID: <20060628215255.69460.qmail@web33006.mail.mud.yahoo.com> Hello, I would like to know if there is a way to use Blogger or MetaWeblog APIs with Plone 2.1 and COREBlog2. If it is possible, how can I do this? I am trying to use Performacing Firefox extension to post to my Blog. Thanks! Ronaldo Richieri / Brazil --------------------------------- Yahoo! Search M?sica para ver e ouvir: You're Beautiful, do James Blunt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://postaria.com/pipermail/coreblog-en/attachments/20060628/104647d4/attachment.htm