From 07d0f26f9ccdd2499226459b7fe29d39c7d7df41 Mon Sep 17 00:00:00 2001
From: Drew Reece <drudus@gmail.com>
Date: Thu, 7 Apr 2011 17:25:12 +0100
Subject: [PATCH] Issue #1114772: Adding help for Views exports.

---
 help/ctools.help.ini          |    6 +++++
 help/export-views-bulk.html   |   44 +++++++++++++++++++++++++++++++++++++++++
 help/export-views-single.html |   39 ++++++++++++++++++++++++++++++++++++
 3 files changed, 89 insertions(+), 0 deletions(-)
 create mode 100644 help/export-views-bulk.html
 create mode 100644 help/export-views-single.html

diff --git a/help/ctools.help.ini b/help/ctools.help.ini
index fcb121b..1560b76 100644
--- a/help/ctools.help.ini
+++ b/help/ctools.help.ini
@@ -57,6 +57,12 @@ title = Exportable objects tool
 [export-ui]
 title = Exportable objects UI creator
 
+[export-views-single]
+title = Export and importing a view
+
+[export-views-bulk]
+title = Export views to a module
+
 [form]
 title = Form tools
 
diff --git a/help/export-views-bulk.html b/help/export-views-bulk.html
new file mode 100644
index 0000000..8450946
--- /dev/null
+++ b/help/export-views-bulk.html
@@ -0,0 +1,44 @@
+This documentation focuses on the Chaos tools bulk export and version control functionality of the Chaos tools module.  The following steps document how to export multiple views at once and create a module from the exported code that will allow you to revert any subsequent changes to your views.
+
+Assumptions:
+- You have views you want to bulk export; we'll call them <em>myView1</em> and <em>myView2</em>
+- You know how to install and enable a module
+
+
+<ol>
+  <li><h3>Modules you will need</h3>
+    <p>Install <a href="http://drupal.org/project/views" target="_blank">Views</a> and  <a href="http://drupal.org/project/ctools" target="_blank">Chaos tools</a> and <a href="base_url:admin/modules" target="_blank">enable</a> the following modules: Views, Views UI, Chaos tools, Bulk Export</p>
+  </li>
+  <li><h3>Evaluate the current state of views</h3>
+    <p>Navigate to the <a href="base_url:admin/structure/views" target="_blank">Views Administration page</a>. You should have operations for <em> Edit | Disable | Delete | Clone | Export </em> next to <em>myView1</em> and <em>myView2</em>.  Once we're done, "Delete" will become "Revert"!</p>
+  </li>
+  <li><h3>Bulk export your views</h3>
+    <ol>
+      <li>Click <strong>Structure</strong> > <strong>Bulk Exporter</strong> to navigate to the <a href="base_url:admin/structure/bulk-export" target="_blank">Bulk Exporter page</a> to export <em>myView1</em> and <em>myView2</em>.</li>
+      <li>Check the boxes to the left of <em>myView1</em> and <em>myView2</em></li>
+      <li>Choose a module name: my_views</li>
+      <li>Click <strong>Export</strong></li>
+    </ol>
+  </li>
+  <li><h3>Create a module from the exported views</h3>
+    <p>The results of the export should now be in front of you.  Specifically, the results page should be composed of three code-containing regions. This code and the following steps are all you need to create a module that will allow you to revert your views to the state they were in when you exported them.
+    <ol>
+      <li>Create a directory called <em>my_views</em> within your sites/all/modules directory.</li>
+      <li>Create the following files, paste in the appropriate code, and place them into the <em>my_views</em> directory:</li>
+        <ul>
+          <li>my_views.info</li>
+          <li>my_views.module (ensure &lt;?php tags are at the beginning of this file!)</li>
+          <li>my_views.views_default.inc (ensure &lt;?php tags are at the beginning of this file!)</li>
+        </ul>
+    </ol>
+  </li>
+  <li><h3>Clear the cache</h3>
+    <p>Just to be safe.  Navigate to the <a href="base_url:admin/config/development/performance" target="_blank">Performance Administration page</a> and <strong>Clear cached data</strong>.</p>
+  </li>
+  <li><h3>Enable the module containing exported views</h3>
+    <p>Navigate to the <a href="base_url:admin/modules" target="_blank">Modules Administration page</a> and enable <em>my_views export module</em>.  <strong>Save</strong>.</p>
+  </li>
+  <li><h3>Verify presence of reversion option for exported views</h3>
+    <p>Navigate to the <a href="base_url:admin/build/views" target="_blank">Views Administration page</a>.  The operations for <em>myView1</em> and <em>myView2</em> should now read <em>Edit | Export | Clone | Revert</em>.  Congratulations, you now have version control in place for your exported views!</p>
+  </li>
+</ol>
diff --git a/help/export-views-single.html b/help/export-views-single.html
new file mode 100644
index 0000000..6380194
--- /dev/null
+++ b/help/export-views-single.html
@@ -0,0 +1,39 @@
+This documentation focuses on the Chaos tools import and export feature.  The following steps document how to export a single view, then re-import the view, potentially to a different site.
+
+Assumptions:
+- You have a view you want to export; we'll call it <em>myView</em>
+- You know how to install and enable a module
+
+<h3>Modules you will need</h3>
+<p>Install <a href="http://drupal.org/project/views" target="_blank">Views</a> and  <a href="http://drupal.org/project/ctools" target="_blank">Chaos tools</a> and <a href="base_url:admin/modules" target="_blank">enable</a> the following modules: Views, Views UI, Chaos tools, Bulk Export</p>
+
+<ol>
+<h2>Exporting views</h2>
+
+<li><h3>Export the view</h3>
+<p>Navigate to the <a href="base_url:admin/structure/views" target="_blank">Views Administration page</a>. You should have operations for <em> Edit | Disable | Delete | Clone | Export </em> next to <em>myView</em>.
+  <ol>
+    <li>Click <strong>Export</strong> on the operation for <em>myView</em>.</li>
+    <li>The results of the export should now be in front of you.  Specifically, the results page should be composed of one code-containing region. This code and the following steps are all you need to re-create <em>myView</em> to the state it was in when you exported it.</li>
+    <li>Copy the text to a file for safe keeping.</li>
+    </ol>
+  </li>
+</ol>
+
+<ol>
+  <h2>Importing views</h2>
+  <li><h3>Import your view</h3>
+  <p>Navigate to the <a href="base_url:admin/build/views" target="_blank">Views Administration page</a> and click <em>Import</em>.</p>
+  <ol>
+    <li>Paste in the code from the text file created from the previous export of <em>myView</em>.</li>
+    <li>Click <strong>Import</strong>.</li>
+  </ol>
+
+  <li><h3>Clear the cache</h3>
+    <p>Just to be safe.  Navigate to the <a href="base_url:admin/config/development/performance" target="_blank">Performance Administration page</a> and <strong>Clear cached data</strong>.</p>
+  </li>
+
+  <li><h3>Verify the view</h3>
+    <p>Return to <a href="base_url:admin/build/views" target="_blank">Views Administration page</a> to verify the view has imported.  Congratulations, you just imported your exported view!</p>
+  </li>
+</ol>
\ No newline at end of file
-- 
1.7.3.1

