$this->dbtype = "mysql"; // Change this if you are not running a mysql database server. Note, the publishing solution has only been tested on MySQL.

Transcription

1 0.1 Installation Prior to installing the KRIG publishing system you should make sure that your ISP supports MySQL (versions from 4.0 and up) and PHP (version 4.0 or later, preferably with PEAR installed.) If PEAR is missing then the PEAR library can be downloaded and placed alongside KRIG and it will function perfectly, it just uses some more discs space (see ini settings for more information.) Any webserver can be used as long as it supports PHP. For the rest of this installation guide it will be assumed that the database in question is called website and that the username for the database is websiteuser with password websitepassword. Further it is assumed that the database is running on the same host as the publishing solution so that it can be reached by the name localhost. The database The first step to installing KRIG is to install the database. The database creation is handled through a series of SQL statements and the script creating all tables and initializing the user and user group tables can be downloaded from You can either cut and paste directly from the page or download the entire script as a file. To create all tables and initialise the database the following command line can be used : mysql u websiteuser p website < db_creation.sql Note that the password is not given on the command line, the mysql client will ask for the password when running. db_creation.sql is the name of the file containing the sql statements (standard name if downloaded from the above given address.) The website database should now contain 20 tables and be ready for usage by the KRIG publishing system. The scripts The next step is to extract the zip archive containing the KRIG publishing system into the directory where you want to publish it. The system can be installed in any folder that your web server can read from. After extracting all files you will need to edit the configuration.php script to reflect your actual setup, the items that needs to be changed are: $this->dbtype = "mysql"; // Change this if you are not running a mysql database server. Note, the publishing solution has only been tested on MySQL. $this->dbserver = "localhost"; // The host name for the database server, or as here, localhost if the database server runs on the same server as the publishing solution. $this->dbnavn = "website"; // The name of the database to be used by the publishing solution. $this->dbbrukernavn = "websiteuser"; // The name of the database user. $this->dbpassord = "websitepassword"; // The password of the database user. $this->baseurl = " // The url where the pages is published, without any filename, that is, the base url for the published pages. $this->tmpdir = D:/tmp/ ; // A folder where the database user has write access, i

2 temporary files/folders that needs to be created will be placed here. After completing this you can direct your browser to the base URL and you should see the same layout as on the page where you downloaded the database installation script but with no content. On the left you should see a login area and you can login with username administrator and password password Advanced options Installed out of the box the KRIG publishing system uses query based URLs, that is the page id is attached to the URL as a query. This means that you will get URLs of the form: This might not be what you want and if your web server is an Apache web server you can change this yourself by changing one line in the configuration.php file. Alter the line that reads : $this->usestaticurls = false; // Only if apache with rewrite rules enabled to $this->usestaticurls = true; // Only if apache with rewrite rules enabled This will enable the URL rewrite rule on the line above which as default changes the URLs so that the two URLs shown above would become : This makes for cleaner URLs if the addresses are to be used externally and it also ensures that search engines like google will not turn their backs on your pages. Note, this requires that your Apache installation honours the.htaccess file in the installation directory. This functionality is not available on any other web servers beside Apache. The setting in the configuration file that reads $this->topindex = 0; is for the situations where you have more than one website using the KRIG publishing solution running on the same database. This can be the case for instance if part of your site is published separately as well as part of the main site. You can then make a separate installation of the script files and set the topindex to point to the id of the category that you want to use as a top node on specialized website. This website can then have its own layout and appear to be totally separate from the main site thought the content is shared among the two Ini settings Some PHP installations does not make the PEAR library available, if this is the case for you then you can download the PEAR library from and place it in a subfolder in your KRIG installation folder. You then need to tell PHP where to find the files. Placing an ini directive in the configuration.php file does this. Uncomment the following line in the configuration.php file: //ini_set ("include_path", ini_get("include_path").";"."s:\ewaydav\imt\pear"); // Fix if PEAR is not installed server wide You need to change S:\ewaydav\imt\pear to point to the directory where you put the pear files. ii

3 Troubleshooting If you experience trouble getting KRIG up and running you can try to uncomment the first line in the configuration.php file: ini_set ("display_errors", "1"); // Set to 0 when configured This will enable PHP to send all error messages to the browsers viewing the page. If you can view pages in KRIG but experience problems logging on it is probably because the settings for storing temporary files on the server is wrong, you can fix this by enabling the second line in the configuration.php script: //ini_set ("session.save_path", "S:\ewaydav\imt\sessionvars"); // Point to a writable directory if not already Uncomment this line and change S:\ewaydav\imt\sessionvars to a directory where the webserver user has write access, this can be the same as $this->tmpdir 0.2 Page design Pages published in KRIG are built up according to a template where HTML comments is used to position the breadcrumb, menu, main content and footer information. A css style sheet is used to define the way different elements should look. Each page that is published is connected to a template file and a css file, these two files can be used for every page that is published or a separate template and css file can be used for each page. The template file and css file will always work as a pair and if you want to make a new layout you must create both a template and a css file and place them in a folder together with any images used by the template file. The HTML comments that can be placed in the template file are: <! pathfinder > This tag will be replaced by a breadcrumb showing the navigational path followed to get to the currently displayed page <! categories tree > This tab will be replaced by an expanding tree structure menu showing the currently displayed page and its sub pages. This menu can then be used to navigate to any sub pages of the currently displayed page, any pages on the same level as the currently displayed page or any of the current pages parents. <! minimum categories tree > This tag will be replaced by a one level menu. This one level menu will show any sub pages of the currently displayed page. If the currently displayed page does not have any sub pages it will display all pages on the same level as the currently displayed page. <! content here > This tag will be replaced by the content of the page. The majority of the page comes from this replacement. <! page owner > This tag will be replaced by the name of the user owning this page. The name will be displayed as a link enabling readers of the page to send to the page owner. <! last page update > iii

