So I was doing routine maintenance on the Caveena Website today when a conflict between two WordPress plugins mucked up our Portfolio page. Being a service-based organization, yeah that’s a pretty big deal.

And this is why I always test website updates on a development server.

So what happened? The issue was between BestWebSoft’s Portfolio Plugin (which, as you probably guessed, we are using for our Portfolio page) and Jetpack. The v3.1 release of Jetpack comes with a new custom post type: Portfolios. I didn’t dig into any of the code but my guess is they used the same name for the Portfolio custom post type. When both were active the permalink would not work and none of our portfolio project pages would display.

The fix was simple enough:

  1. Disable the Custom Post Type module in Jetpack’s settings.
  2. Re-build the permalink structure.

If you happen to be using the Portfolio plugin along with the Custom Post Type module in Jetpack, I unfortunately have no answer for you.