ntozier the version of osticket is v1.11.0-rc1.This is the latest version currently available.
The version of php is php7.0, before I used osticket version v1.10.4, I recently updated this month to version 1.11.0 . I identified this problem, when I create ticket and I close at the same time with image in the input of the answer like this
there is a problem and without image on the input answer there is not a problem, the error is generated by osticket when I put image is :

This error for example :
Fatal error: Uncaught exception 'OrmException' with message 'Call to undefined method QuerySet::merge' in /var/www/html/osticket/include/class.orm.php:1526 Stack trace: #0 [internal function]: QuerySet->call('merge', Array) #1 [internal function]: QuerySet->merge(Object(InstrumentedList)) #2 /var/www/html/osticket/include/class.orm.php(2211): call_user_func_array(Array, Array) #3 /var/www/html/osticket/include/class.ticket.php(4114): InstrumentedList->call('merge', Array) #4 /var/www/html/osticket/include/class.ticket.php(4114): InstrumentedList->merge(Object(InstrumentedList)) #5 /var/www/html/osticket/scp/tickets.php(410): Ticket::open(Array, Array) #6 {main} thrown in /var/www/html/osticket/include/class.orm.php on line 1526

or error on the image :

osTicket 1.11.0 has not been released... so I would recommend that you restore the database and site from backup.

  • sipe replied to this.

    ntozier I think that osticket-1.11 has been released

    1.11.0 has not been released. 1.11-rc1 which is a release candidate for testing has. RC's should never be run in a production environment. Consider them buggy Beta releases.

    • sipe replied to this.

      ntozier thank you for your answer, to search with me. But that did not solve my problem, I still have the same issue.

      If you insist on running a buggy RC then I would recommend that you update to the latest 1.11 from github. There are a ton of bug fixes and such that you can get from there. Otherwise please revert to 1.10.4 or wait until 1.11 is released.

      ramrajone thank you for your answer, to search with me. But that did not solve my problem, I still have the same issue.

      I have news information about this problem. the real problem is that every time we put an image at the level of the ticket response the error is generated. Please help me to solve this problem, I need your help, I'm still looking.

        sipe I suppose if you are not running a stable release no support will be provided or guarantee.

        sipe
        can you try this
        https://github.com/osTicket/osTicket/commit/d8abe105ec04b7750fcd119bf79edb2b01808cd7

        edit: include/class.thread.php

        change from:
        function getClean() { function getClean() {
        return Format::htmlchars(Format::stripEmptyLines(parent::getClean()), true);

        To this:
        function getClean() {
        return Format::htmlchars(Format::stripEmptyLines(parent::getClean()), true); return Format::htmlchars(Format::html_balance(Format::stripEmptyLines(parent::getClean())));

        good evening, for my problem I just saw that the stable version of osticket v1.11 came out yesterday.

        But my problem is not solved. just that it does not send the error, its shows that the ticket has been sent but when I look in the created tickets it does not display. So the ticket is not created.

        Look at your ost_ticket table. Is the ticket there?

        Your response does not actually answer my question. Look at your database, specifically the ost_ticket table. Is the ticket there?

        • sipe replied to this.

          ntozier yes in the database, the ticket is created, but I do not see it when I go on the ticket page of osticket.

          Sorry for the inconvenience, thanks for all your interventions, the stable version of osticket v1.11 has solved my version v1.11.0-rc problem. After upgrading to stable v1.11, the problem is that after creating the ticket with the image in the response field, I was looking for the ticket in open tickets rather than closed tickets. While I closed the ticket

          It sounded to me like if the ticket is in the database then it was created and you just did not have permission t osee it... but looking in the wrong place makes sense too.

          • sipe replied to this.
            Write a Reply...