Menu

#58 Empty Category Names

1.2-ST
open
nobody
Categories (1)
5
2013-10-24
2013-10-10
No

We're on Version 1.2.1 ST - with osTicket version 1.7.1.3
We're on an Ubuntu LAMP stack - 13.04.

After the recent modification, we successfully installed osFAQ and integrated it with osTicket using the provided instructions. All is well, until in the admin interface, I attempt to add a new ticket category in osFAQ. The dialog box accepts my inputs, and creates a new category, but there is no name on the category. (see attachment).

I launched phpMyAdmin to see what the database table had - no luck. There are also entries there, but the category label field is blank.

Thanks! Let me know if there's any other info you'd like me to try or test!

-Stead
Eugene, OR

1 Attachments

Discussion

  • Tim Gall

    Tim Gall - 2013-10-11

    Hi Stead,
    Im not sure whats causing that. Ive tried to reproduce it but only in FireFox. Can you tell me what browser you are using? I cant see anything obvious yet but will have another look and try to reproduce it the problem. My testing version of osTicket is 1.7.1.4 but I dont think 1.7.1.3 will be any different. The main changes to forms was in version 1.7.

    One thing you could try with testing is to edit the osTicket file /main.inc.php.
    Change lines 47 and 48 to:
    ini_set('display_errors', 1);
    ini_set('display_startup_errors', 1);

    That will enable errors to be output to the screen. Then try to create or edit a category and see what happens. The other is to check the osTicket error log in the admin area.

    Once youve finished testing change the values back to 0.

    Tim

     
  • Stead Halstead

    Stead Halstead - 2013-10-14

    Thanks for the response Tim!

    Different browsers produce the same effect.

    No errors displayed while adding a new category with main.inc.php

    No errors in Admin Panel -> System Logs. Log level is currently set to to Debug.

    Strange! It appears to be convinced that nothing is going wrong!

    We'll upgrade to 1.7.2 and post back if that changes the situation at all.

    Thanks!

    -Stead

     
  • Anonymous

    Anonymous - 2013-10-23

    I upgraded to 1.7.2, did a new install of osFAQ , but am still having no luck. Here's my post data when I submitted category "Stead":

    CSRFToken 1c278aa3e1913c5784cc9bf01f2cb413b91bccd0
    categories_date_added 2013-10-23
    category Stead
    category_status 1
    featured 1
    parent_id 0

    Looks good! Unfortunately, the category name is still coming through as a blank entry in when the page redirects. phpMyAdmin is showing this as well.

    Is there a place I can echo the fully constructed SQL statement and track back from there?

    Thanks!

    -Stead

     
  • Stead Halstead

    Stead Halstead - 2013-10-23

    (whoops! That anonymous post was from me too).

    I upgraded to 1.7.2, did a new install of osFAQ , but am still having no luck. Here's my post data when I submitted category "Stead":

    CSRFToken 1c278aa3e1913c5784cc9bf01f2cb413b91bccd0
    categories_date_added 2013-10-23
    category Stead
    category_status 1
    featured 1
    parent_id 0

    Looks good! Unfortunately, the category name is still coming through as a blank entry in when the page redirects. phpMyAdmin is showing this as well.

    Is there a place I can echo the fully constructed SQL statement and track back from there?

    Thanks!

    -Stead

     
  • Stead Halstead

    Stead Halstead - 2013-10-23

    Ta da! Our programmer found the issue - the category name was being submitted via http, rather than HTTPS (which we are using for our OSTicket site). Ah ha!

    Changing the osFAQ settings to use SSL to true fixes this, but I had to change it directly in the database. For some reason, only on the SSL option, the right column collapses and isn't available (see attachment).

    Woo hoo!

     
  • Tim Gall

    Tim Gall - 2013-10-24

    Nice work. Sorry I wasnt more help on this.

    Will see what I can do about the side col issue with the SSL setting. At the moment the SSL setting checks for installed SSL using curl functions and disables the setting if SSL isnt found (and probably if curl isnt installed or working). I put in the restriction to stop people from accidentally making the site unreachable if they didnt have SSL installed (mainly as a preemptive safety precaution). No doubt thats whats causing the problem you were having with the SSL setting.

    Regards,
    Tim

     

Anonymous
Anonymous

Add attachments
Cancel