#2201 closed enhancement (fixed)
Auto verify/lowercase the 'Post shortname' field
| Reported by: | Owned by: | osimons | |
|---|---|---|---|
| Priority: | normal | Component: | FullBlogPlugin |
| Severity: | normal | Keywords: | shortname |
| Cc: | rjstrong@… | Trac Release: | 0.11 |
Description
It would be nice if the plugin would warn about, or even lowercase the variable given, if it contains uppercase chars. It currently allows them and will not be able to find the post if Uppercase is used.
Attachments (3)
Change History (7)
comment:1 Changed 16 years ago by
comment:2 Changed 16 years ago by
The ticket was in response to a potential bug (see attached). When creating a new entry, it allows the use of caps in the shortname; once the entry is submitted, you are immediately given an error. Is this just occurring on my install?
PS: I think this is a GREAT plugin and am really impressed with it. I just installed it from svn a few days ago and look forward to any features you add. Nice work!
comment:3 Changed 16 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
(In [2802]) FullBlogPlugin: Fix for error when parsing the page name from the URL.
Missed this when I changed URL strategy to make post names appear at the root of the URL - the .lower() was never ment to be enforced on page names.
Fixes #2201
comment:4 Changed 16 years ago by
Think I got it - thanks for the error report, and the nice feedback on the plugin. Keep testing :-)
You reckon? I don't know. Haven't given it any thought really. It was never my intention to force any convention on page names - i just used lowercase with underscore at is a common practice for many of the blogs i read. And that is something you will always have to live with anyway - for instance a link to
[wiki:wikistart](not correct camel case) will not find WikiStart.I recently had a string encoding issue, and tested all kinds of variations - not least because page names could well be international of any kind. Asian characters are a very typical example, but also much of the various European encodings.
I'll leave the ticket to ponder it a little, but I don't see any good reason to enforce any kind of standard. The only thing I can think of is making the default post name example configurable in settings - kind of 'showing the way', but not enforce.