Open GoogleCodeExporter opened 9 years ago
yeah probably agree this should be set to disabled for new plugins...
This just requires line 174 of plugin_functions.php changed to false.
Original comment by MichaelS...@gmail.com
on 17 Jul 2012 at 6:26
Original comment by tablatronics
on 18 Jul 2012 at 4:13
Do you know of a way we can indicate new plugins that have never been enabled ?
Original comment by tablatronics
on 24 Jul 2012 at 2:32
Original comment by tablatronics
on 5 Aug 2012 at 1:51
just noticed that if we install from scratch the 2 bundled plugins
'innovation_settings' & 'anonymous_data' are not enabled by default with this
fix.
maybe we should include a base plugins.xml file as part of the distro to get
around this.
Original comment by MichaelS...@gmail.com
on 4 Sep 2012 at 3:52
I just noticed this as well.
Including a base plugins file is not the answer though, it will mess up
upgrades and can mess with permissions.
I would rather we auto enable them on install through code.
Original comment by tablatronics
on 7 Sep 2012 at 5:33
Anyway IMHO this disabled-by-default change is not a minor one (while I think
it's a good idea).
I suggest not changing this in the next 3.1.x, or rename next release to 3.2
Original comment by carnav
on 8 Sep 2012 at 3:18
We are no where close to a 3.2 release.
I think this is an essential change, and should be resolved by next minor
release.
There really isn't a major learning curve here.
Original comment by tablatronics
on 10 Sep 2012 at 12:54
This needs to be addressed.
How to enable activate for includes plugins.
Original comment by tablatronics
on 21 Oct 2012 at 4:05
Original issue reported on code.google.com by
tablatronics
on 16 Jul 2012 at 11:14