jaykul

Well, I made it work on my site, in my own personal, but extremely immitable, way.
https://www.huddledmasses.org/2004/05/28/prev-next_links/

I’m feeling ignored again.

No. It’s not true.
HACK THAT index.php TO PIECES and make it your own. It’s your website.

Shushubh: I believe you! (I think)
My point is: You have to add code to index.php to make that happen. So the feature ships broken. When a (new) user changes that option, NOTHING happens. They have to go find out that they have to put “posts_nav_link()” _INSIDE_ the content div …

Uhm. This an example of a paged post:
https://www.huddledmasses.org/2004/05/13/
And I have my settings set to “posts” now because it makes no difference

Heh, yeah! Hopefully the edit clears things up. I’m still convinced that “posts paged” is the same as “posts.”

Forbidden text is simple, just modify photomatt’s acronym hack
https://photomatt.net/scripts/acronymit
or this word-replacement hack
https://dougal.gunters.org/index.php?p=288&more=1&c=1
Actually, come to think of it, I wrote my own acronym hack, and I think my regular expression is in better shape than the one on phottomatt’s.
/source.php?file=acronyms.php&justcode=true
Copy that file to your server, and then include it, and use add_filter to make wordpress use it.
To make it REPLACE words instead of turning them into acronyms … you would edit that list of words, and then change the replacement line to this:
$text = preg_replace(“|([\s\>])(“.$acronym.”)([\s\<\.,;:\\/\-])|imsU” , “$1”.$description.”$3″ , $text);
Of course, someone could get around to re-writing one of these hacks as a simpler word-filter which just puts *** in — instead of making you define a replacement for every word (Although I like the idea of putting in funny words like “kittens” to replace “s**t” … that’s what we do on the forum I moderate)

Not saying YOU didn’t, but all these text-replacement hacks gotta make sure they get the regex right for words, and are HTML aware, so here’s a stab at it:
preg_replace(“|([\s\>])(“.$KEYWORD.”)([\s\<\.,;:\\/\-])|imsU” , “$1$2$3” , $text);
of course, that one doesn’t DO anything, you’d have to insert your text between the $1 and the $2 and the $3 ??

To keep it from messing up links, just change your search expression so it requires a space (or other punctuation) around the acronym. It ought to be done that way to start with, I’d think (that’s how mine is done)

request #1: a better plugin architecture
request #2: that all other requests be fulfilled in plugins.
??

hmm, now what I need is a community Giggle file, so that the people I trust can all ad their own pages with a keyword or two … and we can automagically link to each other’s good articles…

*randlomly walks in and messes with everyone’s minds*
It seems to me that this whole discussion is confusing DISPLAY with FORMAT.
Just because the entries in the category list are FORMATTED as a list, doesn’t mean you have to DISPLAY them that way.
https://www.alistapart.com/articles/taminglists/
https://www.alistapart.com/articles/slidingdoors/
https://www.alistapart.com/articles/slidingdoors2/
Semantically correct markup doesn’t mean your website has to be ugly … in fact, my problem is that I need <span>s inside my lists to make my sliding doors work … can we make that an option?

Phhhhhaugh! I actually skipped the last few posts of this because everyone seemed to be splitting along lines that have become all-to-familiar.
Can I suggest something very simple? CHANGE the default WP template. It’s NOT sufficiently skinnable to attract any interest from the sort of people you want to design layouts for you. END OF STORY.
What I’m getting at is that if you want to bother soliciting designs, you want some really talented designers to play with you. For that, you need a template that has a few more <div> tags, and not quite so many double-wrapped divs, so that you can actually change the design in CSS, instead of just fiddling with the colors =T
I (and many others, I’m sure) would be happy to donate a more CSS-magic-friendly template which would of course still pass all the usual compliancy tests.
 
Now, to further elaborate on the general concept: What’s called for is a “wp-style” directory off the root, so that the entire design could be hacked by simply dropping in a new style directory, without changing any of the (new) original template. Thus, the current .css would move in there, and the designer would be free to put any images they wanted to use into that folder (or sub-folders of it).
If you want to do this now, your ‘designs’ would have to be able to replace the default index.php (at least) and probably the wp-comments*.php and archives.php too. =(

The reason it’s being download instead of displayed is the “application” in the mime type. RSS is marked as text/xml, but the ATOM is application/atom+xml. If it were text/atom+xml, IE would display it.
The applicable RFC RFC3023 suggests that if an XML document –that is, the unprocessed, source XML document– is readable by casual users, text/xml is preferable to application/xml because user agents (read web browsers) that do not have explicit support for text/xml will treat it as text/plain, displaying the source as plain text.
The RFC specifies that the conservative principle is to use application/xml instead of text/xml so as not to put information in front of users that they will quite likely not understand. That’s the reasoning for choosing application/xml for atom, (if you have a look, I think you’ll agree that the raw document is absolutely not readable by casual users — heck, even technically adept users would probably have a hard time with it unless they’re used to reading unfamiliar xml dialects.
blah blah …
P.S.: it seems to me that application/rss+xml would be more appropriate for the rss feeds …

Heh. I already had one. In fact, it’s almost exactly the same. I don’t sort mine, and I put it in an external file “acronyms.php” and included it, it helps keep all my content filters separate.
/me steals a few extra acronyms