Opened 14 years ago
Closed 14 years ago
#16660 closed defect (bug) (invalid)
Post body disappears after publish
Reported by: | semrocc | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.1 |
Component: | UI | Keywords: | |
Focuses: | Cc: |
Description
After upgrading to 3.1, I have noticed that the body part of new posts always disappear after being published. The same thing happens while trying to save as draft. Once I go and re-enter the body section of the post and republish it appears.
The problem seems to be unique to IE, FF appears to work as it should.
Change History (21)
#2
@
14 years ago
Sorry, I was referring to the content part of the post.
Example:
Title: "post title"
Body: "content"
Just the content area disappears after publish and needs to be reposted.
#3
@
14 years ago
- Keywords reporter-feedback added
Which version of IE? Does the length of the post body matter? Have you disabled all plugins and switched to the default theme?
#4
@
14 years ago
I tested in IE8 and the length of the post does not matter.
My testing was done with all plugins disabled, I did not notice this glitch switching to the default 2010 theme using either browser.
#9
@
14 years ago
Using your custom theme in IE8: Doesn't work.
Using your custom theme in FF: Works.
Using Twenty Ten in IE8: Works.
Using Twenty Ten in FF: Works.
This is based on your comment above. Are those four points accurate?
#10
@
14 years ago
Correct, but to add....while working in IE8, the post content disappears only on the first publish attempt. I can go and make edits at a later time and all works fine. Also, only the content disappears, the post title, excerpt, category and tag information all stays as it should.
#11
@
14 years ago
After some more analyzing, I noticed that using IE 8 and trying to post, the "word count" stays at "0" while inputting text.
If I then backspace to the beginning and start re-entering the text and then publish, it works as should. Its like it doesn't realize that I'm typing until the second try.
#12
@
14 years ago
I have now tried inputting text using the html view first and then switching back to visual. Going this route was successful using IE8.
#13
follow-up:
↓ 16
@
14 years ago
More testing shows that this problem quite likely has to do with auto-upgrade to 3.1 and TinyMCE. On a fresh install (using any theme) no problems were noticed, but on a site that was upgraded through the WP admin the problem occurs.
#14
@
14 years ago
On occasion, I have also come across this page error from within the admin...it may be related:
Message: 'ignore_rpc' is undefined
Line: 13
Char: 5360
Code: 0
URI: http://www.mywebsite.com/wp-includes/js/tinymce/wp-tinymce.php?c=1&ver=3393
*
This appears to be tied to the spell-check as well.
#16
in reply to:
↑ 13
@
14 years ago
- Resolution set to invalid
- Status changed from new to closed
On a fresh install (using any theme) no problems were noticed
Unless we can reproduce this consistently, it's very difficult to be certain that there is a bug here. It sounds very much like either a plugin or a browser caching issue (you say it only happens after an upgrade). Feel free to reopen if you still have a problem that can be reproduced.
#18
@
14 years ago
- Resolution invalid deleted
- Status changed from closed to reopened
I am still experiencing this regularly without any plugins installed and no browser caching problems. I have tested on numerous computers and WP installs with the same results. Would be nice to see it resolved.
#19
@
14 years ago
Would be nice to see it resolved
If you can provide steps to reproduce, then we'll have a go. So far, nobody can replicate the problem you're reporting.
#20
follow-up:
↓ 21
@
14 years ago
So far this morning, I have tested numerous installs and cannot replicate the problem either. I had some Windows updates come through yesterday and am now wondering if there was a connection with that.
Thanks for your attention to this.
#21
in reply to:
↑ 20
@
14 years ago
- Resolution set to invalid
- Status changed from reopened to closed
Replying to semrocc:
So far this morning, I have tested numerous installs and cannot replicate the problem either.
Let's close this off in that case. semrocc, if you can reliably reproduce the issue feel free to re-open the ticket with details.
Sorry for my question, but what is the post body?