Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

initial commit

  • Loading branch information...
commit 6c79918729ab9b41aef1ecf2714489a8a45f933c 0 parents
Miguel Jacq authored
Showing with 174 additions and 0 deletions.
  1. +131 −0 mig5_profiler.info
  2. +27 −0 mig5_profiler.make
  3. +16 −0 mig5_profiler.profile
131 mig5_profiler.info
@@ -0,0 +1,131 @@
+
+; -----------------------------------------------------------------------------
+; Introduction
+; -----------------------------------------------------------------------------
+; Well, this is it! An example Profiler include, showing you how to create your
+; own Install profiles easily. This file uses Drupal's info format, which is
+; very similar to PHP's own ini format, however you can use nested arrays in
+; Drupal's version, which comes in handy for lots of stuff, as you'll see below.
+;
+; "Wait, you said this would be easy, what is all this stuff?"
+;
+; There aren't really any mandatory things here, but if you don't put anything
+; in here, your install profile won't do much. :) Don't get overwhelmed, just
+; go slow and make a few changes here and there till you get the hang of
+; what's happening.
+;
+; I've tried to create examples for every piece of functionality below, but to
+; get a quick breakdown of what's currently available, here's a list of all the
+; possible items:
+;
+; - base
+; - dependencies
+; - nodes
+; - terms
+; - theme
+; - users
+; - variables
+; -----------------------------------------------------------------------------
+
+name = mig5 Profiler Example
+description = An example Install profile that uses Profiler.
+core = 6.x
+theme = chameleon
+
+; -----------------------------------------------------------------------------
+; You could specify this as a base Profiler include by using the following in
+; your own Install profile's Profiler include. Then everything in this file
+; would be merged with your Profiler include:
+; -----------------------------------------------------------------------------
+; base = profiler_example
+
+
+; -----------------------------------------------------------------------------
+; Modules
+; -----------------------------------------------------------------------------
+; List the modules (core, contrib and/or features) to be enabled in the
+; dependencies[] array. Any dependencies of the listed modules will be detected
+; and enabled automatically.
+; -----------------------------------------------------------------------------
+dependencies[] = filter
+dependencies[] = help
+dependencies[] = menu
+dependencies[] = node
+dependencies[] = path
+dependencies[] = system
+dependencies[] = user
+
+; Contrib
+dependencies[] = admin_menu
+dependencies[] = imageapi
+dependencies[] = imagecache
+dependencies[] = token
+dependencies[] = content
+dependencies[] = filefield
+dependencies[] = imagefield
+dependencies[] = number
+dependencies[] = optionwidgets
+dependencies[] = text
+dependencies[] = views
+dependencies[] = features
+dependencies[] = pathauto
+
+; -----------------------------------------------------------------------------
+; Users
+; -----------------------------------------------------------------------------
+; One other thing to note here is that there's this (handy) quirk in Drupal's
+; install API in that you can bypass the configuration form during installation
+; (where you'd normally set up user 1 credentials and the site name and such).
+; To do this you need to specify credentials for user 1 and also specify the
+; site name and site email variables (@see Variables below).
+; -----------------------------------------------------------------------------
+
+users[superduper][uid] = 1
+users[superduper][name] = admin
+users[superduper][mail] = mig@mig5.net
+users[superduper][roles] = Admin,Publisher
+users[superduper][status] = 1
+
+users[siteadmin][uid] = 2
+users[siteadmin][name] = siteadmin
+users[siteadmin][mail] = changeme@example.com
+users[siteadmin][roles] = Admin,Publisher
+users[siteadmin][status] = 1
+
+; -----------------------------------------------------------------------------
+; Variables
+; -----------------------------------------------------------------------------
+; These variables should be pretty self explanatory, as they are just an array
+; of key value pairs for items in the variable table. Nested arrays also can
+; crop up here, since variables can be arrays.
+;
+; Also, make note of the site_name and site_mail variables below. These
+; variables need to be set if you want to bypass the Configuration form during
+; installation (@see Users for more information on how this is accomplished).
+; -----------------------------------------------------------------------------
+variables[site_name] = Profiler Example
+variables[site_mail] = testing@testing
+
+variables[site_footer] = Profiler Example
+variables[site_frontpage] = node/1
+variables[theme_settings][toggle_node_info_page] = 0
+
+; You may also want to set the clean url variable if you don't need clean urls.
+; Since we bypassed the configuration screen, it is enabled by default, so to
+; disable it you'll want to uncomment this line:
+; variables[clean_url] = 0
+
+; -----------------------------------------------------------------------------
+; Nodes
+; -----------------------------------------------------------------------------
+nodes[front][type] = page
+nodes[front][title] = Isn't Profiler nifty?
+nodes[front][uid] = 2
+nodes[front][body] = <p>Donec vel ipsum elit. In rutrum, ante at fringilla pharetra, mi justo fermentum risus; eget commodo est mi lobortis augue. Proin fringilla malesuada semper. Ut velit sapien, condimentum vel faucibus ut, aliquam quis dui? Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Vivamus vulputate fringilla enim, non convallis nibh lacinia at. Etiam fermentum, lectus ac sagittis volutpat, est augue tincidunt mi, et consectetur orci nisi sit amet sapien. Ut nisi nunc, molestie quis sollicitudin at, dignissim eget nisl? Sed vitae sem lectus. Curabitur viverra laoreet magna. Sed eget sapien tellus, eu tempor purus. Proin dignissim, lacus vitae venenatis porttitor, justo libero rhoncus felis, nec dictum nisl mi vitae nisi. Maecenas tincidunt eros at turpis sollicitudin nec viverra enim condimentum. Sed nec enim justo. In tristique risus dui; ac egestas mi. Proin at arcu sed enim eleifend ornare eu at arcu. Curabitur ullamcorper, ipsum eu imperdiet pharetra, mauris lorem hendrerit metus, in consectetur mauris est iaculis eros. Quisque euismod hendrerit metus ullamcorper tempus! Cras gravida ornare arcu vitae commodo. In hac habitasse platea turpis duis.</p>
+
+; Information added by drupal.org packaging script on 2011-08-15
+version = "6.x-2.0"
+core = "6.x"
+project = "mig5_example"
+datestamp = "1313419319"
+
27 mig5_profiler.make
@@ -0,0 +1,27 @@
+core = 6.x
+api = 2
+
+; Contrib
+projects[admin_menu] = "1.8"
+
+projects[imageapi] = "1.10"
+
+projects[imagecache] = "2.0-beta12"
+
+projects[token] = "1.16"
+
+projects[cck] = "2.9"
+
+projects[filefield] = "3.10"
+
+projects[imagefield] = "3.10"
+
+projects[views] = "2.12"
+
+projects[features] = "1.1"
+
+projects[pathauto] = "1.5"
+
+libraries[profiler][download][type] = "get"
+libraries[profiler][download][url] = "http://ftp.drupal.org/files/projects/profiler-6.x-2.0-beta1.tar.gz"
+
16 mig5_profiler.profile
@@ -0,0 +1,16 @@
+<?php
+
+/**
+ * @file
+ *
+ * An example Install profile that uses Profiler. To create your own Install
+ * profile, copy the directory that this file resides in, and rename all files
+ * and directories, replacing profiler_example with the machine name of your
+ * install profile. Then do a find and replace in this file to replace all
+ * instances of profiler_example with the machine name of your profile. Edit the
+ * renamed profiler_example.info file to your taste, and presto-change-o,
+ * you've got yourself an install profile!
+ */
+
+!function_exists('profiler_v2') ? require_once('libraries/profiler/profiler.inc') : FALSE;
+profiler_v2('mig5_profiler');
Please sign in to comment.
Something went wrong with that request. Please try again.