rustindy

Personally, I use the following 3 plugins to combat spam, and so far it’s 100% successfull:
– Bad Post ID
– URI Blocklist
– Spam Stopgap

I even deleted all the words from the built-in moderation/blacklist boxes (except for “online-poker” in the blacklist one). I haven’t had a spam post for 5 or 6 weeks now 🙂

Course, I haven’t noticed any trackback spam yet – I don’t think any of these plugins will help with that…

Don’t quote me, but it looks like “feed:” is being used as a protocol type (like “mailto:” and “aim:” etc.). Presumably, this means that it will eventually be recognized by feed readers and aggregators allowing you to subscribe to an RSS or ATOM feed simply by clicking the link. I’m not aware of any aggregators or feed readers that actually use it at this point though.

To get rid of it, just delete the “feed:” bits from the “footer.php” file in your template(s).

PHP’s default value of 8MB for maximum script memory is very often inadequate for large sites. Unless your server is extremely low on available memory, increasing this to 16, 24, or even 32 (which is one of the recommended values) will have no adverse effects and should get rid of that error message.

So if you adjust the “memory_limit” value in your PHP.ini file to 24M or 32M, it should be fine (you probably have to restart the web server after the change to make it take effect).

Anyone know if there’s a similar program available for Palm or for Java-powered cell phones?

It’s the one labelled “Beta Discussion” on the http://www.wordpress.org/support/ page 😉

In a word, avoid da flash where possible. Search engines won’t crawl it, and it pisses some of us off mightily 😉 Of course, it can be used sparingly for menus and other special applications – just not for entire websites. Unless the point of the website is to be a flash portfolio, of course. Even then….

Anyways, you really wouldn’t really need any more files than a normal 1.5 theme (for example) already has. It’s just a matter of creatively coding the site 😉

Assume, for example, that when someone goes to the site, they see the top menu, the sidebar contains category links and the search thingy, and the main content area has only the most recent post listed (and possibly the previous 3 in excerpt form for convenience). The user clicks the “Archive” link in the top menu.

In scenario #1 above (from my previous post here), a javascript would simply change the src parameter of the sidebar iframe to read sidebar.php?section=archive (for example). The sidebar.php file is simply a normal sidebar template file with switch blocks around each of the sections – if no section querystring is given, it defaults to “category”, otherwise it’ll display the named section. Benefit: less data to transfer to the client on any given page. Con: the iframe refreshes from the server.

In scenario #2, the javascript would instead use the DOM to hide the “category” div and unhide the “archive” div. Benefit: speed – there is no refresh lag. Con: the content of all the sections must be downloaded to the client.

In practice, it would work best to combine the two methods – use the DOM method for changing the sidebar, but use the iframe method to update the main content area if someone clicks a story or archive link.

Kinky 🙂

podz, browsers ignore extraneous whitespace completely (like tabs and multiple spaces), and IE and FireFox (and probably all other browsers) display the source file exactly as it’s sent from the server – they don’t add tabs or spaces to the View Source.

RSL, look for the PHP escaped tab command – it’s /t and will always be enclosed by quotation marks. Removing that slash-t command from echo commands and variables will remove the tabs. But I don’t recommend it.