drewbeck

That’s really nice looking. V. slick.

I added a note to a bug that was already there. Thanks for the pointer!

This may be a problem with the interaction between WordPress and Apache (or other server software? I only know Apache). I was having some issues with the “www.fred.com” v. “fred.com” syntax and found out that my install of Apache is set to automatically redirect to “fred.com.”
The setting is called UseCanonical and it is set in the httpd.conf file.
I found that when I went to “https://www.mysite.com/blog” (with ‘www’, no trailing slash), I was redirected to “https://mysite.com/blog/”, which caused my cookies to break. I believe this was because Apache first looked for the file called “blog”, couldn’t find it, redirected to the directory “blog/” and, in the process, used the canonical version of my domain, “mysite.com”.
There might be some interaction between WordPress and this feature of Apache which causes the domain data to be rewritten in the database.

This is absolutely possible and absolutely simple. Or, rather, absolutely straightforward. What you’d want is a plug-in similar to Textile that parses your post text and converts “[[Donut Shops]]” to “Donut Shops“.
If you look through the textile1.php script, you can see that it’s basically a bunch of regular expressions that parse the text — you’d need to figure out what regex to use. Also, one would need to figure out how to wrap it up in a WordPress plugin …
From my experience skipping over the surface of geekdom, there are probably a handfull of people out there (on this board, really) who have the proper set of knowledge who could code this up in half an hour or so. I’m not one of those people, alas. But you can always hope! Or you could learn some php and figure out how the hell regex’s work …
– drew