Title: ds017's Replies | WordPress.org

---

# ds017

  [  ](https://wordpress.org/support/users/ds017/)

 *   [Profile](https://wordpress.org/support/users/ds017/)
 *   [Topics Started](https://wordpress.org/support/users/ds017/topics/)
 *   [Replies Created](https://wordpress.org/support/users/ds017/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/ds017/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/ds017/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/ds017/engagements/)
 *   [Favorites](https://wordpress.org/support/users/ds017/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Unable to update plugins after upgrade to 4.2](https://wordpress.org/support/topic/unable-to-update-plugins-after-upgrade-to-42/)
 *  [ds017](https://wordpress.org/support/users/ds017/)
 * (@ds017)
 * [11 years ago](https://wordpress.org/support/topic/unable-to-update-plugins-after-upgrade-to-42/page/2/#post-6052691)
 * Fixing line 149 in wp-admin/includes/file.php does indeed do the trick. One thing
   to keep in mind: if you have a site on 4.2 and want to get it to 4.2.1 for the
   security patches, you likely need to patch that line. Then if you want to update
   plugins, you’ll need to patch that line again since the 4.2.1 update will overwrite
   file.php.
 * Sure hope this is fixed in 4.2.2. It’s keeping auto-updates from applying in 
   addition to interfering with updates of plugins, themes and core wordpress itself.

Viewing 1 replies (of 1 total)