PostNuke

This article or section is currently under construction

In principle, someone is working on it and there should be a better version in a not so distant future.
If you want to modify this page, please discuss it with the person working on it (see the "history")

Definition

'PostNuke is a portalware or what we call the C3MS kind.

PostNuke in education

See TECFA SEED Catalog

Installation of PostNuke

Installation of the default portal

In order to install PostNuke you need first of all the right server architecture. Some Internet providers (e.g. Infomaniak in Geneva) provide this environment.

1. A Apache server with a correctly installed PHP
2. A MySQL server (preferably on the same server). You need full permissions for a least one database. Make sure that you know the name of the MySQL database, the name of MySQL user that has full access to it and the corresponding MySQL password.

You do not necessarily need access to the server (via telnet). FTP access is fine, provided that you are allowed to change file permissions or alternatively that your provider offers a web-based file management tool that allows you to change permissions. If you wish to install via FTP you need the following tools:

1. A FTP client
2. A "unzipping" tool like Winzip

1. Download PostNuke from http://www.postnuke.com
2. Decompress the *.zip or *.tar archive in some directory
3. Transfer the whole "html" subdirectory to your Web Server This may take some time. You can then rename this directory on the server if you wish
4. From a web browser, click on the file install.php and follow instructions You will have to enter the following information:
   1. Database name is in most cases: localhost
   2. Database Password
   3. Database Name
   4. Database Prefix This is a very useful feature if you have only access to a single database. Each table will be "prefixed" and there won't be a conflict with other installed portals.
5. Do a NEW INSTALL Don't check "create database" if you already got one !
6. Click on START and choose your password
7. Enjoy

PostNuke Modules installation

Most PostNuke Modules now install fairly easily, i.e. they follow the algorithm outlined below. However, always read the installation instruction. Some modules are not fully API compliant and need extra work. Also make sure to fix file permissions for modules that upload/download (this includes standard modules).

1. Download and uncompress archive
   1. Get the module preferably from it's author's site
   2. Extract the archive to some place Usually the module extracts to some subdirectory.
2. Install and Activate Module
   1. Copy your new_module folder to the postnuke modules folder
   2. Login to postnuke and select Modules from the administration menu
   3. Click on Regenerate
   4. Find your New_Module module and click Initialize
   5. Find your New_Module module and click Activate
3. Insert Module in some Menu
   1. Select Blocks from postnuke Administration Menu
   2. Find a Menu block and click Edit
   3. For URL use {new_module}, substitute of course "new_module" by the module name of your module use whatever you want for the other fields
   4. Click commit

Development of PostNuke Modules

Between 2001 and 2005, TECFA graduate or master students developed a few modules from which we can tell a few things:

While programming PostNuke modules is in most cases more efficient than writing stand-alone components, it is not easy. To program a good Beta version of typical module developed at Tecfa like pnProdAct, pScenariovQuizPN ArgueGraph,wTool takes on average about 2 month (more or less 1 month according to the complexity of the module, PhP programming skills and previous experience with PostNuke

Repurposing a module can take much less, if you don't need to change its structure. E.g. edu-recipes took less than a week for an unexperienced person.

Implementing a more ambitious module like Vivian Synteta's ePBL or Dorel Gorgas WINE (development of a an emotional agent, [1]) took more time.

If you subcontract module writing or if you hire someone you should insist that the person respects PostNuke's programming guidelines and its API (application programmer's interface). This will make installation much easier for everyone and it will greatly increase the likeliness that your module will run in future versions!

Documentation for writing such modules is not optimal (as with most Open Source projects. However, there are a number of resources which you can find in various Support portals. The starting point is http://docs.postnuke.com/ but many other places may have interesting information, e.g. at Tecfa we provided a few slides for PN 7.2x that we used for teaching: http://tecfa.unige.ch/guides/tie/html/portal-prog-pn-en/portal-prog-pn-en.html