#14 Fatal error

[Thomas Ball]

First step in install:

FATAL ERROR: Errors encountered while processing the database schema file.
CREATE TABLE IF NOT EXISTS ost_faq_settings ( id int(15) NOT NULL AUTO_INCREMENT, key_name varchar(35) NOT NULL, key_value text NOT NULL DEFAULT '', field_type varchar(15) NOT NULL, title varchar(64) DEFAULT NULL, description varchar(255) DEFAULT NULL, sort_order int(7) NOT NULL DEFAULT '0', date_added datetime NOT NULL DEFAULT '0000-00-00 00:00:00', last_modified datetime NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (id), UNIQUE KEY key_name (key_name) ) ENGINE=MyISAM DEFAULT CHARSET=utf8;

Then get an email with DB Error #1146

[select key_name, key_value, field_type from ost_faq_settings;]

Table 'osticket.ost_faq_settings' doesn't exist

[Tim Gall]

Will aim to have a look into this late this week (thurs/fri) or over the weekend.

I suspect its due to the version of mysql on your server. I think I know how to get around this and will attach a fix to this post as soon as I have time.

[Thomas Ball]

Tim

I would really appreciate this!

I would love to have your app work along with the osFAQ system

Tom

[Nobody/Anonymous]

Tim:

Just wondering if you had any time to look at this?

Tom

[Tim Gall]

Hi Tom,
Sorry for the delay. I did have a look at it and think its related to the TEXT data type in the "faq_settings" table declaration. At a guess I get the impression your db engine doesnt like the TEXT datatype (Im not sure why though). Ive heard from one other person who had the same issue.

To solve it Ill attach a patch file with my next comment that has the changes made to the install SQL. Ill replace the TEXT data type with LONGTEXT, BLOB or one of thier variants. Should be ready over the next few hours.

Tim

[Tim Gall]

v1.0-RC6 Patch-02 with modified faq_settings table

[Tim Gall]

Tom:
See the attached patch "osfaq_1.0.rc6_PATCH-02.1.zip" at the bottom of this page.
It contains patch 2 and the altered "faq_settings" table.

Tim

[Thomas Ball]

Tim:

Thanks

I will give it a try and let you know.

Appreciate your work on this.

Tom

[Thomas Ball]

Tim:

That seems to get rid of my database error.

However I now have a 500 - Internal server error when I click on the FAQ in the staff panel.

I guess I have some hunting to do.

Tom

[Tim Gall]

Hi Tom,
If you can give me some more details I can probably help.

Initially you could try enabling full error output in osTicket by edditting:
[your-osTicket-installation]/main.inc.php
Change lines 44 and 45 FROM:
ini_set('display_errors',0);
ini_set('display_startup_errors',0);
TO:
ini_set('display_errors',1);
ini_set('display_startup_errors',1);

That will display all errors on the page you are viewing instead of logging or suppressing them. It makes debugging easier when you can see them.

If that doesn't give you any ideas, try posting another comment here with the following info:

1) Can you paste the URL that triggers the 500 error. Leave the domain part out if you like, or mask it somehow.
2) Also let me know what server operating system you are running (linux, windows, etc).
3) Also if you can access your servers error log, have a read through it to see if theres any errors relating to your issue and let me know what they are.

[Tim Gall]

If you need any more help with this, add a comment and I can reopen the tracker.
Also, osFaq v1.0ST is due for release this month.