Just wanted to ask something similar.
    Is there a git release which I can pull in full, or do I have to patch every single part?

      crusader

      Not all patches are merged yet so you will need to apply manually. With this being said they will all be merged into develop once they are approved. We do not recommend using git branches in production as they can become unstable; we develop and merge into develop branch, test, and then push it to a tag once it’s ready for packaging.

      Cheers.

        17 days later

        Seems some of the patches are causing collisions, is there a specific order, I have to apply the patches in?

        Tinnitus
        I've tried it with those patches, seems they have been applied correctly, yet it still does not display the php site correctly.

          @crusader

          So after reviewing your error messages again I see that your site is actually running PHP 8.1 when v1.16.1 REQUIRES PHP 8.0.

          /var/www/localhost/htdocs/osTicket.new # **php8.1 index.php**
PHP Warning: ...

          You will need to downgrade PHP to 8.0, keep the changes applied, and retest.

          Cheers.

            KevinTheJedi I already downgraded to 8.0.x and still have the same issue, yet this time I don't even see the error messages anymore

              Did you see my comment about the order of how the patches have to be applied?
              Cause I'm not sure if I messed up something. When I start from the bottom, it gives me a collison with the third or fourth patch.

              @crusader

              Not really, I would start from oldest first though. If you get collisions then simply resolve them and move to the next one.

              Cheers.

              I used the latest DEV branch now, and it seems whatever was merged into that, worked. Finally got the upgrade done and seems to be working so far.
              Thank you for your help

              Write a Reply...