Upgrading Mojo

You might also be interested in an auto-upgrade tool, MojoRising.  Use PowerShell instead.

Note: It is recommended that if you are upgrading from a much earlier version of mojo (let’s say, 10 iterations back), you should back up your /Data/Sites/ folder and do a fresh install instead.  You may also want to consider doing a fresh install for every major release of mojo (eg, moving from 2.2 to 2.3 or at least 2 to 3).  Please reference http://www.mojoportal.com/upgrading.aspx for more information on the upgrade process

<Style name="Heading 1" element="h1" />
<Style name="Heading 2" element="h2" />
<Style name="Heading 3" element="h3" />
<Style name="Heading 4" element="h4" />
<Style name="Heading 5" element="h5" />

 

  1. Download the latest version of mojo from http://mojoportal.codeplex.com/releases/
  2. Remove the extraneous “skin” folder(s) from the download.
  3. Login to your site as admin before uploading the files for any upgrade
  4. Copy your db connection string, as you’ll need to paste it back into web.config when done, or just make sure it’s saved in the user.config file.
  5. Copy any files that you modified in MojoPortal to your local drive. These will be overwritten during the upgrade, unless of course you changes are confined to your uniquely-named skin folder. It’s a good idea to create a folder on your local drive with the modified files in their paths relative to MojoPortal.
  6. Rename the SetupProviderConfigindexbuilders folder on the server (your target location).  This is necessary when upgrading to versions 2.3.0.4 and above.
  7. Remove the following DLLs from your /bin folder, per this blog post – all DLLs that begin with PollFeature and SurveyFeature.
  8. Upload the Setup folder from new version of CMS
  9. Upload remaining files, making sure you do not overwrite your chosen skin folder (shouldn’t happen if you gave it a unique name). Your skin folder is located at DataSites1skinsskinfoldername.  Your skin folder may not be under the “1” directory is you have more thaAlso, be especially careful that you have backups of the following files, if you have changed them from mojo’s defaults:
    1. error.htm / PageNotFound.aspx
    2. ClientScript/mojofckconfig.js – Where you control the toolbar sets.  Eg, you may want to add back in ‘TextColor’
    3. Data/Sites/1/style/CalendarMojo.css
    4. ClientScript/mojofckstyles.xml – Where the FCKEditor styles are located.
  10. Open web.config and repaste your unique settings (ignore if you’ve been using user.config)
  11. If you are upgrading from a version below 2.3.0.8 and would like to use the new search improvements integrated into mojo, consider adding the code below for the new search results and rebuilding your search index.  When upgrading, you may need to rebuild your search index anyways, so ideally you should do a test search post upgrade to see for sure.
  12. .searchterm { color:black; background-color:yellow; }
  13. Make sure the Data folder has full ACL privileges
  14. Navigate to installation folder via web browser (eg, http://wsdev.colostate.edu/cwis123/Setup/default.aspx)
  15. Disable setup in web.config, which also will restart the web application.
  16. If you have done it already, consider deleting the extra skins that were installed
  17. You may want to check out this blog post in case any new features require CSS changes
  18. Make the appropriate web.config changes per the Install Notes, especially consider doing the following:
    • using the fulltrust web.config file
    • changing the cookie name from .mojochangeme to something unique to your site
    • changing the machinekey from the default value
    • uncommenting/changing the maximum file size upload in web.config (see code below)
    • allowing more media formats like .mp4 (see https://www.mojoportal.com/using-the-audio-and-video-players for details)
    • enabling gZip/content compression (see code below)
    • implementing a meta switch in IIS if you want/need to force your pages to use some predefined rendering engine (see http://msdn.microsoft.com/en-us/cc817572.aspx)
  19. Consider uncommenting/changing the maximum file size upload in web.config (below is set to 20 megs):
    <httpRuntime requestValidationMode="2.0" maxRequestLength="20480" maxUrlLength="560" maxQueryStringLength="2048"  />
  20. Consider adding the following code to the webServer element of web.config to setup gZip/caching:

<staticContent>
<clientCache httpExpires="Sun, 29 Mar 2020 00:00:00 GMT" cacheControlMode="UseExpires" />
</staticContent>
<httpCompression directory="%SystemDrive%inetpubtempIIS Temporary Compressed Files">
<scheme name="gzip" dll="%Windir%system32inetsrvgzip.dll"/>
<dynamicTypes>
<add mimeType="text/*" enabled="true"/>
<add mimeType="message/*" enabled="true"/>
<add mimeType="application/javascript" enabled="true"/>
<add mimeType="*/*" enabled="false"/>
</dynamicTypes>
<staticTypes>
<add mimeType="text/*" enabled="true"/>
<add mimeType="message/*" enabled="true"/>
<add mimeType="application/javascript" enabled="true"/>
<add mimeType="*/*" enabled="false"/>
</staticTypes>
</httpCompression>

 

 <httpProtocol>
<customHeaders>
<clear />
<add name="X-UA-Compatible" value="IE=edge" />
</customHeaders>
</httpProtocol>