Closed (outdated)
Project:
Drupal core ideas
Component:
Idea
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
15 May 2007 at 23:26 UTC
Updated:
27 Dec 2022 at 05:51 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dmitrig01 commentedKeeping up with head, and removing cruft
Comment #2
RobRoy commentedThink we'll want some Doxygen and inline comments to space out those functions at the bottom.
Comment #3
dmitrig01 commentedwell, here are some comments
Comment #4
dmitrig01 commentedAnd the .profile file (also has even more comments :) )
Comment #5
ChrisKennedy commentedI like the concept.
Just on visual inspection:
* Tons of coding style errors - spacing, comments, etc. (http://drupal.org/node/318)
* A lot of interface strings are not currently translatable, such as in single_user_blog_profile_details() for example.
* Your comment says "Disable clean URLs" but it's actually saving the value, which could either enable or disable clean URLs.
* It looks like you don't have blog.module enabled by default? I'd add contact.module too.
I will get around to testing this eventually. It would be easier to do so if you posted a true patch against CVS (http://drupal.org/patch/create) though.
Comment #6
drewish commentedi don't think it makes any sense to enable the blog.module, the defined node types do a better job for a single user blog site.
i cleaned up some coding issues and comments. i think rather than using the site email as the admin password we should let them provide a separate email and password.
Comment #7
drewish commentedhere's the profile
Comment #8
dami commentedIMHO, this is more suitable for a contrib profile. We could throw in a more blog-centric theme (e.g. remove the "username's blog" link), comment_info module (maybe it will go into d6 core?), archive, blogroll etc....
Comment #9
ChrisKennedy commentedcomment_info was basically added to core earlier today: http://drupal.org/cvs?commit=67770
Comment #10
dmitrig01 commentedComment #11
drewish commentedi don't think this is ready for prime time yet. it really needs to have some more work done on the account creation stuff. the site wide email shouldn't be used as the admin account, they serve different purposes. the user should be prompted for an admin and user email and separate passwords.
Comment #12
mfer commentedagreed with derwish
Comment #13
ChrisKennedy commentedhttp://support.bryght.com/install-profiles/basic has some good stuff to consider:
From Configuration:
Comment #14
catchMore core install profiles would be great, but not in D6 at this stage.
Comment #15
gábor hojtsyActually, Dries just posted to the development mailing list, that if profiles emerge "in a day or two" (ie really quick solutions with small teams working together), new "core modules only" profiles would be accepted still.
Looking at the patch, some comments:
- name the tags profile "Tags", not "Categories"
- do not name the blog type 'blog', as this is the same type used by blog module... name it 'blogpost' or 'blog_post'
- the current installer helps people set the same email for site and admin, this profile disallows it
- there is a var_dump() in there :)
- the install profiles API changed a bit since this was created
Comment #17
dami commentedIt's mostly the form api changes that break the patch. It should be easy to fix. I will do it if I have time tonight and nobody hasn't done it by then. But exactly what customization/functionality should be included is still up for discussion.
Comment #18
dami commentedJust corrected errors due to form api and install profile api changes. Didn't touch much on anything else, except for
1 assign 'blog poster' to 'authenticated user role' and grant permissions.
2 Added a 'single-user-blog-setup' to task list. And changed output to drupal_set_message after the said step finished.
3 Other Suggestions from Gabor:
1) Changed 'Categories' to 'Tag'
2) Changed 'blog' type to 'blogpost'
Pieces missing:
1 Set same email for site and admin
2 A new welcome page different than the default one.
3. ...
Writing installation profile is new to me, hope my changes is in the right direction.
Comment #19
robloachAdded site mission statement....
I tested it out and it's skipping the Single User Blog Setup step.
Comment #20
dami commentedIt has been almost a month since my last patch, so can't remember exactly what the steps are... but I think the "Single User Blog Setup" is not skipped, it's still get to run and what's missing is an explicit pause and "Continue to next step" page.
Also, just noticed a related issue has been created as a GHOP task at:
http://drupal.org/node/197305
Comment #21
add1sun commentedJust a quick note that the GHOP one is not limited to core and is specifically designed to use contrib. The work done on that project will be added to CVS and be used as the starting block for a more full-featured contrib blogging install profile.
Comment #22
Bevan commentedNot sure if this is something that's already been considered discussed or even completed here, but if not: Offer some vocabularies by default
Comment #23
gábor hojtsyNow goes to Drupal 7, it was not ready in time.
Comment #24
mcrittenden commentedAny chance of this still making it into D7?
Comment #25
patcon commentedAgreed. This is where Wordpress excels, so this is where Drupal should go :)
Comment #26
catchComment #27
aschiwi commentedHere's a first shot at a patch since the patches in this thread are from Drupal 6.
Basically it's a copy of the Standard profile, but using some of the stuff from the patches above (blog post content type name). I guess next steps would be to talk about what the profile needs to be useful in core?
Comment #34
dpiComment #42
quietone commented@dmitrig01, thank you for the idea. This looks like it should be in the ideas project, moving now.
However, the blog module was removed from Drupal 8. https://www.drupal.org/node/2116417.
There is a recent demo profile, demo_umami, that was added in Drupal 8.6.x. https://www.drupal.org/node/2937365
Therefor, I am closing this as outdated.