Osticket: New or editing notes is broken

Created on 18 Sep 2019 · 10Comments · Source: osTicket/osTicket

Prerequisites

[ ] Can you reproduce the problem in a fresh installation of the "develop" branch?
[X] Do you have any errors in the PHP error log, or javascript console?
[X] Did you check the osTicket forums?
[X] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report

Description

Problem with the notes since upgrading to the latest version of osticket-develop (presumably very similar to 1.14rc1). Organisation notes are broken.

Steps to Reproduce

Click organisation
Click on notes
Edit existing note

Expected behavior:
Same behaviour as before. Edit by default opens up in WYSIWYG editor, then option to change to code mode, then ability to save is displayed. Ideally an option to undo changes or at least see the changes made too (this is a sneaky attempt to add a brilliant option to notes)

Actual behavior: [What actually happened]
Display is cut to small version, only shows up as code (no WYSIWYG editor mode) and no save button

Versions

osTicket Version | 1.14-git (5ea4fb5)
Web Server Software | Apache
MySQL Version | 10.3.18
PHP Version | 7.3.9

Source

TechCare-Aus

All 10 comments

@TechCare-Aus

I see you say you are using the develop branch but that branch actually correlates to 1.12-git. I think you meant you're using the latest from develop-next branch if you're using v1.14-rc1. 😉

I notice the same issue with v1.14-rc1 and I do believe it was due to the Redactor upgrade. We will look into this. 👍

Cheers.

JediKev on 18 Sep 2019

👍1

I see you say you are using the develop branch but that branch actually correlates to 1.12-git. I think you meant you're using the latest from develop-next branch if you're using v1.14-rc1. 😉

haha sorry mate. yes typo.

On a side note. When I've updated to the latest git on branch develop-next and go to information next to osTicket Version | 1.14-git (5ea4fb5) it tells me to upgrade. Is this due to it thinking that v1.14RC1 is a higher version?

TechCare-Aus on 19 Sep 2019

@TechCare-Aus

It’s just not in our dns yet as it’s an RC so it’s going to say that for now.

Cheers.

JediKev on 19 Sep 2019

@JediKev I can understand the RC not being in your DNS, but Git should be the latest version always surely? Or are you saying that this function only works with officially released versions?

TechCare-Aus on 19 Sep 2019

@TechCare-Aus - I was a little confused by @JediKev response as well. To answer you - it depends on which branch you pull.

master - latest stable release v1.12.2
develop - latest + bug fixes v1.12.2+
develop-next - upcoming release / new features / bleeding edge v1.14-rc1+

We of course don't recommend pulling from develop-next for production-use unless you like living on the edge... we're ironing out bugs and do indeed require upgrade since the next version comes with database patches. I think this is in essence what Kevin was pointing out, we are squishing as many bugs as possible before we cut the second release candidate.