@EIJason

This is a known issue, in which I already have a patch to fix. Do you know how to rebuild our plugins? If so I can post the patch for you. If not, you’ll have to wait until I can throw together a rebuilt plugin with the patch applied or just wait until a new build is released on the site.

Cheers.

@EIJason

you mean build the phar files? Is it a standard thing?

No, it's not standard as we package them differently than most. I will have to put together a build for you and post it here when I'm done.

Cheers.

@EIJason

On Another note our biggest problem is editors... we cannot replicate HTML Copies of Tables or Office copies of tables... pretty frustrating...

Do you have raw examples you can post? Put the example(s) in a code block so the code isn't interpreted as actual tables on the Forum. Also, create a new discussion for this so we don't get separate issues mixed up here. Try copying a normal table with not a ton of styling, etc. and see if that works. Also, try pasting the table contents into Notepad, copy them from there and then paste to see if that works. Also, DON'T use IE (if you are) as IE is not supported by osTicket anymore.

the TinyHTML Editor is slightly better but there is allot to be done to make that work as it should with all the areas of osticket... (as a plugin of course) but I should put this in new post right?

We are completely changing the editor in v2.0 so that post will not be necessary.

Cheers.

@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.