Title: fclose() problems
Last modified: August 18, 2016

---

# fclose() problems

 *  [brainwidth](https://wordpress.org/support/users/brainwidth/)
 * (@brainwidth)
 * [21 years ago](https://wordpress.org/support/topic/fclose-problems/)
 * After a relatively successful upgrade to 1.5.1, I applied the fixes for the rss
   problem, as well as removing the if_function which appears to be causing the 
   extended ping problem. I tested both ping and trackback functionality using Red
   Alt’s Pingomation, and I can send and receive both pings and trackbacks. However,
   I have two related problems that I would like to solve if at all possible.
 * (1) Although I appear to be pinging the Ping-o-matic service, the Red Alt tool
   tells me that my blog has no last update record at Ping-O-Matic. Why?
 * (2) Although I received the ping from pingomation, I get the fclose related error
   [detailed here.](http://extraball.sunsite.dk/notepad.php?ID=7404&parse=) What
   gives? If it matters, I’m on dreamhost.

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

 *  [klklaser](https://wordpress.org/support/users/klklaser/)
 * (@klklaser)
 * [21 years ago](https://wordpress.org/support/topic/fclose-problems/#post-204276)
 * _(2) I get the fclose related error _
 * The programmers are working on that issue now, but I don’t think anything’s been“
   committed” yet in regards to fclose on 1189 of xmlrpc.php. There are more details
   about it [here,](http://mosquito.wordpress.org/view.php?id=1324) search the page
   for: fclose .
 * If you’re interested in the interconnections between functions, I’ve found [this tool](http://www.cenamayo.com/wpxref/nav.html?_functions/index.html)
   educational.
 *  Moderator [James Huff](https://wordpress.org/support/users/macmanx/)
 * (@macmanx)
 * [21 years ago](https://wordpress.org/support/topic/fclose-problems/#post-204279)
 * 1. I don’t trust that part of the Red Alt tool. It hasn’t been accurate for me.
   To check your ping-o-matic success, run over to [http://blo.gs](http://blo.gs)
   and search for your blog. If you find that it has been recently updated there,
   then you are pinging ping-o-matic. If it hasn’t, then you should apply the patch
   here: [http://mosquito.wordpress.org/view.php?id=1325](http://mosquito.wordpress.org/view.php?id=1325)
 * 2. The fclose error is actually related to the pingback problems. To fix it, 
   use the wp_remote_fopen patch here: [http://mosquito.wordpress.org/view.php?id=1324](http://mosquito.wordpress.org/view.php?id=1324)
 *  Thread Starter [brainwidth](https://wordpress.org/support/users/brainwidth/)
 * (@brainwidth)
 * [21 years ago](https://wordpress.org/support/topic/fclose-problems/#post-204426)
 * I’ve applied the fix for 1325, I’ll have to see if the 1324 fix helps. Thanks!
 *  Thread Starter [brainwidth](https://wordpress.org/support/users/brainwidth/)
 * (@brainwidth)
 * [21 years ago](https://wordpress.org/support/topic/fclose-problems/#post-204689)
 * I fixed the fclose() problems by moving to revision 2606 of functions.php and
   xmlrpc.php. However, I’m still generating no record at ping-o-matic, and instead
   of getting the fclose error when receiving pingbacks, I get [this one](http://pastebin.com/285341).
   The ping still shows up on my post, though.

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

The topic ‘fclose() problems’ is closed to new replies.

## Tags

 * [pingomatic](https://wordpress.org/support/topic-tag/pingomatic/)

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 4 replies
 * 3 participants
 * Last reply from: [brainwidth](https://wordpress.org/support/users/brainwidth/)
 * Last activity: [21 years ago](https://wordpress.org/support/topic/fclose-problems/#post-204689)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics