Breaking down the Jetpack megalith

  • This is an imaginative concept, to break down the Trusted Jetpack Megalith. So many people have complained about poor performance with Jetpack, although to be clear, much of that is due to users not understanding how to disconnect various services they don’t want.

    However, having a choice of discreet functions, such as widget visibility is a more economical way to go. I notice you have done the same breakdown for some other areas of jetpack.

    Some questions: if I use your discreet version of widget visibility and then install jetpack, will there be a duplication of DB tables? will I be able to ‘inherit’ the discreet version widget settings? Any conflicts? Or other problems?

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

  • I’m glad you like them.

    To answer your question:
    I assume you mean the case when you need more functions and decide to use the whole Jetpack, you want to make sure your configurations are not lost.

    Yes, any configurations you make with on of the Jetpack plugins I published, will work with the original Jetpack.

    You’ll see conflicts if you try to activate the original Jetpack with one of the Jetpack plugins I published.

    There is no DB duplication. The same tables will be used.

    Thanks for your review.

    Thread Starter houseofstrauss

    (@houseofstrauss)

    Ok, that’s good to hear, but worth noting a caution if thinking of using both plugins. I suspect many people will value the choice you are offering. I’m gonna give a 5 star review for ‘user choice’ and creativity.

    Thank-you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Breaking down the Jetpack megalith’ is closed to new replies.