4 This tag will be replaced by the date and time of the last update on the page. The last update time is shown as the last time any element on the page changed. <! login screen > This tag will be replaced by the login/logout screen. This screen also gives access to the user settings when a user is logged in or the main administrator pages when an administrator is logged in. It is not possible to give access to the user preferences link or the administrator page link without showing the login/logout image. <! printfriendlyurl > This tag will be replaced by the URL required to create a printer friendly version of this page. The printer friendly page will be generated by skipping the template and only generating the content for the page. This tag needs to sit in a anchor tag like this: <a href= <! printfriendlyurl > >something</a> The page layout with these tags placed where the elements is to be placed needs to be called content.template. Any one template can use one or more of the tags to place the needed elements on a page. Which tags to use is totally up to the designer of the page and depends on the information one wants on the page. The content.template file for the KRIG homepages is shown in figure 1. 1 <s c r i p t type=" t e x t / j a v a s c r i p t "> 2 <! 3 i f ( s e l f. parent. frames. length!=0) { 4 document. l o c a t i o n = document. l o c a t i o n. t o S t r i n g ( ). replace (/ index. php/ gi, 5 " p r i n t F r i e n d l y. php")+"& quiet=true " ; 6 } 7 // > 8 </s c r i p t > 9 <t a b l e border ="0" width="800px " c l a s s ="TABLE " c e l l s p a c i n g ="0" cellpadding ="0" 10 s t y l e ="background : rgb (255,255,255);" > 11 <tr> 12 <td width="800px " colspan ="2" bgcolor="#ffffff " s t y l e ="height : 86px ; 13 background image : u r l ( heading. gif ) ; background repeat : no repeat"> 14 <t a b l e border ="0" width="100%" s t y l e ="height :86 px " 15 c e l l s p a c i n g ="0" cellpadding ="0"> 16 <tr> 17 <t d width ="180" rowspan="2"></td> 18 <td width ="620" height="55"></td> 19 </tr> 20 <tr> 21 <td width ="620" height ="25" valign="top"><! pathfinder ></td> 22 </tr> 23 </table> 24 </td> 25 </tr> 26 <tr> 27 <td width="174px " height ="100" valign="top " s t y l e ="width :174px ; 28 background image : u r l ( menu. gif ) ; background repeat : y repeat"> 29 <t a b l e border ="0" s t y l e ="width :174px ; " c e l l s p a c i n g ="0" cellpadding ="0"> 30 <tr> iv

5 31 <t d width ="8px"></td> 32 <td width="150px"><! c a t e g o r i e s t r e e ><br><br> 33 <! login screen ></td> 34 <t d width ="16px"></td> 35 </tr> 36 </table> 37 </td> 38 <td width="646px " height ="500" valign="top"> 39 <! content here > 40 </td> 41 </tr> 42 <tr> 43 <td width="100%" colspan ="2" s t y l e ="height : 8px ; 44 background image : u r l ( body_end. gif ) ; background repeat : no repeat"></td> 45 </tr> 46 <tr> 47 <td width="100%" colspan ="2" s t y l e ="height : 22px ; 48 background image : u r l ( f o o t e r. gif ) ; background repeat : no repeat"> 49 <t a b l e border ="0" width="100%" c e l l s p a c i n g ="0" cellpadding ="0" > 50 <tr> 51 <t d width="190"></ td> 52 <td width ="610" c l a s s =" f o o t e r t x t ">Page maintained by 53 <! page owner >. Page l a s t updated <! l a s t page update ></td> 54 </tr> 55 </table> 56 </td> 57 </tr> 58 </table> Figure 1: example content.template file The following css classes can be defined in the intranet.css file:.pathfinder This class is used to display the breadcrumb links..menuitem This class is used for displaying a menu item in the tree structure menu (class is used on a table data element) and in a one level menu (class is used only on the actual anchor element.).menuitemselected Used to display the selected menu item in the tree structure menu..selectedmenuitem Used to display the selected menu item in a one level menu..footertxt Used for displaying text normally found in the footer of the page (page author and last modified information.) v

6 .footertxt A Same as above but for link text (page author with registered .).dialog This class should be fine as it is, used to lay out dialog windows in the publishing part.pagehaspresentation Used to format the notice letting the user know that there are self running presentations available. The classes above is reserved by the system and can not be changed. Other CSS can be created at will to create the layout the designer want to achieve. In addition to the above mentioned classes the definition shown below should also be included in all intranet.css files. p r i n t { 2 div. sp_formfeed { 3 page break before : always ; 4 } 5 } This definition is used so that annotations shown as footnotes can always be put on separate pages. The content.template and intranet.css files must be placed in a web accessible place, the pair defining the default layout of published pages should be placed in the folder where the basic scripts for the publishing solution is located (this folder already contains a content.template and intranet.css file with a default layout but you would probably like to alter these.) Alternative layouts can be specified by giving either a relative or absolute address from the Edit category of the Category control dialog. vi