Title: wordpressuser101's Replies | WordPress.org

---

# wordpressuser101

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

 *   [Profile](https://wordpress.org/support/users/wordpressuser101/)
 *   [Topics Started](https://wordpress.org/support/users/wordpressuser101/topics/)
 *   [Replies Created](https://wordpress.org/support/users/wordpressuser101/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/wordpressuser101/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/wordpressuser101/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/wordpressuser101/engagements/)
 *   [Favorites](https://wordpress.org/support/users/wordpressuser101/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: [segfault when trying update WordPress/plugin versions](https://wordpress.org/support/topic/segfault-when-trying-update-wordpressplugin-versions/)
 *  Thread Starter [wordpressuser101](https://wordpress.org/support/users/wordpressuser101/)
 * (@wordpressuser101)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/segfault-when-trying-update-wordpressplugin-versions/#post-9422061)
 * Thanks for the solution, it worked well (just have to change permission). In 
   fact, i think that in step 3, WordPress bypass that at-risk detection and always
   create files using the ‘direct’ method. I think it can be a security risk in 
   specific situation like “poorly” configured shared host. Anyway, you can always
   just add the line when you need to update stuff and deleted it after!

Viewing 1 replies (of 1 total)