Changeset 566
- Timestamp:
- 08/09/09 01:43:29 (4 years ago)
- Location:
- enpraxis.educommons/trunk/enpraxis/educommons
- Files:
-
- 32 edited
-
CHANGES.txt (modified) (1 diff)
-
IMSContentPackaging.txt (modified) (1 diff)
-
INSTALL.txt (modified) (1 diff)
-
LOCALIZATION.txt (modified) (5 diffs)
-
MIGRATION.txt (modified) (6 diffs)
-
SETUP.txt (modified) (2 diffs)
-
SeleniumRCTests.txt (modified) (2 diffs)
-
browser/templates/faq_view.pt (modified) (1 diff)
-
docs/CHANGES.html (modified) (2 diffs)
-
docs/CHANGES.pdf (modified) (previous)
-
docs/IMSContentPackaging.html (modified) (2 diffs)
-
docs/IMSContentPackaging.pdf (modified) (previous)
-
docs/INSTALL.html (modified) (2 diffs)
-
docs/INSTALL.pdf (modified) (previous)
-
docs/LOCALIZATION.html (modified) (6 diffs)
-
docs/LOCALIZATION.pdf (modified) (previous)
-
docs/MIGRATION.html (modified) (6 diffs)
-
docs/MIGRATION.pdf (modified) (previous)
-
docs/MIGRATIONS_OLD.html (modified) (1 diff)
-
docs/MIGRATIONS_OLD.pdf (modified) (previous)
-
docs/PORTLETS.html (modified) (1 diff)
-
docs/PORTLETS.pdf (modified) (previous)
-
docs/SETUP.html (modified) (3 diffs)
-
docs/SeleniumRCTests.html (modified) (4 diffs)
-
docs/src/CHANGES.txt (modified) (1 diff)
-
docs/src/LOCALIZATION.txt (modified) (4 diffs)
-
docs/src/SETUP.txt (modified) (2 diffs)
-
docs/src/SeleniumRCTests.txt (modified) (1 diff)
-
tests/seleniumtests/QA.py (modified) (3 diffs)
-
tests/seleniumtests/__init__.py (modified) (1 diff)
-
tests/seleniumtests/accountsLogin.py (modified) (1 diff)
-
tests/seleniumtests/addNewUsersAll.py (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
enpraxis.educommons/trunk/enpraxis/educommons/CHANGES.txt
r8 r566 1 ======================== 2 Changes in version 3.2.1 3 ======================== 4 Installers 5 Simplified installation have been added, including buildout scripts and Windows installers. 6 Expanded IMS Import 7 eduCommons can now import from IMS Common Cartridge, IMS Content Package, MIT course downloads, Blackboard IMS, WebCT Vista, WebCT 6.1/7.0, and Moodle Backups. 8 Improved IMS Export 9 eduCommons can now export to IMS Common Cartridge, IMS Content Package, and IMS Package for Moodle. 10 WordPress Import/Export 11 Support has been added to import pages from a WordPress site as well as export eduCommons content directly to WordPress pages. 12 Static Site 13 It is now possible to publish an entire eduCommons site to static HTML. 14 Expanded RSS 15 Additional RSS have been added to create an RSS feed of most recent items. 16 OIA-pmh and Improved Metadata 17 Support has been added for additional metadata in rdf/rss views as well as OAI/pmh. 18 OpenSearch Support 19 Support has been added for OpenSearch, including the Firefox OpenSearch widget which allows a search of a specific eduCommons site directly from the browser's search window. 20 1 21 ======================== 2 22 Changes in version 3.1.0 -
enpraxis.educommons/trunk/enpraxis/educommons/IMSContentPackaging.txt
r522 r566 1 IMS Content Packaging and eduCommons 3.2.1 1 IMS Content Packaging and eduCommons 3.2.1-rc2 2 2 ================================================ 3 3 4 4 This document details how to write IMS Content packages that are compatible with 5 eduCommons 3.2.1 .5 eduCommons 3.2.1-rc2. 6 6 7 7 eduCommons uses version 1.2 of the IMS Content Packaging Specification. XML Schemas -
enpraxis.educommons/trunk/enpraxis/educommons/INSTALL.txt
r522 r566 1 1 ================================== 2 Installing eduCommons 3.2.1 2 Installing eduCommons 3.2.1-rc2 3 3 ================================== 4 4 5 Download the eduCommons 3.2.1 release, available at:5 Download the eduCommons 3.2.1-rc2 release, available at: 6 6 7 7 :: -
enpraxis.educommons/trunk/enpraxis/educommons/LOCALIZATION.txt
r522 r566 18 18 19 19 ======================================== 20 Localization with eduCommons 3.2.1 20 Localization with eduCommons 3.2.1-rc2 21 21 ======================================== 22 22 … … 37 37 less time consuming because most of the translation work has already been done in Plone. 38 38 39 There are about 4 00 strings needed for a translation of eduCommons (compared to about 1600 strings39 There are about 470 strings needed for a translation of eduCommons (compared to about 1600 strings 40 40 for a Plone translation). Some of these are sentences or paragraphs, but the major part are one or 41 41 two words. These strings are scattered around in Plone, for example in page templates. Other items 42 42 to translate are widget labels, and workflow states. All those strings are collected in master 43 files. Currently eduCommons contains six.pot files. Each language requires its own .po files that43 files. These are called .pot files. Each language requires its own .po files that 44 44 corresponds to the strings or message ids declared in the .pot files. The .pot is the blueprint for 45 45 the .po files. … … 82 82 this translation compared to not getting one at all :) 83 83 84 4. Here is a link to the most recent translation files available for eduCommons (plone.po and 85 eduCommons.po). Remember, unless there is already an existing translation available, you need 86 to grab the .pot files. 87 88 http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/ 89 90 Here are links to the latest translations for each of the eduCommons products on the Plone 91 Collective site (these links may change, so check back for the most accurate information): 92 93 http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/ 94 95 http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/ 96 97 http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/ 98 99 http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/ 84 4. Each product in eduCommons has .po files located in the locales directory. We have combined 85 all these files in a single location of ease of translation. It can be accessed here: 86 http://educommons.com/localization/localization-files.zip 87 If you wish to translate a language for which we do not currently have translation files, 88 please contact us at info [at] educommons [dot] com. 100 89 101 90 … … 139 128 ${number} TRANSLATION. 140 129 141 9. Keep translating (but take breaks, this isn't done in one sitting - it's repet etive (but130 9. Keep translating (but take breaks, this isn't done in one sitting - it's repetitive (but 142 131 rewarding) work. After you have translated all of plone.pot, you should start on eduCommons.pot. 143 132 Don't worry, you have already completed the biggest part. … … 154 143 works, you can get an account with Plone (Here's how to request write access to the Collective.) 155 144 and maintain the files in SVN yourself (see next section). If not, no problem, just e-mail your 156 translation to us at eduCommons [at] cosl [dot] usu [dot] edu, and we will add it for you and put it into the145 translation to us at info [at] educommons [dot] com, and we will add it for you and put it into the 157 146 eduCommons distribution in the next release. We will also add you to our our `eduCommons 158 Localization Team page . <./educommons-localization-team>`__147 Localization Team page, here: http://educommons.com/documentation/how-to/educommons-localization-team 159 148 160 149 13. Please check on your translations periodically to keep them updated as new versions are 161 released. A quick findfor "" will reveal any new or missing stings that need to be translated.150 released. A quick search for "" will reveal any new or missing stings that need to be translated. 162 151 163 152 14. If you have other questions or about contributing a translation to eduCommons please contact 164 us at educommons [at] cosl [dot] usu [dot] edu. Thank you for you help!153 us at info [at] educommons [dot] com. Thank you for you help! 165 154 -
enpraxis.educommons/trunk/enpraxis/educommons/MIGRATION.txt
r522 r566 1 1 =================================== 2 Migrating to eduCommons 3.2.1 2 Migrating to eduCommons 3.2.1-rc2 3 3 =================================== 4 4 … … 13 13 14 14 15 Migration of eduCommons 3.1.1-final to 3.2.1 15 Migration of eduCommons 3.1.1-final to 3.2.1-rc2 16 16 -------------------------------------------------- 17 17 18 The migration eduCommons from version 3.1.1-final to version 3.2.1 18 The migration eduCommons from version 3.1.1-final to version 3.2.1-rc2 19 19 includes the following: 20 20 21 21 1. Pre-migration of Data.fs in version 3.1.1-final 22 22 23 2. Movement of Data.fs file to a new 3.2.1 instance23 2. Movement of Data.fs file to a new 3.2.1-rc2 instance 24 24 25 3. Migration to the eduCommons 3.2.1 instance25 3. Migration to the eduCommons 3.2.1-rc2 instance 26 26 27 4. Export/Import of eduCommons site to a new 3.2.1 instance27 4. Export/Import of eduCommons site to a new 3.2.1-rc2 instance 28 28 29 29 5. Final steps … … 70 70 71 71 72 Movement of Data.fs file to a new 3.2.1 instance72 Movement of Data.fs file to a new 3.2.1-rc2 instance 73 73 ------------------------------------------------------ 74 74 75 75 For this step, you will move the Data.fs file from the old instance to 76 the new instance. First of all, install an eduCommons-3.2.1 76 the new instance. First of all, install an eduCommons-3.2.1-rc2 77 77 instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 78 78 copy the Data.fs file from the var directory of the old site to the … … 83 83 84 84 85 Migration to eduCommons 3.2.1 instance85 Migration to eduCommons 3.2.1-rc2 instance 86 86 ------------------------------------------------ 87 eduCommons 3.2.1 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation:87 eduCommons 3.2.1-rc2 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1-rc2. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation: 88 88 89 89 1. Navigate to the root of your ZMI instance and create a new eduCommons site called eduCommons321 90 2. Open your new 3.2.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)90 2. Open your new 3.2.1-rc2 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 91 91 3. Navigate to portal_setup 92 92 4. Press the 'Upgrades' tab … … 96 96 97 97 98 Export/Import of eduCommons site to a new 3.2.1 instance98 Export/Import of eduCommons site to a new 3.2.1-rc2 instance 99 99 -------------------------------------------------------------- 100 100 … … 102 102 103 103 1. Navigate to the root of your ZMI instance 104 2. Select the checkbox next to your new 3.2.1 eduCommons site104 2. Select the checkbox next to your new 3.2.1-rc2 eduCommons site 105 105 3. Press Import/Export 106 106 4. If your production environment is on the same server as your migration environment, choose 'Save file to server', else -
enpraxis.educommons/trunk/enpraxis/educommons/SETUP.txt
r522 r566 78 78 The *Site Title* and *Site Description* fields should contain values that were initially set during the installation process. If you want to change these fields, you can do so here. The *Site Title* field is referred to throughout the site. It is important to remember that eduCommons will only change the portal title on a page when a template is applied. If you change this setting here, it will be necessary to also change it throughout the site, or to reapply templates that refer to it. 79 79 80 eduCommons provides a number of settings that can be used with your site. The *Site 'From" Name* and *Site 'From' Address* are already discussed in the section titled `Mail Settings`_.81 82 80 *JavaScript for web statistics support* is an area for enabling web statistics support from external providers (for e.g. Google Analytics). Paste the code snippets provided. It will be included in the rendered HTML as entered near the end of the page. 83 81 84 The *Default Language* setting is discussed in the next section.85 82 86 83 Setting the Default Language for your Site … … 141 138 There are other options that are available if you find yourself needing extra functionality. The `development site`_ for eduCommons can be used to check to see if your bug is being or has been fixed, or to see what features have been scheduled for development on the `roadmap`_. There are also `forums`_ where you can post issues and get responses from the development team and/or other eduCommons users. 142 139 143 .. _development site: http:// cosl.usu.edu/trac144 .. _roadmap: http:// cosl.usu.edu/trac/roadmap145 .. _forums: http:// cosl.usu.edu/forums140 .. _development site: http://educommons.com/dev 141 .. _roadmap: http://educommons.com/dev/roadmap 142 .. _forums: http://educommons.com/support-forums 146 143 147 144 eduCommons depends on community support, and participation in the user community/development process is both appreciated and welcome. 148 145 149 For additional documentation, including updates to these setup instructions, please visit: http:// cosl.usu.edu/projects/educommons/documentation, specifically http://cosl.usu.edu/projects/educommons/documentation/how-to146 For additional documentation, including updates to these setup instructions, please visit: http://educommons.com/documentation -
enpraxis.educommons/trunk/enpraxis/educommons/SeleniumRCTests.txt
r522 r566 1 1 ========================================= 2 eduCommons 3.2.1 SeleniumRC Testing2 eduCommons 3.2.1-rc2 SeleniumRC Testing 3 3 ========================================= 4 4 … … 53 53 Role Username Password 54 54 ==== ========= ========= 55 admin admin admin55 admin/manager admin test1234 56 56 producer producer producer 57 57 reviewer reviewer reviewer 58 qa qa qa58 qa quality quality 59 59 publisher publisher publisher 60 viewer viewer viewer60 viewer viewer viewer 61 61 ======= ========= ========= 62 62 -
enpraxis.educommons/trunk/enpraxis/educommons/browser/templates/faq_view.pt
r564 r566 708 708 cluster and a content staging cluster.</p> 709 709 710 <p>For more information on eduCommons, please contact The Center for Open and Sustainable Learning (<a href="http://cosl.usu.edu/">http://cosl.usu.edu/</a>).</p>710 <p>For more information on eduCommons, please visit <a href="http://educommons.com">http://educommons.com</a>.</p> 711 711 712 712 <p><a href="#TOP">Top</a></p> -
enpraxis.educommons/trunk/enpraxis/educommons/docs/CHANGES.html
r520 r566 12 12 13 13 14 <div class="section" id="changes-in-version-3-2-1"> 15 <h1>Changes in version 3.2.1</h1> 16 <dl class="docutils"> 17 <dt>Installers</dt> 18 <dd>Simplified installation have been added, including buildout scripts and Windows installers.</dd> 19 <dt>Expanded IMS Import</dt> 20 <dd>eduCommons can now import from IMS Common Cartridge, IMS Content Package, MIT course downloads, Blackboard IMS, WebCT Vista, WebCT 6.1/7.0, and Moodle Backups.</dd> 21 <dt>Improved IMS Export</dt> 22 <dd>eduCommons can now export to IMS Common Cartridge, IMS Content Package, and IMS Package for Moodle.</dd> 23 <dt>WordPress Import/Export</dt> 24 <dd>Support has been added to import pages from a WordPress site as well as export eduCommons content directly to WordPress pages.</dd> 25 <dt>Static Site</dt> 26 <dd>It is now possible to publish an entire eduCommons site to static HTML.</dd> 27 <dt>Expanded RSS</dt> 28 <dd>Additional RSS have been added to create an RSS feed of most recent items.</dd> 29 <dt>OIA-pmh and Improved Metadata</dt> 30 <dd>Support has been added for additional metadata in rdf/rss views as well as OAI/pmh.</dd> 31 <dt>OpenSearch Support</dt> 32 <dd>Support has been added for OpenSearch, including the Firefox OpenSearch widget which allows a search of a specific eduCommons site directly from the browser's search window.</dd> 33 </dl> 34 </div> 14 35 <div class="section" id="changes-in-version-3-1-0"> 15 36 <h1>Changes in version 3.1.0</h1> … … 253 274 <hr class="footer" /> 254 275 <a class="reference external" href="CHANGES.txt">View document source</a>. 255 Generated on: 2009-08-0 6 16:49UTC.276 Generated on: 2009-08-09 07:41 UTC. 256 277 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 257 278 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/IMSContentPackaging.html
r520 r566 12 12 13 13 14 <div class="section" id="ims-content-packaging-and-educommons-3-2-1 ">15 <h1>IMS Content Packaging and eduCommons 3.2.1 </h1>14 <div class="section" id="ims-content-packaging-and-educommons-3-2-1-rc2"> 15 <h1>IMS Content Packaging and eduCommons 3.2.1-rc2</h1> 16 16 <p>This document details how to write IMS Content packages that are compatible with 17 eduCommons 3.2.1 .</p>17 eduCommons 3.2.1-rc2.</p> 18 18 <p>eduCommons uses version 1.2 of the IMS Content Packaging Specification. XML Schemas 19 19 for the specification can be found at <a class="reference external" href="http://imsglobal.org/xsd/imscp_v1p2.xsd">http://imsglobal.org/xsd/imscp_v1p2.xsd</a> and … … 475 475 <hr class="footer" /> 476 476 <a class="reference external" href="IMSContentPackaging.txt">View document source</a>. 477 Generated on: 2009-08-0 6 16:49UTC.477 Generated on: 2009-08-09 07:41 UTC. 478 478 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 479 479 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/INSTALL.html
r520 r566 5 5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 6 6 <meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> 7 <title>Installing eduCommons 3.2.1 </title>7 <title>Installing eduCommons 3.2.1-rc2</title> 8 8 <link rel="stylesheet" href="./default.css" type="text/css" /> 9 9 </head> 10 10 <body> 11 <div class="document" id="installing-educommons-3-2-1 ">12 <h1 class="title">Installing eduCommons 3.2.1 </h1>11 <div class="document" id="installing-educommons-3-2-1-rc2"> 12 <h1 class="title">Installing eduCommons 3.2.1-rc2</h1> 13 13 14 <p>Download the eduCommons 3.2.1 release, available at:</p>14 <p>Download the eduCommons 3.2.1-rc2 release, available at:</p> 15 15 <pre class="literal-block"> 16 16 http://sourceforge.net/projects/educommons/files/educommons/eduCommons-3.2.1-final/educommons.buildout-3.2.1-final.tar.gz/download … … 112 112 <hr class="footer" /> 113 113 <a class="reference external" href="INSTALL.txt">View document source</a>. 114 Generated on: 2009-08-0 6 16:49UTC.114 Generated on: 2009-08-09 07:41 UTC. 115 115 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 116 116 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/LOCALIZATION.html
r520 r566 25 25 setting from neutral to the appropriate setting for your instance.</p> 26 26 </div> 27 <div class="section" id="localization-with-educommons-3-2-1 ">28 <h1>Localization with eduCommons 3.2.1 </h1>27 <div class="section" id="localization-with-educommons-3-2-1-rc2"> 28 <h1>Localization with eduCommons 3.2.1-rc2</h1> 29 29 <div class="section" id="overview"> 30 30 <h2>Overview</h2> … … 41 41 translation work, but follows the same process as Plone. Adding an eduCommons translation is much 42 42 less time consuming because most of the translation work has already been done in Plone.</p> 43 <p>There are about 4 00 strings needed for a translation of eduCommons (compared to about 1600 strings43 <p>There are about 470 strings needed for a translation of eduCommons (compared to about 1600 strings 44 44 for a Plone translation). Some of these are sentences or paragraphs, but the major part are one or 45 45 two words. These strings are scattered around in Plone, for example in page templates. Other items 46 46 to translate are widget labels, and workflow states. All those strings are collected in master 47 files. Currently eduCommons contains six.pot files. Each language requires its own .po files that47 files. These are called .pot files. Each language requires its own .po files that 48 48 corresponds to the strings or message ids declared in the .pot files. The .pot is the blueprint for 49 49 the .po files.</p> … … 81 81 language you understand is Italian, and you want to provide a Chinese translation, we prefer 82 82 this translation compared to not getting one at all :)</p> 83 <p>4. Here is a link to the most recent translation files available for eduCommons (plone.po and 84 eduCommons.po). Remember, unless there is already an existing translation available, you need 85 to grab the .pot files.</p> 86 <blockquote> 87 <p><a class="reference external" href="http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/">http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/</a></p> 88 <p>Here are links to the latest translations for each of the eduCommons products on the Plone 89 Collective site (these links may change, so check back for the most accurate information):</p> 90 <p><a class="reference external" href="http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/">http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/</a></p> 91 <p><a class="reference external" href="http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/">http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/</a></p> 92 <p><a class="reference external" href="http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/">http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/</a></p> 93 <p><a class="reference external" href="http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/">http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/</a></p> 94 </blockquote> 83 <p>4. Each product in eduCommons has .po files located in the locales directory. We have combined 84 all these files in a single location of ease of translation. It can be accessed here: 85 <a class="reference external" href="http://educommons.com/localization/localization-files.zip">http://educommons.com/localization/localization-files.zip</a> 86 If you wish to translate a language for which we do not currently have translation files, 87 please contact us at info [at] educommons [dot] com.</p> 95 88 <p>5. Open poEdit or your editor of choice and load the first of the master files. In poEdit 96 89 select File --> Open (for existing .po translation files) or File --> New catalog from POT file. … … 129 122 criteria." The code in the first part should be left as it is, so the translation will look like this: 130 123 ${number} TRANSLATION.</p> 131 <p>9. Keep translating (but take breaks, this isn't done in one sitting - it's repet etive (but124 <p>9. Keep translating (but take breaks, this isn't done in one sitting - it's repetitive (but 132 125 rewarding) work. After you have translated all of plone.pot, you should start on eduCommons.pot. 133 126 Don't worry, you have already completed the biggest part.</p> … … 141 134 works, you can get an account with Plone (Here's how to request write access to the Collective.) 142 135 and maintain the files in SVN yourself (see next section). If not, no problem, just e-mail your 143 translation to us at eduCommons [at] cosl [dot] usu [dot] edu, and we will add it for you and put it into the 144 eduCommons distribution in the next release. We will also add you to our our <a class="reference external" href="./educommons-localization-team">eduCommons 145 Localization Team page.</a></p> 136 translation to us at info [at] educommons [dot] com, and we will add it for you and put it into the 137 eduCommons distribution in the next release. We will also add you to our our <a href="#id1"><span class="problematic" id="id2">`</span></a>eduCommons 138 Localization Team page, here: <a class="reference external" href="http://educommons.com/documentation/how-to/educommons-localization-team">http://educommons.com/documentation/how-to/educommons-localization-team</a></p> 139 <div class="system-message" id="id1"> 140 <p class="system-message-title">System Message: WARNING/2 (<tt class="docutils">../LOCALIZATION.txt</tt>, line 142); <em><a href="#id2">backlink</a></em></p> 141 Inline interpreted text or phrase reference start-string without end-string.</div> 146 142 <p>13. Please check on your translations periodically to keep them updated as new versions are 147 released. A quick findfor "" will reveal any new or missing stings that need to be translated.</p>143 released. A quick search for "" will reveal any new or missing stings that need to be translated.</p> 148 144 <p>14. If you have other questions or about contributing a translation to eduCommons please contact 149 us at educommons [at] cosl [dot] usu [dot] edu. Thank you for you help!</p>145 us at info [at] educommons [dot] com. Thank you for you help!</p> 150 146 </blockquote> 151 147 </div> … … 155 151 <hr class="footer" /> 156 152 <a class="reference external" href="LOCALIZATION.txt">View document source</a>. 157 Generated on: 2009-08-0 6 16:49UTC.153 Generated on: 2009-08-09 07:41 UTC. 158 154 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 159 155 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/MIGRATION.html
r520 r566 5 5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 6 6 <meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> 7 <title>Migrating to eduCommons 3.2.1 </title>7 <title>Migrating to eduCommons 3.2.1-rc2</title> 8 8 <link rel="stylesheet" href="./default.css" type="text/css" /> 9 9 </head> 10 10 <body> 11 <div class="document" id="migrating-to-educommons-3-2-1 ">12 <h1 class="title">Migrating to eduCommons 3.2.1 </h1>11 <div class="document" id="migrating-to-educommons-3-2-1-rc2"> 12 <h1 class="title">Migrating to eduCommons 3.2.1-rc2</h1> 13 13 14 14 <div class="section" id="preparation"> … … 20 20 </ol> 21 21 </div> 22 <div class="section" id="migration-of-educommons-3-1-1-final-to-3-2-1 ">23 <h1>Migration of eduCommons 3.1.1-final to 3.2.1 </h1>24 <p>The migration eduCommons from version 3.1.1-final to version 3.2.1 22 <div class="section" id="migration-of-educommons-3-1-1-final-to-3-2-1-rc2"> 23 <h1>Migration of eduCommons 3.1.1-final to 3.2.1-rc2</h1> 24 <p>The migration eduCommons from version 3.1.1-final to version 3.2.1-rc2 25 25 includes the following:</p> 26 26 <ol class="arabic simple"> 27 27 <li>Pre-migration of Data.fs in version 3.1.1-final</li> 28 <li>Movement of Data.fs file to a new 3.2.1 instance</li>29 <li>Migration to the eduCommons 3.2.1 instance</li>30 <li>Export/Import of eduCommons site to a new 3.2.1 instance</li>28 <li>Movement of Data.fs file to a new 3.2.1-rc2 instance</li> 29 <li>Migration to the eduCommons 3.2.1-rc2 instance</li> 30 <li>Export/Import of eduCommons site to a new 3.2.1-rc2 instance</li> 31 31 <li>Final steps</li> 32 32 </ol> … … 65 65 </ol> 66 66 </div> 67 <div class="section" id="movement-of-data-fs-file-to-a-new-3-2-1- instance">68 <h1>Movement of Data.fs file to a new 3.2.1 instance</h1>67 <div class="section" id="movement-of-data-fs-file-to-a-new-3-2-1-rc2-instance"> 68 <h1>Movement of Data.fs file to a new 3.2.1-rc2 instance</h1> 69 69 <p>For this step, you will move the Data.fs file from the old instance to 70 the new instance. First of all, install an eduCommons-3.2.1 70 the new instance. First of all, install an eduCommons-3.2.1-rc2 71 71 instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 72 72 copy the Data.fs file from the var directory of the old site to the … … 76 76 </pre> 77 77 </div> 78 <div class="section" id="migration-to-educommons-3-2-1- instance">79 <h1>Migration to eduCommons 3.2.1 instance</h1>80 <p>eduCommons 3.2.1 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation:</p>78 <div class="section" id="migration-to-educommons-3-2-1-rc2-instance"> 79 <h1>Migration to eduCommons 3.2.1-rc2 instance</h1> 80 <p>eduCommons 3.2.1-rc2 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1-rc2. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation:</p> 81 81 <ol class="arabic simple"> 82 82 <li>Navigate to the root of your ZMI instance and create a new eduCommons site called eduCommons321</li> 83 <li>Open your new 3.2.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li>83 <li>Open your new 3.2.1-rc2 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li> 84 84 <li>Navigate to portal_setup</li> 85 85 <li>Press the 'Upgrades' tab</li> … … 89 89 </ol> 90 90 </div> 91 <div class="section" id="export-import-of-educommons-site-to-a-new-3-2-1- instance">92 <h1>Export/Import of eduCommons site to a new 3.2.1 instance</h1>91 <div class="section" id="export-import-of-educommons-site-to-a-new-3-2-1-rc2-instance"> 92 <h1>Export/Import of eduCommons site to a new 3.2.1-rc2 instance</h1> 93 93 <p>You are now ready to transfer your migrated instance to the production environment.</p> 94 94 <ol class="arabic simple"> 95 95 <li>Navigate to the root of your ZMI instance</li> 96 <li>Select the checkbox next to your new 3.2.1 eduCommons site</li>96 <li>Select the checkbox next to your new 3.2.1-rc2 eduCommons site</li> 97 97 <li>Press Import/Export</li> 98 98 <li>If your production environment is on the same server as your migration environment, choose 'Save file to server', else … … 113 113 <hr class="footer" /> 114 114 <a class="reference external" href="MIGRATION.txt">View document source</a>. 115 Generated on: 2009-08-0 6 16:49UTC.115 Generated on: 2009-08-09 07:41 UTC. 116 116 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 117 117 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/MIGRATIONS_OLD.html
r520 r566 223 223 <hr class="footer" /> 224 224 <a class="reference external" href="MIGRATIONS_OLD.txt">View document source</a>. 225 Generated on: 2009-08-0 6 16:49UTC.225 Generated on: 2009-08-09 07:41 UTC. 226 226 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 227 227 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/PORTLETS.html
r520 r566 158 158 <hr class="footer" /> 159 159 <a class="reference external" href="PORTLETS.txt">View document source</a>. 160 Generated on: 2009-08-0 6 16:49UTC.160 Generated on: 2009-08-09 07:41 UTC. 161 161 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 162 162 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/SETUP.html
r520 r566 60 60 <h1>Site Settings</h1> 61 61 <p>The <em>Site Title</em> and <em>Site Description</em> fields should contain values that were initially set during the installation process. If you want to change these fields, you can do so here. The <em>Site Title</em> field is referred to throughout the site. It is important to remember that eduCommons will only change the portal title on a page when a template is applied. If you change this setting here, it will be necessary to also change it throughout the site, or to reapply templates that refer to it.</p> 62 <p>eduCommons provides a number of settings that can be used with your site. The <em>Site 'From" Name</em> and <em>Site 'From' Address</em> are already discussed in the section titled <a class="reference internal" href="#mail-settings">Mail Settings</a>.</p>63 62 <p><em>JavaScript for web statistics support</em> is an area for enabling web statistics support from external providers (for e.g. Google Analytics). Paste the code snippets provided. It will be included in the rendered HTML as entered near the end of the page.</p> 64 <p>The <em>Default Language</em> setting is discussed in the next section.</p>65 63 </div> 66 64 <div class="section" id="setting-the-default-language-for-your-site"> … … 100 98 <h1>Other Customizations</h1> 101 99 <p>If you have a need for further customizations in your eduCommons site, it is possible to change things at a number of levels. This flexibility comes at a cost. The more a site is customized, the harder it is to upgrade when new versions become available. It is important to consider carefully the cost of additional functionality before you make any decisions on customizations.</p> 102 <p>There are other options that are available if you find yourself needing extra functionality. The <a class="reference external" href="http:// cosl.usu.edu/trac">development site</a> for eduCommons can be used to check to see if your bug is being or has been fixed, or to see what features have been scheduled for development on the <a class="reference external" href="http://cosl.usu.edu/trac/roadmap">roadmap</a>. There are also <a class="reference external" href="http://cosl.usu.edu/forums">forums</a> where you can post issues and get responses from the development team and/or other eduCommons users.</p>100 <p>There are other options that are available if you find yourself needing extra functionality. The <a class="reference external" href="http://educommons.com/dev">development site</a> for eduCommons can be used to check to see if your bug is being or has been fixed, or to see what features have been scheduled for development on the <a class="reference external" href="http://educommons.com/dev/roadmap">roadmap</a>. There are also <a class="reference external" href="http://educommons.com/support-forums">forums</a> where you can post issues and get responses from the development team and/or other eduCommons users.</p> 103 101 <p>eduCommons depends on community support, and participation in the user community/development process is both appreciated and welcome.</p> 104 <p>For additional documentation, including updates to these setup instructions, please visit: <a class="reference external" href="http:// cosl.usu.edu/projects/educommons/documentation">http://cosl.usu.edu/projects/educommons/documentation</a>, specifically <a class="reference external" href="http://cosl.usu.edu/projects/educommons/documentation/how-to">http://cosl.usu.edu/projects/educommons/documentation/how-to</a></p>102 <p>For additional documentation, including updates to these setup instructions, please visit: <a class="reference external" href="http://educommons.com/documentation">http://educommons.com/documentation</a></p> 105 103 </div> 106 104 </div> … … 108 106 <hr class="footer" /> 109 107 <a class="reference external" href="SETUP.txt">View document source</a>. 110 Generated on: 2009-08-0 6 16:49UTC.108 Generated on: 2009-08-09 07:41 UTC. 111 109 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 112 110 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/SeleniumRCTests.html
r520 r566 5 5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 6 6 <meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> 7 <title>eduCommons 3.2.1 SeleniumRC Testing</title>7 <title>eduCommons 3.2.1-rc2 SeleniumRC Testing</title> 8 8 <meta name="author" content="Santiago Suarez Ordoñez <santiycr @ gmail..com>" /> 9 9 <meta name="copyright" content="This document has been placed in the public domain." /> … … 11 11 </head> 12 12 <body> 13 <div class="document" id="educommons-3-2-1- seleniumrc-testing">14 <h1 class="title">eduCommons 3.2.1 SeleniumRC Testing</h1>13 <div class="document" id="educommons-3-2-1-rc2-seleniumrc-testing"> 14 <h1 class="title">eduCommons 3.2.1-rc2 SeleniumRC Testing</h1> 15 15 <table class="docinfo" frame="void" rules="none"> 16 16 <col class="docinfo-name" /> … … 90 90 Role Username Password 91 91 ==== ========= ========= 92 admin admin admin92 admin/manager admin test1234 93 93 producer producer producer 94 94 reviewer reviewer reviewer 95 qa qa qa95 qa quality quality 96 96 publisher publisher publisher 97 viewer viewer viewer97 viewer viewer viewer 98 98 ======= ========= ========= 99 99 </pre> … … 295 295 <hr class="footer" /> 296 296 <a class="reference external" href="SeleniumRCTests.txt">View document source</a>. 297 Generated on: 2009-08-0 6 16:49UTC.297 Generated on: 2009-08-09 07:41 UTC. 298 298 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 299 299 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/src/CHANGES.txt
r8 r566 1 ======================== 2 Changes in version 3.2.1 3 ======================== 4 Installers 5 Simplified installation have been added, including buildout scripts and Windows installers. 6 Expanded IMS Import 7 eduCommons can now import from IMS Common Cartridge, IMS Content Package, MIT course downloads, Blackboard IMS, WebCT Vista, WebCT 6.1/7.0, and Moodle Backups. 8 Improved IMS Export 9 eduCommons can now export to IMS Common Cartridge, IMS Content Package, and IMS Package for Moodle. 10 WordPress Import/Export 11 Support has been added to import pages from a WordPress site as well as export eduCommons content directly to WordPress pages. 12 Static Site 13 It is now possible to publish an entire eduCommons site to static HTML. 14 Expanded RSS 15 Additional RSS have been added to create an RSS feed of most recent items. 16 OIA-pmh and Improved Metadata 17 Support has been added for additional metadata in rdf/rss views as well as OAI/pmh. 18 OpenSearch Support 19 Support has been added for OpenSearch, including the Firefox OpenSearch widget which allows a search of a specific eduCommons site directly from the browser's search window. 20 1 21 ======================== 2 22 Changes in version 3.1.0 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/src/LOCALIZATION.txt
r8 r566 37 37 less time consuming because most of the translation work has already been done in Plone. 38 38 39 There are about 4 00 strings needed for a translation of eduCommons (compared to about 1600 strings39 There are about 470 strings needed for a translation of eduCommons (compared to about 1600 strings 40 40 for a Plone translation). Some of these are sentences or paragraphs, but the major part are one or 41 41 two words. These strings are scattered around in Plone, for example in page templates. Other items 42 42 to translate are widget labels, and workflow states. All those strings are collected in master 43 files. Currently eduCommons contains six.pot files. Each language requires its own .po files that43 files. These are called .pot files. Each language requires its own .po files that 44 44 corresponds to the strings or message ids declared in the .pot files. The .pot is the blueprint for 45 45 the .po files. … … 82 82 this translation compared to not getting one at all :) 83 83 84 4. Here is a link to the most recent translation files available for eduCommons (plone.po and 85 eduCommons.po). Remember, unless there is already an existing translation available, you need 86 to grab the .pot files. 87 88 http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/ 89 90 Here are links to the latest translations for each of the eduCommons products on the Plone 91 Collective site (these links may change, so check back for the most accurate information): 92 93 http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/ 94 95 http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/ 96 97 http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/ 98 99 http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/ 84 4. Each product in eduCommons has .po files located in the locales directory. We have combined 85 all these files in a single location of ease of translation. It can be accessed here: 86 http://educommons.com/localization/localization-files.zip 87 If you wish to translate a language for which we do not currently have translation files, 88 please contact us at info [at] educommons [dot] com. 100 89 101 90 … … 139 128 ${number} TRANSLATION. 140 129 141 9. Keep translating (but take breaks, this isn't done in one sitting - it's repet etive (but130 9. Keep translating (but take breaks, this isn't done in one sitting - it's repetitive (but 142 131 rewarding) work. After you have translated all of plone.pot, you should start on eduCommons.pot. 143 132 Don't worry, you have already completed the biggest part. … … 154 143 works, you can get an account with Plone (Here's how to request write access to the Collective.) 155 144 and maintain the files in SVN yourself (see next section). If not, no problem, just e-mail your 156 translation to us at eduCommons [at] cosl [dot] usu [dot] edu, and we will add it for you and put it into the145 translation to us at info [at] educommons [dot] com, and we will add it for you and put it into the 157 146 eduCommons distribution in the next release. We will also add you to our our `eduCommons 158 Localization Team page . <./educommons-localization-team>`__147 Localization Team page, here: http://educommons.com/documentation/how-to/educommons-localization-team 159 148 160 149 13. Please check on your translations periodically to keep them updated as new versions are 161 released. A quick findfor "" will reveal any new or missing stings that need to be translated.150 released. A quick search for "" will reveal any new or missing stings that need to be translated. 162 151 163 152 14. If you have other questions or about contributing a translation to eduCommons please contact 164 us at educommons [at] cosl [dot] usu [dot] edu. Thank you for you help!153 us at info [at] educommons [dot] com. Thank you for you help! 165 154 -
enpraxis.educommons/trunk/enpraxis/educommons/docs/src/SETUP.txt
r8 r566 78 78 The *Site Title* and *Site Description* fields should contain values that were initially set during the installation process. If you want to change these fields, you can do so here. The *Site Title* field is referred to throughout the site. It is important to remember that eduCommons will only change the portal title on a page when a template is applied. If you change this setting here, it will be necessary to also change it throughout the site, or to reapply templates that refer to it. 79 79 80 eduCommons provides a number of settings that can be used with your site. The *Site 'From" Name* and *Site 'From' Address* are already discussed in the section titled `Mail Settings`_.81 82 80 *JavaScript for web statistics support* is an area for enabling web statistics support from external providers (for e.g. Google Analytics). Paste the code snippets provided. It will be included in the rendered HTML as entered near the end of the page. 83 81 84 The *Default Language* setting is discussed in the next section.85 82 86 83 Setting the Default Language for your Site … … 141 138 There are other options that are available if you find yourself needing extra functionality. The `development site`_ for eduCommons can be used to check to see if your bug is being or has been fixed, or to see what features have been scheduled for development on the `roadmap`_. There are also `forums`_ where you can post issues and get responses from the development team and/or other eduCommons users. 142 139 143 .. _development site: http:// cosl.usu.edu/trac144 .. _roadmap: http:// cosl.usu.edu/trac/roadmap145 .. _forums: http:// cosl.usu.edu/forums140 .. _development site: http://educommons.com/dev 141 .. _roadmap: http://educommons.com/dev/roadmap 142 .. _forums: http://educommons.com/support-forums 146 143 147 144 eduCommons depends on community support, and participation in the user community/development process is both appreciated and welcome. 148 145 149 For additional documentation, including updates to these setup instructions, please visit: http:// cosl.usu.edu/projects/educommons/documentation, specifically http://cosl.usu.edu/projects/educommons/documentation/how-to146 For additional documentation, including updates to these setup instructions, please visit: http://educommons.com/documentation -
enpraxis.educommons/trunk/enpraxis/educommons/docs/src/SeleniumRCTests.txt
r8 r566 53 53 Role Username Password 54 54 ==== ========= ========= 55 admin admin admin55 admin/manager admin test1234 56 56 producer producer producer 57 57 reviewer reviewer reviewer 58 qa qa qa58 qa quality quality 59 59 publisher publisher publisher 60 viewer viewer viewer60 viewer viewer viewer 61 61 ======= ========= ========= 62 62 -
enpraxis.educommons/trunk/enpraxis/educommons/tests/seleniumtests/QA.py
r512 r566 40 40 sel = self.selenium 41 41 sel.open("/eduCommons/logged_out") 42 sel.type("__ac_name", "q a")43 sel.type("__ac_password", " asdfasdf")42 sel.type("__ac_name", "quality") 43 sel.type("__ac_password", "quality") 44 44 sel.click("submit") 45 45 sel.wait_for_page_to_load("30000") … … 80 80 sel.click("link=Log out") 81 81 sel.wait_for_page_to_load("30000") 82 sel.type("__ac_name", "q a")83 sel.type("__ac_password", " asdfasdf")82 sel.type("__ac_name", "quality") 83 sel.type("__ac_password", "quality") 84 84 sel.click("submit") 85 85 sel.wait_for_page_to_load("30000") … … 96 96 sel = self.selenium 97 97 sel.open("/eduCommons/logged_out") 98 sel.type("__ac_name", "q a")99 sel.type("__ac_password", " asdfasdf")98 sel.type("__ac_name", "quality") 99 sel.type("__ac_password", "quality") 100 100 sel.click("submit") 101 101 sel.wait_for_page_to_load("30000") -
enpraxis.educommons/trunk/enpraxis/educommons/tests/seleniumtests/__init__.py
r557 r566 1 1 #import addNewSite 2 #import addNewUsersAll2 import addNewUsersAll 3 3 import accountsLogin 4 4 import createDivision -
enpraxis.educommons/trunk/enpraxis/educommons/tests/seleniumtests/accountsLogin.py
r512 r566 33 33 def test_admin_account(self): 34 34 sel = self.selenium 35 sel.login("admin"," admin")35 sel.login("admin","test1234") 36 36 self.failUnless(sel.is_element_present('//a[@id="user-name"]/span[text()="admin"]')) 37 37 self.assertEqual("admin (Administrator)",sel.get_text('//li[a[@id="user-name"]]')) -
enpraxis.educommons/trunk/enpraxis/educommons/tests/seleniumtests/addNewUsersAll.py
r512 r566 87 87 sel.wait_for_page_to_load("30000") 88 88 sel.type("fullname", "john doe") 89 sel.type("username", "q a")89 sel.type("username", "quality") 90 90 sel.type("email", "test@test.com") 91 91 sel.type("password", "asdfasdf")
Note: See TracChangeset
for help on using the changeset viewer.
