Forum Replies Created

Viewing 15 replies - 91 through 105 (of 390 total)
  • Thread Starter rustindy

    (@rustindy)

    I should also say that I don’t really care what *most* people do. Let them eat cake, so to speak. I’ll learn to grow cattle so I can have my damn steak 🙂

    I’m not sure where to buy cow seeds though…

    Thread Starter rustindy

    (@rustindy)

    Whooami – I didn’t know Bad Behaviour did that, I’ll look at it for sure. I have also thought about just hardcoding the renamed comments file, but I thought it would be too easy for a spammer to figure out if they wanted to. It’d be nice to have the filename completely randomized on a per-use basis.

    The problem with using referer fields to prevent spam is that many people surf with them blocked. Isn’t that what using mod_rewrite would rely on?

    Any solution would also have to be completely cross-platform and server independent (so it should work equally well on *NIX and Windows, with at least IIS and Apache). That also removes mod_rewrite from the equation since most IIS servers don’t have an equivalent filter.

    Thread Starter rustindy

    (@rustindy)

    Macmanx, the method I’m suggesting (or rather, asking about) doesn’t have anything to do with false positives or making WP decide what is and is not spam. The operation of either method would be 100% transparent to the user. I’d like to see WP somehow hide the comment file itself so that bots can’t find it but users will still see it.

    There *must* be a way to do it, and now I’m asking for people to suggest how 🙂

    Forum: Fixing WordPress
    In reply to: Avoid caching
    rustindy

    (@rustindy)

    There is a “no-cache” meta tag you can put in your HEAD section, and that’s *supposed* to prevent browsers from caching the page. But it’s up to the browser to support it and listen to it. I think most do.

    Or I could be thinking of something else and be completely wrong.

    Anyways, the code is:

    <meta http-equiv="pragma" content="no-cache" />

    Forum: Installing WordPress
    In reply to: Free Hosting
    rustindy

    (@rustindy)

    innereyes.com does free WP hosting 😉

    rustindy

    (@rustindy)

    A good point – sometimes the sidebar is too short to make it necessary to provide a skip link or place it after the content in the source.

    It is definitely possible with CSS. Negative margins are one way, but I personally haven’t experimented much with them. So far the only site I’ve designed (such as it is) that adheres to my own preaching is digitalrights.ca and it’s done simply with floats and some creative positioning. I even got it to keep both posting sections in order in the source 🙂

    Course I haven’t really road-tested it much yet, so who knows if anything’s broken in that one…

    rustindy

    (@rustindy)

    Most people’s sites don’t though 😉 And most of them should.

    Forum: Fixing WordPress
    In reply to: 1.5.1 RSS issue
    rustindy

    (@rustindy)

    allrighty, now my main RSS feed works with (another) new post, but the category feeds are still screwed.

    rustindy

    (@rustindy)

    Yup, I’m all for semantic ordering of content 🙂

    A standard blog layout might look like this in source:
    – header
    – main menu or navigation (if any)
    – content
    – sidebar(s)
    – footer

    And viola, a semantic source layout 🙂

    For example, check http://www.digitalrights.ca/ if you want. It’s laid out that way, though my CSS is still kinda messy. Haven’t had time to finish the thing 🙁

    Forum: Fixing WordPress
    In reply to: 1.5.1 RSS issue
    rustindy

    (@rustindy)

    Any fix info for those of us who don’t have an SVN client installed? Like the code that has changed in order to repair the RSS feeds? 😀

    rustindy

    (@rustindy)

    Probably, although the content technically (semantically) shouldn’t be part of a definition list.

    rustindy

    (@rustindy)

    If you can make the content come before the sidebar in the source code, I’ll really be impressed 😉

    Forum: Fixing WordPress
    In reply to: 1.5.1 RSS issue
    rustindy

    (@rustindy)

    How did a bug like this make it through Q&A?

    Adding a new post didn’t seem to do anything, and so far neither has changing the feed prefs and adding a post. I’ll keep trying, but in the meantime, all of the 1.5.1 RSS feeds on my server are broken.

    rustindy

    (@rustindy)

    Sorry Poon, I never received any question about adding comments to the asides.

    Kafkaesqui has it right though – my plugin works off the custom fields and are tied specifically to the post they’re added to. There is no easy way to add commenting to them.

    I’ve actually been looking at the MiniBlog plugin lately to handle asides on my site.

    Forum: Fixing WordPress
    In reply to: 1.5.1 RSS issue
    rustindy

    (@rustindy)

    Well I upgraded to 1.5.1 and posted and my feed has a ‘strtotime()’ warning in it and nothing else 🙁

Viewing 15 replies - 91 through 105 (of 390 total)