#45 Helpdesk 0.9.9 issues
I have enjoyed working with your software, and look forward to version one. I saw this newest 0.9.9 out there, and decided to try it out. I have not had much success with it. I think the main reason is there isn't much documentation for these new versions out. Anyhow, after figuring out how to install php-pear on a windows box, and finding that I had to install pear/db package, it finally worked. It didn't really say whether it supported mysql, but there was an option for it in the conf file, so I installed appserv 2.5.7 on windows XP, which is what I have been using before with postgresql. I managed to create the database, but when I tried to run that sql query, it spit up some errors. The first error was easy enough to fix; there were some semicolons in the middle of a insert into statement. The tbl_wrktimer, I never got inserted the way it was supposed to be.
That being said, I played around with it a little, noticed some weird sql errors every now and then, mostly about constraints being violated. I would go back, and then forward again, and it would work fine.
I noticed that the CSS doesn't display right in IE 6. At least it didn't for me. The footer grey area went all the way up past the username/password entry. I haven't noticed any errors with the CSS in firefox 1.5 or 2.0.
Since I had some problems with the mysql database, I decided to try the postgresql again, since that is what this was originally built on. I installed the newest (8.2.1) version of postgresql for windows, and created the database. I tried to run that sql code for postgres, and it once again spit up some errors. "ERROR: there is no unique constraint matching given keys for referenced table "tbl_issues"
SQL state: 42830
" is the error that I got.
I would really like to use your software, and have enjoyed using the .9 version. Not too many problems with that one.
Although, I did have a redirect error, where if you tried to login unsuccessfully, and then logged in correctly, would append another helpdesk/ in the path. Oh, and if the files are in the root of the www directory, something's weird, because the address it takes you to when you log in is something like http://localhost\domains.php/ just like that. .9.9 does the same thing. I don't think it's a problem with my apache configuration. As soon as I put it into a subdirectory, such as www/helpdesk/, it works fine.
I apologize for the long post, and probably should have split these errors up into separate issues.
my email address: wlentz102@gmail.com
Thank you very much for you assistance.
Logged In: YES
user_id=564662
Originator: NO
As a tester i confirm the MySQL database errors :
in :
INSERT INTO `tbl_Links` (`id`, `text`, `link`, `category`, `sortorder`) VALUES (1, 'Home', 'index.php', 1, 0),
(2, 'About', 'about.php', 1, 1),
(3, 'News', 'news.php', 1, 2),
(4, 'Documentation', 'docs/index.html', 1, 3);
(5, 'F.A.Q.', 'faq.php', 1, 4),
(6, 'Download', 'download.php', 1, 5);
(7, 'Features', 'features.php', 1, 6),
(8, 'Change Log', 'changelog.php', 1, 7),
(9, 'Central Mcr. CLC', 'http://helpdesk.centralmanclc.com/', 2, 0),
(10, 'Oxford Archeology', 'http://www.thehumanjourney.net/', 2, 1);
(11, 'European Electronique', 'http://www.euroele.co.uk/', 2, 2);
There are ";" who are comming too early
And in :
CREATE TABLE tbl_Wrktimer (
issue int4 DEFAULT '0' NOT NULL,
userid int4 DEFAULT '0' NOT NULL,
running ENUM('f','t') DEFAULT 'f' NOT NULL,
`begin` DATETIME DEFAULT 'now()' NOT NULL,
`end` DATETIME DEFAULT 'now()' NOT NULL,
primary key (issue,userid)
);
The default value 'now()' for begin an end is not alowed by MySQL syntax. A
As a workaround i have used instead :
`begin` TIME DEFAULT '' NOT NULL,
`end` TIME DEFAULT '' NOT NULL,
Witch is probably not good as it fails my install....
See : http://dev.mysql.com/doc/refman/5.0/en/data-type-defaults.html
Logged In: YES
user_id=1768647
Originator: NO
I am in the middle of evaluating numerous helpdesk apps and was particularly interested in a PHP MySQL based one. After running through the same setup issues as outlined by the previous posters and having duely fixed them I got this error. "DB Error: extension not found" which has stumped me so far.
Have you a timeline for v1 to be released and this version is very buggy from a MySQL point of view. Or has anyone else run into this DB issue as well, who can help me out?