Allow modules to be enabled/disabled by using parameters in the URL [#2062511]

Thanks so much for this wonderful application!

It's great that we can add extra project through the UI and the URL. But they don't get enabled.
If I go:

http://simplytest.me/project/filter_harmonizer/7.x-1.x?add[]=ctools&add[]=views

I find that in addition to the module to be simply-tested (filter_harmonizer), CTools and Views indeed get installed.
I'd hoped they would also be auto-enabled (why else would you want to add them?).
But I need to go to the Modules page, admin/modules to do this manually.

Actually, thinking about this more. For projects that contain more than one module, or use a core module that is not enabled by default, we probably need an enable[]=... parameter, unless you want to enable all modules in the project by default.
Like so:

http://simplytest.me/project/filter_harmonizer/7.x-1.x?add[]=ctools&add[]=views&enable[]=views_ui

This way I can add the Views project and then enable the Views and Views UI modules.

Rik

Comments

Comment #0.0

rdeboer

Melbourne

commented 11 August 2013 at 06:48

Issue summary:

View changes

Added request for "enable[]=..." parameter.

Comment #1

klonos

he/him

English

90% Melbourne, Australia - 10% Larissa, Greece

commented 4 September 2013 at 06:33

Title:

Added modules don't get enabled

» Allow modules to be enabled/disabled by using parameters in the URL

I'm mostly facing this issue when testing Views: only the API submodule (views) is enabled after installation and I constantly find myself repeating the steps to enable the Views UI (views_ui). The &enable[]=views_ui proposed by @RdeBoer in the issue summary would be most useful.

To extend his suggestion I'd also want to put a &disable[]=module_name parameter on the table. Most common scenario is when I want to test admin_menu. I constantly find myself visiting the modules page once the installer is done in order to disable the core toolbar (and the overlay) and enable Admin Menu. This has become a very tedious task for me and I'd like to have a way to "automate" it.

PS: changed issue title so it resembles a feature request rather than a bug ;)

Comment #2

patrickd commented 10 September 2013 at 19:36

Status:

Active

» Postponed

The current problem of this issue is that any introduction of new submission features/options would currently drastically increase the complexity of the service.

To clarify what's going on with simplytest.me and how we handle this in future I created #2086033: Relaunching simplytest.me

I'm on it, just give me some time!

thanks :)