Pika 306 Whats New

Notes on What's New in Pika 3.06

Pika 3.06 was released on June 6, 2007.

According to the changelog, the Customization Manager is not used anymore. There appears to be a new file structure. Pika 3.06 now expects 2 directories at the same level, one for the main Pika files, and one for custom files that has "-custom" appended to its directory name. So for instance, on one of my local pika installs, under /var/www/ there is a directory called apache2-default. In there I copied all the main files from the pika_cms-306 directory. Then I created an apache2-default-custom directory and copied in the files from pika_cms-306-custom directory. Depending on how you configure your Apache webserver, you may just be able to copy those 2 pika directories straight from the zip file onto the web server. Note that the settings.php is now in the "blahblah-custom\config" directory, and if you are migrating you'll need to move your settings.php over there. New code has been added to /app/lib/pl.php to handle this new way of organizing the custom template files. Correspondingly, calls to the templating function now look like this: pl_template($a, 'subtemplates/pb_attorneys.html', 'yes'); and notice it includes a more full path. The library code will appropriately route this to a custom subtemplate if it exists, or to the default one if there is not a custom one. In my testing, I've found that the custom file structure works for templates, subtemplates, and modules. It does not work for reports. Reports must stay under the main Pika reports directory.

-- original entry by Andrew Cameron