I just checked Saturday's full backup and the values are the same.

I restored that backup, overwriting the upgrade attempt and everything is back to normal (with the prior TZ problem).

Did I miss a step in how I tried to upgrade from the 1.11 ZIP I downloaded from the repository?

    Version of PHP?
    Did you check your PHP error logs like I asked?

      tolistim

      1. Make sure you have a good backup of Database and files of osTicket
      2. Then put the system in the offline mode: by going to /scp/settings.php
      3. Download the new version from https://osticket.com/download/ and choose the osTicket Core, v1.11 (Latest Release)
      4. Upload to your server v. 1.11 and replace current files/folders from Upload folder from your downloaded, and exclude the script folder/files
      5. Make sure you have the correct permission, then go to the URL/SCP of the osTicket system and login, you should see osTicket Upgrader, make sure your Prerequisites are all good, if any errors correct it, then click Start Upgrade Now
        check this post for more details: https://howtohelpdesk.com/how-to-upgrade-osticket-to-1-11/

          ramrajone
          Sorted the php back to 7.2 and now I see the user note about being offline if I go to the main site page.

          But, if I try to login as an agent expecting to see the upgrade option, I receive the "valid CSRF Token required" message.

          As a test, I removed my ost-config.php file and (the setup folder is there from the 1.11 update) I get the install screen. So something is twisted in my config.php file, but that is unchanged from before the DST change.

          Also - the CSRF message is in the error.log, but there is nothing that seems unusual in the php logs.

              Completely cleared the local browser cache in Safari and Firefox and the same thing is returned.

              Launched a new Windows 10 VM and even tried from Edge.

                tolistim
                Not sure if this might fix your problem
                error: Valid CSRF Token Required OsTicket:
                then need to edit file class.ostsession.php round line 191
                catch (DoesNotExist $e) {
                $this->data = new SessionData([‘session_id’ => $id]);
                $this->data->session_data = “”;

                    ramrajone
                    Thanks, that fixes the CSRF token.

                    But ... it does not sort the DST issue with the agent's lock expiring immediately since the ticket lock is seen to be 1 hour old as soon as the agent starts typing. We were hoping that the change to PHP 7.2 would sort this, but no change.

                        tolistim
                        ?? not under DST issue mean? Can you give some details and screenshots

                          Write a Reply...