@EIJason

So I made a fork of your osticket intallation and I made those certain changes.

Which repo did you fork? My repo at JediKev/osTicket or the main repo at osTicket/osTicket? If I were you I would fork the main repo at osTicket/osTicket as this is always the most up-to-date. I very rarely keep my base branches up-to-date in my public fork, only on my local clones. The 1.14.x series used to be on develop-next but now it is on develop, so I would use this branch to stay up-to-date with the latest changes.

Now I was under the impression that when you make changes to the your osticket my fork is automatically updated.

Now this is not entirely true. Most of the time you will need to clone your fork somewhere locally $ git clone <clone-url>, add osTicket as a remote via $ git add remote <remote-name> <main-repo-url>, fetch the latest changes via $ git fetch <remote-name>, and then merge the fetched branch to your local clone via $ git merge <remote-name>/<branch>. Here is an example:

$ git clone https://github.com/your/fork.git
$ cd <cloned-project-folder>
$ git checkout develop
$ git add upstream https://github.com/osTicket/osTicket.git
$ git remote -v (to see a list of remotes)
$ git fetch upstream
$ git merge upstream/develop (make sure you are on the develop branch first with `$ git checkout develop`)

So I copied the whole of my OSTicket fork back over my live files but the version didnt update?

If you are going to use a Git clone then it will always show the version like that. The only time it will show the actual version number is if you either package osTicket or use the downloads from our site or the Github Releases page.

Cheers.

KevinTheJedi The only time it will show the actual version number is if you either package osTicket or use the downloads from our site or the Github Releases page.

Side note: This is why i recommend using the download from osticket.com/download

EIJason So how do I update my osticket to the latest version and keep the changes I made?

You could setup a repo to track your changes and merge them after each upgrade.
Most of the mods I run have been shifted to plugins to avoid having to modify the core files each upgrade.

I'm really a github novice and do not really use it much. You will want @KevinTheJedi to respond to this one.

@EIJason

A good way to tell is by doing $ git log and looking at the latest commit locally. Then you go to the branch in Github and see what the latest commit was on that. Then you compare the two to see if you are up-to-date.

Cheers.

@EIJason

I second @ntozier. Unable to read from file means that it cannot read the file either due to permissions/ownership issues or the file is simply not there.

Cheers.

I haven't used this plugin for years... but when i did I used the absolute path.