Pier 1.2 to Pier 2.0

Several differences need to be taken into account:

• For HTML code, Pier 1.2 can have it sprinkled throughout, in Pier 2.0 it needs to be set aside within triple brackets (like this:

  wiki text {{{<span class="strong">text in HTML</span>}}} more wiki text

  ). After importing an older pier into a Pier 2.0 image, the Pier2Addon named Pier-SW2-Sw1Features can be used to convert the wiki to use the new format, see the class comment of the converter class for how to use this.

• Images downloaded from http://www.piercms.com/download are not yet able to run on SeasideHosting, the error in the system out is:

  This interpreter (vers. 6502) cannot read image file (vers. 6505).

  This is due to seasidehosting not supporting the COG VM (it can be identified by finding Closure Cog VM in PharoDebug.log). Options are:
  • Run the image under http://pharocloud.com - it does cost money, but there are pre-made images ready to use
  • Try an image from https://ci.inria.fr/pharo-contribution/job/Pier3Addons/
  • Build an image based on a Pharo image, the steps to get around this are:
    1. Download an image, such as from http://pharo-project.org/pharo-download, look for standard VM - versions 1.3 and newer are all pre-built with COG.
    2. Load Seaside & Magritte from the installing workspace, and Pier from the http://www.piercms.com/dev/code instructions
    3. Open the Seaside Control Panel - click World - Tools - Seaside Control Panel
    4. Choose Add Adaptor from the top pane, WAComancheAdaptor works well
    5. Going to http://localhost:8080/ should give a welcome page, next go to http://localhost:8080/config
    6. Add an application for Pier, from a workspace in the image you will need to create a PRKernel - ie PRKernel named: 'Smallwiki2'
    7. Load your favorite addons, good options are PBBlog and PRGoogleGadget

  Other tips can be found at http://book.seaside.st/book/advanced/deployment/deployment-preparing

• For importing change history, see Importing History
• The search is much improved over the search in previous version (and can replace the Pier 1.0 advanced search), however it is not immediately visible in Firefox. To make it more obvious, its best to add the example text by editing the search field:
  
• There is code in the 2.0 version that allows all children of a structure to have links - such as:

  *value:children|link*

  In one of the early version, the same could be created with:

  *value:children|link*

  The later version cause the plus signs to embed all of the children contents instead of creating links. If the plan is to create a list of links, it is best to use stars instead.

• At one point, the image grew to 300Mb, by checking Session Allow Termination to true in the Pier configuration, the size came back to normal.