Should not be part of core

  • This should remain a plugin that people can choose to use if they wish. It should not be part of core. It is not ready for core. It is something geared towards .com not .org installations.

    There are more important things that need to be in core first before this should even be considered.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tammie Lister

    (@karmatosed)

    @simonp303 thanks for taking time to leave a review. What features do you feel need to be worked on to make it ready for core? I’d love to explore more what you feel is the baseline there. When you mention other important things what are you thinking of?

    Thread Starter Simon Pollard

    (@simonp303)

    It just needs an ability to be turned off – there are far too many plugins and themes that need the editor to remain as standard.

    Going forward it can then be enabled once people have had the chance to test. Noting that some people just have 1 site, they don’t have the luxury of a staging or local site to test on. Enforcing such a massive update on what in a lot of cases is someones business is a big concern to me.

    The more control people have, and the less it is enforced the more happy engagement there will be. Such as when U2 forced there album on iTunes users, it was not appreciated. Offer it for free and let people choose, it would have gone down a lot better.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Should not be part of core’ is closed to new replies.