Hi,I have an osticket installation of 1.7.3 that I am attempting to upgrade and have staged a separate debian wheezy box for testing purposes.  We have all of the dependencies installed and can load the original 1.7.3 site on this box.  We've downloaded the 1.8.1.2 zip and extracted the contents of the upload folder from this zip directly into the docroot.  Once we hit reload, we are then greeted by an installer (with empty fields), not an upgrader tool.  Our ost-config.php is intact.Any ideas?Thanks!

Meant to add that all attempts to hit /scp/ & /setup/upgrade.php get redirected to /setup/install.php.  

ok, this is bizarre.  i've gone through this exercise of restoring a working installation of v1.7.3, and extracting the contents of the 'upload' dir into the document root of our osticket installation to re-attempt an upgrade 1.8.1.2 and now i'm in a constant state of being unable to authenticate on the newer version.  when I restore 1.7.3, I can get back in, after upgrading, i cannot.   i am going to outline my exact steps for transparency1.7.3 docroot:   /var/www/osticket    (rsync'd over from our production installation)I keep the contents of the zipfile in a staging directory so that i can reuse it as needed:cd /var/www; mkdir staging; unzip -d staging osTicket-v1.8.1.2.zip; chown -R www-data.www-data staging1.7.3 loads normally, here is a screenshot of our settings page (/scp/settings.php): http://imgur.com/Gq3LgvRUpgrading our 1.7.3 installation to 1.8.1.2:cd /var/www/osticketcp -af ../staging/upload/* .less include/ost-config.php   <---confirm SECRET_SALT, ADMIN_EMAIL & db settings still intactThen when I reload /scp/settings.php, I am asked to log in and subsequent authentication attempts fail.  I've tried this with different browsers, cleared cache, etc to no avail.No errors are in the apache2 logs, and development tools shows no issues with the page loads.  The self help troubleshooting edits don't seem to apply to 1.8.1.2.  Those configurables were available in the main.inc.php for 1.7.3, which was overwritten by the zip file extraction, so I don't have any additional debugging info for php unfortunately.System info:cat /etc/debian_version 7.5apt-show-versions | egrep "php5-|mysql|apache2"apache2-mpm-prefork/wheezy uptodate 2.2.22-13+deb7u1apache2-utils/wheezy uptodate 2.2.22-13+deb7u1apache2.2-bin/wheezy uptodate 2.2.22-13+deb7u1apache2.2-common/wheezy uptodate 2.2.22-13+deb7u1libapache2-mod-php5/wheezy uptodate 5.4.4-14+deb7u9libdbd-mysql-perl/wheezy uptodate 4.021-1+b1libmysqlclient18/wheezy uptodate 5.5.37-0+wheezy1mysql-client-5.5/wheezy uptodate 5.5.37-0+wheezy1mysql-common/wheezy uptodate 5.5.37-0+wheezy1mysql-server/wheezy uptodate 5.5.37-0+wheezy1mysql-server-5.5/wheezy uptodate 5.5.37-0+wheezy1mysql-server-core-5.5/wheezy uptodate 5.5.37-0+wheezy1php5-cli/wheezy uptodate 5.4.4-14+deb7u9php5-common/wheezy uptodate 5.4.4-14+deb7u9php5-curl/wheezy uptodate 5.4.4-14+deb7u9php5-gd/wheezy uptodate 5.4.4-14+deb7u9php5-gmp/wheezy uptodate 5.4.4-14+deb7u9php5-imap/wheezy uptodate 5.4.4-14+deb7u9php5-ldap/wheezy uptodate 5.4.4-14+deb7u9php5-mcrypt/wheezy uptodate 5.4.4-14+deb7u9php5-mysql/wheezy uptodate 5.4.4-14+deb7u9The contents & md5 checksums of the files in our /var/www/osticket directory after the contents of the 1.8.1.2 upload directory have been extracted directly into it:  http://pastebin.com/HT6AgReD

Sounds to me like you did something wrong.

eureka, we have had a break through.  in order to be able to authenticate after the upgrade, i had to disable our ldap plugin for 1.7.3, upgrade to 1.8.1.2 and using the github repo as opposed to the zipfile on osticket.com.  feel free to close out this thread.

Write a Reply...