User login

Steps to Follow on All Agaric Sites (default configuration destined for an installation profile)

Searched words: 
standard steps to incorporate into an installation profile Drupal configuration for all sites install checklist

This document is a part (soon to be an automated part) of Agaric's ultimate site deployment checklist.)

Make automatic with a custom Agaric installation profile

  • Set the File system path to sites/default/files: example.org/admin/settings/file-system
  • Enable clean URLs: example.org/admin/settings/clean-urls
  • Set Anonymous user to Visitor: example.org/admin/settings/site-information
  • Add a new role, admin: example.org/admin/user/roles
  • Edit this role's permissions: example.org/admin/user/access/3
    • administer blocks
    • administer comments
    • post comments
    • post comments without approval
    • administer menu
    • administer content types
    • administer nodes
    • create page content (are all create/edit permissions implied by administer nodes?)
    • create story content
    • edit page content
    • edit story content
    • revert revisions
    • view revisions
    • access administration pages
    • administer site configuration
    • administer taxonomy
    • access user profiles
    • administer users
    • change own username
  • Enable these modules (already part of the agaric_basic_5 codebase)
    • Administration Menu
    • CCK:
      • Content
      • Content Copy
      • Date
      • Date Copy
      • Fieldgroup
      • Node Reference
      • Number
      • Option Widgets
      • Text
      • User Reference
    • Core:
      • Blog
      • Blog API
      • Path
      • Search
      • Statistics
      • Tracker
      • Upload
    • Image
    • Image Gallery
    • BUEditor
    • CVS Deploy
    • Date API
    • LoginToboggan
    • Token
    • Update status
    • ASCII art CAPTCHA
    • CAPTCHA
    • Edit term
    • Views
    • Views RSS
    • Views Theme Wizard
    • Views UI
    • Drush
    • drush Package Manager
    • drush Package Manager CVS Support

    Needs configuration when enabled:
    Pathauto
    Admin Role

    Possibly disable:
    Color

Probably not so easy to put in an installation profile

  • Site name, first site information setting: example.org/admin/settings/site-information
  • E-mail address to the format admin at example.org: example.org/admin/settings/site-information

Resolution

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Internal paths in single or double quotes, written as "internal:node/99", for example, are replaced with the appropriate absolute URL or path. Paths to files in single or double quotes, written as "files:somefile.ext", for example, are replaced with the appropriate URL that can be used to download the file.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Syntax highlight code surrounded by the {syntaxhighlighter SPEC}...{/syntaxhighlighter} tags, where SPEC is a Syntaxhighlighter options string or "class="OPTIONS" title="the title".
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.