yeago

Instead of reviving 4 months old posts… turn off the wysiwyg editor and your code will remain as you entered.

No, actually that’s not true. READ UP PLEASE. This is disinfo.

You’re right. wpautop is flawless!

oh wait

and again

And I’m the only one questioning its utility

Or do you own research into the matter

Sorry you find it nonsensical. I think that among bloggers who post a lot of html you’d find a lot of disagreement–especially if the vast amount of support posts about this topic is an indication. What’s funny is I think wpautop is quite useful as I don’t want to bother with typing p and br. However, I’m hard pressed (and have as yet received no reason) why you’d need a p or a br between any html tags, text or otherwise. With a little more constructive discussion about the logic of the wpautop function I’d say it could serve all without any fuss.

Who’s text are you talking about? If you’re talking about regular users, fine and dandy, but the fieldset is a popular tag for developers for vision-impaired users. It is a text or form-input grouping element.

I see what you mean and thank you for clarifying why some html tags are ignored by wpautop. I see its not arbitrary.

However, in the current case they aren’t “filtered out”. They are simply messed up with paragraph tags–not necessarily even disabled or non-functional, just non-standard and pesky. I think the fact that the community created a ‘disable wpautop’ plugin could be taken as a sign that the wpautop function is considered non-functional in its current state to a large slice of users.

Another fix.

https://yeago.net/works/problem-issue-with-wordpress-messing-up-html-with-p-and-br-tags

Here’s my fix:

https://yeago.net/works/problem-issue-with-wordpress-messing-up-html-with-p-and-br-tags

I’ll talk to wp developers and see if they’re interested in incorporating it in future versions.

I’m gonna take it to a more technical channel.

If anyone finds that p tags are fudging up their code, and you’re a brave code-naut you can open up wp-includes/functions-formatting.php and look at the function wpautop. To fix this I simply did:

find and replace the word ‘select’

replace ‘select’ with ‘select|*tagsYourHavingProblemWithSeparatedByPipes*’

PS: On versions other than 2.0.3 I can’t help if you mess something up.

Nah, its a bug. I’m looking at the function myself and it makes exceptions for all kinds of html tags. The fact that it treats fieldsets like regular ol’ text dirt is called one thing: BUG.

gspark, you’re missing something. =)

WP inserts Ps in all kinds of places that it just doesn’t belong.

HandySolo, disabling wpautop seems interesting but isn’t this an obvious BUG? Why on earth would WP insert Ps around things it *knows* are html tags?

Microkid, for the sake of the endless hoards who share the same problem, coould you be a little more specific?

ps: Its just an example form, not a real one.


<?php query_posts('posts_per_page=1&category_name=categoryNAME&offset='.$_GET['offset']); ?>


and then

<?php

//Hack I used.

if($_GET['offset'] == "" || $_GET['offset'] < 1){
    echo "<a href='?offset=1'>Next »</a>";
}else{
    $next = $_GET['offset'] + 1;
    $prev = $_GET['offset'] - 1;
    echo "<a href='?offset=" . $prev . "'>« Previous</a>";
    echo " - ";
    echo "<a href='?offset=" . $next . "'>Next »</a>";
}
?>

https://www.ads-software.com/extend/plugins/page2cat/

Is it related to this? I really need some feedback here =)

Nobody, eh?

un-me.