Greetings all, I just thought I'd share my great experiences with OSTicket - and see if we can compile a few suggestions that may help the developers improve on the design portability.
First off - Well done. Great program. Very simple to install, customize and use. The 1.6 is indeed ready a great version, although I think a few simple changes will help developers looking for a great OS alternative.
Design time - Although easy to design for, and problems have been documented in the forums (such as the (admin login issue) for custom designs), it is still common to come across a few problems when customizing the installation. An easy fix for some issues would be a simple call in - just like with the header / footer includes.
(e.g. for index.php
<?php require('client.inc.php');?>
<?php require('style.inc.php'); ?>
<?php require(CLIENTINC_DIR.'header.inc.php');?> - developers do not edit
<?php require(CLIENTINC_DIR.'body.inc.php');?> - developers do not edit
<?php require(CLIENTINC_DIR.'base.inc.php');?>
<?php require(CLIENTINC_DIR.'footer.inc.php');?>
)
If you section the design of the site into these includes and the css only, then people can edit only the header / footer / main and css styles. They can simply add OST to their site by splitting a page from their site into sections. This will also get rid of the admin login issue, as the issue will only occur if certain code is placed inside the header.inc.php file.
Anyone have any other ideas, or has anyone found an easier way to integrate OST into their site?