Title: [Plugin: Project Status] Permalink Conflict
Last modified: August 20, 2016

---

# [Plugin: Project Status] Permalink Conflict

 *  [NathanCorbier](https://wordpress.org/support/users/nathancorbier/)
 * (@nathancorbier)
 * [14 years ago](https://wordpress.org/support/topic/plugin-project-status-permalink-conflict/)
 * When activating the Project Status plugin on WordPress 3.3.2 using the WooThemes
   Swatch template, the custom permalinks return 404 for several areas. I’m unsure
   if this is a WooThemes issue, or a Project Status issue, but disabling Project
   Status immediately restores permalinks.
 * [http://wordpress.org/extend/plugins/project-status/](http://wordpress.org/extend/plugins/project-status/)

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

 *  [raegenhare](https://wordpress.org/support/users/raegenhare/)
 * (@raegenhare)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-project-status-permalink-conflict/#post-2751034)
 * I use a Templatic theme, and have the same problem. As soon as I activate Project
   Status, all the links go 404. As soon as I deactivate Project Status, everything
   works again.
 * I hope the developer will consider posting a patch soon. I really like the program…
 * Thanks.
 *  [daniel.l](https://wordpress.org/support/users/daniell-1/)
 * (@daniell-1)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/plugin-project-status-permalink-conflict/#post-2751069)
 * I wonder is this issue fixed or not? I’m now using a theme with portfolio/projects
   show by default, and permlink structure is [http://www.domain.com/posttname](http://www.domain.com/posttname),
   after installing Project Status, the theme project page all goes 404, however
   if I change the system permlink setting to default, everything is back again.
 * Is there a solution to fix this issue?
    Thanks.
 *  [viperousmango](https://wordpress.org/support/users/viperousmango/)
 * (@viperousmango)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-project-status-permalink-conflict/#post-2751090)
 * I’m also experiencing this issue. when Project Status is activated on my WordPress
   3.5 website running a custom theme, I get a 404 page not found error for any 
   post content types. Pages themselves are fine to navigate too.
 * I have to deactiave the plugin and re-save my permalink structure to correct 
   it.
 * Anyone have any ideas as I really do like using the plugin for clients!
 *  [vonkanehoffen](https://wordpress.org/support/users/ttr738/)
 * (@ttr738)
 * [13 years, 3 months ago](https://wordpress.org/support/topic/plugin-project-status-permalink-conflict/#post-2751107)
 * Just had this myself and fixed it by commenting out:
    `flush_rewrite_rules();`
   in project-status.php Bit of a hack as you now need to flush your rewrite rules
   manually when you activate the plugin, but it worked for me.
 * Think that function is meant to be called only once on initial plugin activation,
   hence the problem. Hope that helps someone 🙂
 *  [vonkanehoffen](https://wordpress.org/support/users/ttr738/)
 * (@ttr738)
 * [13 years, 3 months ago](https://wordpress.org/support/topic/plugin-project-status-permalink-conflict/#post-2751108)
 * line 110 btw

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

The topic ‘[Plugin: Project Status] Permalink Conflict’ is closed to new replies.

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

 * 5 replies
 * 5 participants
 * Last reply from: [vonkanehoffen](https://wordpress.org/support/users/ttr738/)
 * Last activity: [13 years, 3 months ago](https://wordpress.org/support/topic/plugin-project-status-permalink-conflict/#post-2751108)
 * Status: not resolved