Re: contributed plugins 1.2.2 released
will guaraldi <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.user |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 22 Jun 2005, Joseph Reagle wrote:
>
> ** any reason the file naming convention went from 'contrib-1.2.1' to
> 'contrib.1.2.2' that shift from '-' to '.' caused me to make a stupid
> mistake.
I wrote a new packaging script for 1.2.2 which is how it got changed.
There is no standard for release names, so I'm not sure what to tell you.
> On Tuesday 21 June 2005 14:35, will guaraldi wrote:
>> comments
>>
>> * comments no longer shows comments by default! In order to view
> comments
>> for a given entry, you must append "showcomments=yes" to the
> querystring.
>> THIS IS NOT A BACKWARDS-COMPATIBLE CHANGE! Thanks David!
>
> I never understood David's intention nor the inconsistency but figured
> if it caused a problem for someone else I could accommodate the shift.
> However, my code now reads:
>
> <a href="$base_url/$file_path" title="Permalink">this entry</a> posted to
> <a href="$base_url/$path" title="Category">$absolute_path</a>; <br/>
> <a href="$base_url/$file_path?showcomments=yes" title="Comments
> ($num_comments)">comments ($num_comments)</a>
>
> So the user is going to have to be clueful that they can't leave a
> comment on the "the entry" but have to click "comments" instead? (Is
> that a common blog convention?) Making the "this entry" show the
> comments too, as I originally did, means I have the query option in the
> permalink which I don't want.
Um... I guess you could add some code to make the behavior configurable
or you could take the code out.
>> * comments no longer has documentation for the unused
> comments-rejected-words
>> property.
>
> What does this mean? My config.py has:
> py['comment_rejected_words'] = ['casino', 'poker', 'loans', 'mortgage',
> 'drugs', 'loss', 'blackjack']
> This isn't supported anymore?
The comments plugin doesn't use the comment_rejected_words config
property and didn't in the version that came with contributed plugins
1.2.1 either. The documentation was left in by mistake and I removed it
in the version that was released with 1.2.2.
I have a plugin called wbgcomment_blacklist which uses that property to
reject comments that have blacklisted words in them. If you don't have my
plugin, then that line in your config.py file won't do anything.
I'm pretty sure we covered this back in May when you asked why setting
comment_rejected_words doesn't seem to do anything.
> Also, thought I would test the rendering in IE 6.0 and noticed a very
> strange behaviour. If I load:
> http://reagle.org/joseph/blog/
> in IE, it renders the page. However, if I ask it to reload or go back to it
> later, I get a blank document?!
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META http-equiv=Content-Type content="text/html;
> charset=windows-1252"></HEAD>
> <BODY></BODY></HTML>
I have no idea what the issue is here. I've never seen anything like that
before, though I don't use IE anymore and your site works fine in Firefox.
Your server returns the same response for both IE and Firefox, so I think
it's a client issue.
My best guess is either you have meta tags in your html page that cause IE
to do something "interesting" or the HTTP response isn't quite right in
such a way that causes IE to do the wrong thing.
The HTTP response is this:
HTTP/1.x 304 Not Modified
Date: Wed, 22 Jun 2005 17:21:42 GMT
Server: Apache/2.0.46 (Red Hat)
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
Etag: "1118428239.0"
Vary: Accept-Encoding,User-Agent
Can anyone who has IE 6.0 work through and figure out what the issue is?
/will
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click