Title: 's Replies | WordPress.org

---

# vtradmin

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

 *   [Profile](https://wordpress.org/support/users/vtradmin/)
 *   [Topics Started](https://wordpress.org/support/users/vtradmin/topics/)
 *   [Replies Created](https://wordpress.org/support/users/vtradmin/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/vtradmin/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/vtradmin/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/vtradmin/engagements/)
 *   [Favorites](https://wordpress.org/support/users/vtradmin/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: [PHP Fatal Error after upgrading to 2.6.2](https://wordpress.org/support/topic/php-fatal-error-after-upgrading-to-262/)
 *  Thread Starter [vtradmin](https://wordpress.org/support/users/vtradmin/)
 * (@vtradmin)
 * [17 years, 7 months ago](https://wordpress.org/support/topic/php-fatal-error-after-upgrading-to-262/#post-884153)
 * Well, it looks like the problem wasn’t with WordPress. One of the developers 
   at my company had tried to integrate the blog into a broader site framework, 
   and he got pulled off the project before he’d really finished. Some of the legacy
   code/Apache rules were causing the problem.

Viewing 1 replies (of 1 total)