Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

ost-config.php is not in /Include directory

Hello,

I'm running OSTicket v1.9.5.1. I inherited this installation. I did do an upgrade a year or two ago and had problems but the upgrade eventually went through, how I don't know. The problem I'm seeing is that there isn't an ost-config.php in the /Include directory, only the sample file. The actual config file is located in the root directory and is named ostconfig.php. Who ever initially installed this had to of made some modifications right? Where is the pointer to the config file? Where does it tell what the name of the config file is and where it is located? I'd like to get this back to a standard install. 

Comments

  • edited August 1
    ostconfig.php is the old file.   Simply move it to the /include folder (rename it) you should be good to go.
  • This is my post from the last upgrade I did. I would like to get this back to a standard install and have the 
    ost-config.php config file used instead of the ostconfig.php located in the root directory.

    http://osticket.com/forum/discussion/83968/trying-to-upgrade-from-1-6rc4-to-latest-version#latest

    Thanks,
  • Then I have no idea what it is that you are trying to ask.

    The standard install has a ost-config.php in the /include directory.
  • Hi ntozier,

    There is no ost-config.php in the /include directory. There is an ost-sampleconfig.php file in the /include directory but no ost-config.php file. In the root directory of the install there is an ostconfig.php and this has all the database information, just like the ost-config.php file should have. The installation is reading the ostconfig.php in the root and not an ost-config.php file in the /include directory. There isn't any ost-config.php file anywhere.

  • Please see my first reply to this thread.
  • Sorry I missed that ntozier

    1. Backup, backup, backup
    2. Upload current version overwriting old files
    3. Move ostconfig.php to /include directory and rename to ost-config.php
    4. Login and the upgrade installer should kick off.

    Sound about right?

    Thanks,
  • Yupper. :)
  • side thought: What version of PHP do you have installed?  You probably want to upgrade to 5.6 if you aren't running it already.
  • PHP - 5.5.9-1ubuntu4.21 (apache2handler)
    MySQL - 5.5.57-0ubuntu0.14.04.01

    Those are my versions
  • You might want to upgrade PHP to 5.6, it's the version that osTicket works the best with currently, but that version should be okay.
  • Hello,

    So I went through with the upgrade from 1.9.5.1 to 1.10 as I had planned out

    1. Backup, backup, backup
    2. Upload current version overwriting old files
    3. Move ostconfig.php to /include directory and rename to ost-config.php
    4. Login and the upgrade installer should kick off.

    A couple of things, after copying the files and moving and renaming ostconfig.php to ost-config.php in the /Include directory, the admin page would not load. I had to put the full path to the upgrade.php file. Once I did that the upgrade went through. That's fine, as long as it went through and it did. Was able to get the ostconfig.php file moved to the /Include directory and renamed to ost-config.php. What I lost was the formatting of the landing page for clients. The layout is somewhat different and the size is much smaller. Is there a directory I can copy back over to get my old  formatting back?

    Thanks,
  • Depends what you mean mate, have you got a screenshot showing the problem?
  • I've attached a "Before" and "After" screenshot.

    Thanks
    Before Upgrade OSTicket.jpg
    827 x 409 - 54K
    After Upgrade OSTicket.jpg
    813 x 418 - 40K
  • Mine looks like that too. Must have been part of the upgrade.

    You can edit that page a bit in the admin panel -> Manage -> Pages -> Landing

    However the placement of the buttons isn't an option there.
  • Guess I'll have to become a Web Developer :-)

Sign In or Register to comment.