Conflict with v3.1 of Jetpack

  • Resolved lim2me

    (@lim2me)


    10 years, 6 months ago

    Using Portfolio v2.28 and Jetpack v3.1.1.

    Jetpack v3.1 comes with a new custom post type: Portfolio. When I updated both plugins I noticed:

    * The Custom Post Type module of Jetpack activated by itself (prior to updating I had a pre-3.1 version so I had no Custom Post Type module in Jetpack)
    * The url to my main Portfolio page (handled by Portfolio plugin), and all my single portfolio pages, would not load.

    Since I had no use for the custom post type module in Jetpack, I simply disabled it and all was well.

    I suspect there is a conflict in the name chose to define the custom post type. Just thought you may want to look into this.

    https://www.ads-software.com/plugins/portfolio/

Viewing 1 replies (of 1 total)
  • Plugin Author bestwebsoft

    (@bestwebsoft)

    Dear lim2me,

    Thank you for the information. We will see what we can do.

    Regards,
    BestWebSoft Support Team

Viewing 1 replies (of 1 total)
  • The topic ‘Conflict with v3.1 of Jetpack’ is closed to new replies.