Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Just chiming in to say that I, too, am wondering how to accomplish this (or how I understand it): what I’m looking for is the ability to effectively keep wpautop “on” for the majority of a post, but selectively disable it within a post; for example, discussing a chunk of code would use wpautop — the code itself would not.

    Surely there’s a way to allow either the tag itself or a specially named div (or a set of comment-like thingies) to enable this?

    I've been trying, but a) I am not good with regexp, and b) I have no idea what's going on. :(

    On a semi-related note, on my site, I can change the labels well enough, but then I’ve got something like “Newer >> | << Older” when what I really want is “<< Older | Newer >>”

    Is there a way around this without having to hack any of the core files? Thanks!

    Also, just for kicks, I removed my custom labels, and the default labels are in fact backwards; that is, WP assigns “Next Page >>” when it means “<< Previous Page” and vice versa…

    I’m using WordPress 2.3.2, FYI.

    Thread Starter bgoulette612

    (@bgoulette612)

    Bump? ??

    bgoulette612

    (@bgoulette612)

    Silly suggestion, but have you made sure that “page.php” doesn’t have any junk in front of the very first <?php opener? In a previous file, I had an unnecessary carriage return and I got stream errors…clearing out that extra stuff fixed it…

    Of course, the problem might not be in page.php — especially if you haven’t touched it…That’s just the first thing that comes to mind…

    Edit: Looks like something in comment-functions.php or a file that loads prior to that…but you probably already figured that out…

    Thread Starter bgoulette612

    (@bgoulette612)

    It’s been a long while since I’ve bothered with this, but I’m still having the same problem…

    I totally skipped the whole upgrade procedure and just gutted all my original wp files. All of them! I left my database and tables intact…

    When I replaced all the files with the shiny new 1.5.2 files, I realized that the curly quotes were still missing…It can’t possibly be something from the wp-includes files! If anyone knows what I need to do to fix this, please let me know! I looked through the database tables, just in case there was something in there, but I really have no idea what to look for…Again, thanks in advance!

    Regards

Viewing 5 replies - 1 through 5 (of 5 total)