Posted 5 years ago #
I have just updated to 2.1 from 2.0.7
I used to have my widescreen images in div's and that worked great. But now WordPress changes my entries from <div>blabla</div> to <div>blabla</div>. So now the images appear with a small margin to the left.
Is there a possible way to change this back?
(see for yourself: http://www.nehold.com)
Posted 5 years ago #
Thought that I fixed it, but it keeps on creating a without any reason!
Related: around my <!--more--> (on the site: "Lees meer") it also creates <p>..</p> without reason.
Do you have the wysiwyg editor turned off and it still has this behavior?
Posted 5 years ago #
Yes, and the source code of the posts doesn't have the <p> after my <div>'s, that's what so weird. It must be something inside the WordPress source code?
I haven't seen this reported on the forum but I could have missed it. I'll look into it.
edit - btw, I don't see this behavior in FF.
Also, look at some of these:
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.nehold.com%2F
Posted 5 years ago #
Several of these errors haven't been here before.. But I will see what to fix, and check back then. THNX!
Posted 5 years ago #
samboll: This problem has been reported before. WP 2.1 is inserting extraneous P tags in various places, and often it's not closing them. Check this out:
http://wordpress.org/support/topic/101822?replies=6
I thought I saw it elsewhere but could be wrong.
I specifically downgraded from 2.1 to 2.0.7 to fix the invalid XHTML issue this created (I post a lot of photos using DIVs). Despite the downgrade problems with links and pages, it was worth it to get the site working again. Once I switched back to 2.0.7, all the problems went away, the extra tags disappeared, and my site once again validates as XHTML.
It seems 2.1 is inserting extra tags unnecessarily, and it's doing so to the detriment of valid code and usability.
Posted 5 years ago #
Same problem here. P tag is inserted before Img tag and div tags. All my images gone from FF :(
Posted 5 years ago #
Whow, glad I'm not the only one who has this (but sorry that it even exists).
There isn't any way to bypass this whole problem temp, before another release comes out?
Posted 5 years ago #
"Whow, glad I'm not the only one who has this (but sorry that it even exists)."
Me too, I uploaded and installed to 2.1 a couple of hours ago and have been fighting the dreaded <p tags ever since.
All of my images are posted inside Divs and all are being pushed to one side ... see here; http://www.barganews.com/
I will wait another couple of hours to see if somebody comes up with a quick fix - if not then its back to 2.0.7 until this is sorted .... shame but we do at least live in interesting times don't we ?
ciao
db
Posted 5 years ago #
If you edit or save post it will not insert P tag. But when browser request url it will automatically insert P tag. I was just wondering if anyone knows the name of PHP file /code which displays post to end user.
Posted 5 years ago #
I see it's not just with DIV tags:
Posted 5 years ago #
It's really weird :) I'm waiting a week for a fix to come along, and then I'm switching back to 2.0.7
It is a shame, 'cause 2.1 is so much better for me in all the other areas! (I had a huge problem with post.php and that is all fixed now.)
xenogere: so, it's an all-round problem than.
Posted 5 years ago #
Maybe 2.1 should be placed on hold untill this is fixed?
Posted 5 years ago #
I saw it mainly with DIV tags used for images, bit it also inserts them around LABEL and TEXTAREA tags as well as the <!--more--> metacommand. It's quite odd--like an overzealous content filter in the display code (it has to be in the display code only since the extra tags aren't stored in the posts).
Posted 5 years ago #
fix22: I'd recommend holding off on the upgrade until this and a few other issues are resolved (like the non-standard XMLRPC interface).
Posted 5 years ago #
I am going to install 2.0.7 and run domain.com/blog/wp-admin/upgrade.php
Is this a good idea?
Posted 5 years ago #
Isn't there a specific instruction about downgrading in the codex?
edit: can't find it, must have made that up than :S
Posted 5 years ago #
Downgrading wasn't a quick process for me. It's easy at the beginning: Install the 2.0.7 code and run wp-admin/upgrade.php like you normally would. After that, however, I ran into some issues.
One: All links were orphaned. I had to create new link groups and make sure my links were moved into them. I didn't think this was a major problem.
Two: Pages disappeared. All of the pages moved over to posts, so I had to recreate all of my pages by hand to restore the permalinks and content. I didn't lose them, though; they just moved over to regular posts, so I had to hunt them down, copy and paste the content over, and delete the migrated posts.
I'm not sure what other problems might exist depending on how you've used WP in the past. Those were the two major issues I saw after downgrading, but your mileage may vary.
Posted 5 years ago #
Installed the 2.0.7 code and ran wp-admin/upgrade.php ...Take out all plugins BEFORE you do this though ..
"One: All links were orphaned. I had to create new link groups and make sure my links were moved into them.
Two: Pages disappeared. All of the pages moved over to posts, so I had to recreate all of my pages by hand to restore the permalinks and content."
yep, same happened to me but it only took a few minutes to hand copy and paste them from posts back into pages
All back up and running again: http://www.barganews.com ... now to wait and see what the coders can come up with
ciao
db
Posted 5 years ago #
Thanks for hints.
It is getting late at night I will try out downgrade tomorrow.
Posted 5 years ago #
There is also issue with feedburner. I need to manually ping feedburner and later I received email:
Your Ping resulted in an Error "Exceeded Access Limits - Try again Later"
Downgrade is must for me
Posted 5 years ago #
Same problem here, paragraph tags are inserted between div and img tags without the paragraph tag being closed as well.
While I'm waiting for a fix I have just copied the code from the 2.0.7 functions-formatting.php to the new formatting.php in wp-includes, which seems to work fine.
I might've broken something else by replacing the new code with the old, but in my case I haven't noticed any problem so far...
Posted 5 years ago #
I'm no expert, but isn't this an easy fix? Isn't there not just some syntax in one of the php files that needs to be fixed (or deleted)?
Posted 5 years ago #
I was also having this issue of any p tag inside a div that is inserted through the write panel, like from contact form plugins etc.-the opening p tag was there but the closing was gone.
what it is and the fix can be found here;
http://trac.wordpress.org/ticket/3669
I just inserted the one line of code found there and it fixed all my problems and hasn't seemed to break anything else yet.
Posted 5 years ago #
And what if I don't want the whole p tag? This closes the useless p tag, but it's still useless.
Posted 5 years ago #
Yep, you're right, it still inserts the p tag when it shouldn't. Bummer. But hey at least it validates...
Posted 5 years ago #
That's true :)
Posted 5 years ago #
Solution: delete line 66 (and 67, if you used the fix linked above) of wp-includes/formatting.php. This might break some other stuff, but nothing seems to be amiss for me.
Posted 5 years ago #
Yeah, I tried that and noticed it fixed it but not sure if breaks anything else though. Doesn't seem to on my local install
This topic has been closed to new replies.
