| Project: | Drupal core |
| Version: | 7.x-dev |
| Component: | install system |
| Category: | task |
| Priority: | normal |
| Assigned: | Xano |
| Status: | closed (duplicate) |
Issue Summary
I think we should add more dummy content to the default installation profile - participants at the UMN usability testing asked for this, and it's been mentioned elsewhere. I've opened another issue to enable a 'tags' vocabulary by default here: http://drupal.org/node/261869
The main issue with adding dummy content and settings to default.profile however, is that people installing Drupal other than for the first couple of times will have to sit there deleting it before they can get any work done. Attached is a 'Drupal Advanced" profile - which is just the default profile with nearly everything removed, no content types, no optional modules enabled.
Having both a 'default' and 'advanced' profile would be consistent with a lot of desktop software - where you click an advanced option to install a lighter set of options and set up your own preferences. We might want to change 'advanced' to 'minimum' or something.
Attached is a new advanced.profile which should go in profiles/advanced (you'll need to make the folder). I won't make a proper patch until there's been some feedback, but this at least gives an idea what it'd look like. Note that at the moment, this doesn't really remove all that much, but I'm hoping we can add more things to the default profile as time goes on.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| advuserprofile.patch | 3.05 KB | Idle | FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch advuserprofile.patch. | View details | Re-test |
Comments
#1
I like it but dblog imo needs to be there.
#2
I considered leaving dblog but wasn't sure about leaving only one module, that's probably the main candidate for leaving enabled and would be fine with me.
By the way, that patch is completely errant here's the file I meant to upload.
#3
subscribe
#4
I'd support this. It would be a great thing to do. Re-roll and commit? I'm sure we'll be refining this install profile over time.
#5
OK here it is with 'dblog' included. Just noticed that locale gets enabled anyway though, so do we need to add a task at the end to disable it? Leaving at needs work (and still not a patch, not sure how to add folders in cvs).
#6
#7
#8
The rename to something like 'minimum' is a good idea I think. It's not advanced in the same way that desktop applications have advanced modes (in fact it is frequently the opposite as it often means enabling more features). 'Minimum' describes what the install profile actually is.
#9
Here it is as minimum.profile - and with locale disabled in minimum_profile_tasks()
Might need some more tweaking, but back to review to get some feedback.
#10
It looks to me as it is too minimal. Wasn't the goal to create some dummy data and to setup a vocabulary?
#11
Ah, I get it now. The idea is to add stuff to the default profile, and to keep the minimum profile the minimum profile. Makes sense.
#12
I'd suggest two changes though:
1. Let's rename 'minimum' to 'expert' as that better communicates the target audience and looks at it from an end-user point of view.
2. Let's add an entry to CHANGELOG.txt.
If you do a re-roll, I'll commit it the same day. ;)
#13
How can I resist an offer like that :)
Here's expert.profile as a .txt file (not sure how to roll a new folder into a patch), and a patch for CHANGELOG.txt
I'm still not happy with locale.module being enabled then immediately disabled again afterwards, but don't see a way 'round this the way profiles currently work.
#14
Committed to CVS HEAD.
This opens the doors to add more things to the default profile and/or to create additional install profiles for core. It also helps set an example for more install profiles in the contributed modules repository.
#15
Automatically closed -- issue fixed for two weeks with no activity.
#16
I would change the profile names to the following:
#17
I'd be fine with such a change. It also mirrors how desktop software does this.
#18
Here's the patch that applies the changes as mentioned in #16.
#19
Patch failed to apply. More information can be found at http://testing.drupal.org/node/14338. If you need help with creating patches please look at http://drupal.org/patch/create
#20
I justed tried patching this version against the latest dev and it works. I couldn't figure out how to let the patch delete the 'Expert' profile though.
#21
#22
Kaaskop wanted to know if this patch still applies cleanly to HEAD, and yes it does, so webchick here we go :)
#23
If we're changing the name, we ought to change the function names to match.
#24
#25
I attached a zipped version of the modified
/profilesdirectory. Since I cannot create a patch for removed and added files somebody else has got to do this.#26
Here's the patch for HEAD that adds and deletes files.
#27
#28
The last submitted patch failed testing.
#29
Could somebody update that last patch? It's my code, but I'm no good at creating patches that add or delete files.
#30
I can confirm this patch still works with the latest HEAD. I think the patch failed automatic testing due to known problems with HEAD a few days ago.
#31
Somehow people (Keith? :-P ) started working on a similar issue: #297181: Modify descriptions on initial installation form.. Are going through with this one or do we let it be like it is now?
#32
Oops. I was indeed unaware of this issue, or would have tried to take it into account when changing those names and descriptions in the other issue. I haven't read through this issue yet, so I'm not sure how, of if, it fits in. I'll read through it though.
#33
Fixed in another issue already.