uncheck “Attempt to notify any Weblogs linked to from the article (slows down posting.)” in the admin section. Can be found at options -> discussion.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
To further explain the situation, it’s due to a setting which sends automatically sends a pingback (like a trackback) to all links in the post. Your post published as soon as you hit the publish button, but WP is still waiting for a return response from Amazon. Technically, the problem is Amazon’s, as they are not returning your ping, but you can disable the feature by deselecting “Attempt to notify any Weblogs linked to from the article (slows down posting.)” in Options/Discussions.
Is there something else that can override that box? I have mone unchecked and it still pingbacks. Yes I know the difference. strange others can’t get it to work and I cannot get it to stop.
I have a similar problem with hangs, but only once in a while. But when it happens it posts 4 times.
maybe try removing the entries in the Update Services (Options-Writing)?
Removing the entries in the Update Services worked. Thanks!
mine was simple. The pingbacks were hard wired, so unchecking the box didn’t do anything. I had to edit a couple of files. Now it is fixed. Thanks
>>>Once I click on the publish button the page never refreshes. <<<
I’ve had the same problem. I end up editing what I just edited and after saving, it writes over what I did the last time, I have a mess since I didn’t really “make” any of those first saved changes.
After hitting Save and Continue Editing, hit REFRESH and it will load in the last saved info to the database, which you just saved.
I’ve found this problem more with Firefox than with MSIE. Just hit Cntrl+Shift+R and your “saved” page will reappear. FF just reloads the cached original page, not the new one, so a forced cache clearing usually does the job.
It’s a problem with FF not with WordPress, though maybe there is something in the code that is magical to me that might force the total refresh…
I use IE. I found out by testing to my own posts that even unchecked I was still performing pingbacks. This is a problem when the sites being checked do not respond. It hangs. The fix is to repair the code in 2 files. I posted this fix previously about pingbacks. The files have the pingbacks hard coded on. the check box is irrelevant.
If you want I will find it for you, just email me brianbonner90 at gmail dot com
As a point of interest, I don’t have this problem with Firefox at all. It always refreshes just fine on publish, and multiple sequential edits don’t cause the same troubles as you have either, Lorelle.
I’m using FF1.0.3, but 1.0 through 1.0.2 were fine as well.
It only happens with large posts, I’ve been able to figure out. But I’m not the only one who reported this behavior. Someone pointed out the answer to me on the forums a couple months ago when I was going bonkers with this. And there have been quite a few posts from time to time reporting the same behavior. It’s been reported as a bug to WP Mosquito, but it really is a problem with FF.
Lucky you not to have it. I have to deal with it very frequently. Did it in 1.0.1, 1.0.2, and now in 1.0.3. I kept thinking each new version would kill it. It does help when I set my cache to about zero, but it takes FOREVER for pages to load.
Brianbonner: I wasn’t talking about the ping issue. That is completely unrelated. That is part of the slowdown of posting.
Have you checked bugzilla for anything reported there? There might be a simple workaround or fix…. I’m not that good with the about:config stuff, there’s probably something you could do there, but I wouldn’t know offhand.
Hmm. I do have some “unusual” settings in FF though, courtesy of a FF guru I know. If you want to try them, email me sylvermoon (at) gmail.com, and I’ll send you the whole banana.
Same refreh problem with Firefox appears in Konqueror.
brianbonner, what files have you edited?
Lorelle: So glad that you posted about this. I’ve been using WP for 2 mos. now & didn’t notice the hang problem until a few wks. ago. But it’s getting more severe. I too use FF (1.0.5).
When I do a hard Reload after publishing, then the new material appears. Guess I’ll have to use that fr. now on though it’s a slightly unwieldy workaround.
thanks again…
