Title: [Plugin: FeedWordPress] WP crashes when Feedwordpress is activated
Last modified: August 19, 2016

---

# [Plugin: FeedWordPress] WP crashes when Feedwordpress is activated

 *  [bufordt](https://wordpress.org/support/users/bufordt/)
 * (@bufordt)
 * [15 years, 3 months ago](https://wordpress.org/support/topic/plugin-feedwordpress-wp-crashes-when-feedwordpress-is-activated/)
 * WordPress crashes when I activate Feedwordpress. Deleting the feedwordpress directory
   in the plugins directory allows WordPress to work again.
 * I have 3 other plugins activated.
 * Advertising Manager
    SimpleModal Login WP Photo album Plus
 * and I’m running the Collective 1.0 Theme

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

 *  [viralspinmedia](https://wordpress.org/support/users/viralspinmedia/)
 * (@viralspinmedia)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-feedwordpress-wp-crashes-when-feedwordpress-is-activated/#post-1948867)
 * Hi bufordt:
 * I found that my site would get this “500 server message” and discovered that 
   my .htaccess file was being rewritten. You may want to check your Cron jobs in
   your CPanel to see if there are any working.
 * If you don’t administrate the CPanel, you may want to to talk to tech support.
 * Needless to say, because my site has to remain live and running with the feeds.
   I’m trying something else.
 *  [CrisBloomfield](https://wordpress.org/support/users/crisbloomfield/)
 * (@crisbloomfield)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-feedwordpress-wp-crashes-when-feedwordpress-is-activated/#post-1948890)
 * > WordPress crashes when I activate Feedwordpress. Deleting the feedwordpress
   > directory in the plugins directory allows WordPress to work again.
 * Having the same issue here when trying to create a new install 2011.0211.2 on
   WP 3.1
 * Interestingly I have this combination working fine on two other sites where they
   have upgraded to these versions over time.
 *  [CrisBloomfield](https://wordpress.org/support/users/crisbloomfield/)
 * (@crisbloomfield)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-feedwordpress-wp-crashes-when-feedwordpress-is-activated/#post-1948891)
 * So I did some further testing and found that there is a conflict with the following
   two plugins. If either of these are active when the FeedWordpress plugin is activated
   then the whole back end crashes out:
 * Recent Posts with Excerpts
    Stop Spammer Registrations
 * With them disabled then it works just fine.
 *  [viralspinmedia](https://wordpress.org/support/users/viralspinmedia/)
 * (@viralspinmedia)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-feedwordpress-wp-crashes-when-feedwordpress-is-activated/#post-1948894)
 * Hi Cris:
 * I’m using a child theme with resident plugins built in. Thanks for posting your
   observations. This does make sense. I found that certain plugins “clash” with
   each other when activated because they are fighting for the same resources. Interesting.
   Thanks again. Very helpful. Forgot about that situation. I’ve been using wordpress
   for the last 3 years. 2 years solid and 1 year off and on.

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

The topic ‘[Plugin: FeedWordPress] WP crashes when Feedwordpress is activated’ is
closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/feedwordpress_a6a79a.svg)
 * [FeedWordPress](https://wordpress.org/plugins/feedwordpress/)
 * [Support Threads](https://wordpress.org/support/plugin/feedwordpress/)
 * [Active Topics](https://wordpress.org/support/plugin/feedwordpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/feedwordpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/feedwordpress/reviews/)

 * 4 replies
 * 3 participants
 * Last reply from: [viralspinmedia](https://wordpress.org/support/users/viralspinmedia/)
 * Last activity: [15 years, 2 months ago](https://wordpress.org/support/topic/plugin-feedwordpress-wp-crashes-when-feedwordpress-is-activated/#post-1948894)
 * Status: not resolved