Well, the default profile is nice, but web n00bs might have some trouble with it. This profile is meant to be a simple blogging platform.
It is almost complete, and just needs a small amount of work.
There are two more things that need to be done:
The permissions for user #2,
and
After installation, if you click 'log out', then there is a register button.

Another good thing would be to remove the user login block, and apon installation, tell the user 'to log in, visit $base_url/user

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dmitrig01’s picture

Keeping up with head, and removing cruft

RobRoy’s picture

Think we'll want some Doxygen and inline comments to space out those functions at the bottom.

dmitrig01’s picture

FileSize
2.28 KB

well, here are some comments

dmitrig01’s picture

And the .profile file (also has even more comments :) )

ChrisKennedy’s picture

I 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.

drewish’s picture

i 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.

drewish’s picture

here's the profile

dami’s picture

IMHO, 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....

ChrisKennedy’s picture

comment_info was basically added to core earlier today: http://drupal.org/cvs?commit=67770

dmitrig01’s picture

Status: Needs work » Needs review
drewish’s picture

Status: Needs review » Needs work

i 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.

mfer’s picture

agreed with derwish

ChrisKennedy’s picture

http://support.bryght.com/install-profiles/basic has some good stuff to consider:

From Configuration:

A description of some of the out-of-the-box configuration that is done once you've installed a new site based on this profile. The site has limited customization for a particular style of site, although the basics are closest to perhaps a corporate blog or similar limited interactivity system. Appropriate for various types of content- or data-driven sites.

* a "tags" vocabulary is created and applied to blog, story, and image content types
* a front page Story is posted with the title of "Welcome"
* a default Page type is created titled "About"
* the About page and the Contact form are added to a new Secondary links menu at the top of your theme. The Primary links are left unconfigured for you to modify as you add content and design your site.
* User profiles are configured to include a Full Name, Website, and Interests fields
* The creation of Contributor and Site Admin roles
* Permissions set for all roles. Anonymous and authenticated members can only add comments, while the Contributor role can work with blogs. Site Admins have full access.
* The TinyMCE and Img_Assist plugins are configured with default collections of buttons and settings: a Comment profile for anonymous visitors, a Basic profile for Contributors, and an Advanced profile for Site Admins.

catch’s picture

Title: Get a new install profile into core - single user blog » Single user blog install profile for core
Version: 6.x-dev » 7.x-dev

More core install profiles would be great, but not in D6 at this stage.

Gábor Hojtsy’s picture

Version: 7.x-dev » 6.x-dev
Component: other » install system

Actually, 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

dami’s picture

It'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.

dami’s picture

Just 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.

RobLoach’s picture

Added site mission statement....

variable_set('site_mission', $form_values['site_mission']);

...


    $form['site_information']['site_mission'] = array(
      '#type' => 'textfield',
      '#title' => st('Mission'),
      '#default_value' => variable_get('site_mission', ''),
      '#description' => st('Your site\'s mission statement or focus.'),
      '#weight' => -17,
    );

I tested it out and it's skipping the Single User Blog Setup step.

dami’s picture

It 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

add1sun’s picture

Just 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.

Bevan’s picture

Not sure if this is something that's already been considered discussed or even completed here, but if not: Offer some vocabularies by default

Gábor Hojtsy’s picture

Version: 6.x-dev » 7.x-dev

Now goes to Drupal 7, it was not ready in time.

mcrittenden’s picture

Any chance of this still making it into D7?

patcon’s picture

Agreed. This is where Wordpress excels, so this is where Drupal should go :)

catch’s picture

Version: 7.x-dev » 8.x-dev
aschiwi’s picture

Here'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?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dpi’s picture

Title: Single user blog install profile for core » [ideas] Blogging profile
Version: 8.6.x-dev » 8.8.x-dev
Component: install system » other
Assigned: dmitrig01 » Unassigned
Issue summary: View changes

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Project: Drupal core » Drupal core ideas
Version: 10.1.x-dev »
Component: other » Idea
Status: Needs work » Closed (outdated)

@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.