Would prefer Pepper not pre-installed

Plugins
1

I’m a big fan of security and especially plugins that help to achieve that.

However I am not a fan of the Pepper plugin itself nor installed on core updates. Recommended or optional - absolutely. Just like Classic Directory is - absolutely. Forced install, just no.

I would prefer it was optional and not added on install. It’s kinda like the Hello Dolly all over again.

This plugin seems to create a bit of confusion and difficulty for people, and I see people getting locked out and not understanding what the plugin does.

You have to understand not everyone are techies and devs. If you give them a plugin they are going to use it. I can see this creating issues for clients as we shift over to ClassicPress.

Again. Please remove it as a forced install on core updates and please let users decide if they want to install it - just like the Classic Directory.

Apologies but I have a strong opinion on this one.
Thank you. :pray:

2

I will not take a position on your point, but:

  • it’s already installed in 2.2, so we can’t remove it from current version.
  • it was later upgraded to fix a bug, so we must push it also in 2.3 because it can cause errors.
  • we can’t remove a feature until version 3.

Edit: with “we can’t” I mean that SemVer don’t allow us to do that.

2 Likes
3

NP at all Simone. But do consider shifting it to an optional install, just like Classic Directory as an example.

1 Like
4

I have a question. A big one probably as usual. Can a screen be integrated in the CP install process that lists plugins like Switch to CP, Directory Integration and Pepper and asks user to select which ones to install on the core during install? would this mean keeping various types of packages for CP for the various scenarios and installing the one that the user select or would it be easy to just do the install and download the plugin(s) selected?
tagging @MattyRob and @timkaye here also since I do not have a clue how difficult this might be (I think it should not, it’s just adding a function to install the plugins from somewhere).
I agree that being a breaking change it should go in v3, just to understand if it is feasible.

2 Likes
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.