Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

[resolved] osTicket v1.10 - Closed Ticket will not show details when single ticket is clicked.

When the closed ticket list is selected and a specific ticket is clicked for details, the details do not show.
When the ticket is reopened, the details are then visible.
This is the display.
The error is consistent.

Particulars
php v5.5.11
Windows Server 2012 w/IIs



Where should I start looking?
Thank you

Comments

  • Can you provide a screen shot please?
  • I am experiencing this issue as well. If you close the ticket, it moves to closed as planned. If you try to view the details, the page is blank. I saw that this might be a group membership issue, but I am a member of the group that the ticket belongs to. I cannot upgrade until this issue is resolved.

    Ubuntu 16.04
    Apache2
    php 5.6
    osticket v1.10.1
    image


    image


    image


    image


    image


    image
    2017-09-20_1018.png
    920 x 374 - 44K
    2017-09-20_1019.png
    1348 x 200 - 41K
    2017-09-20_1020.png
    1272 x 508 - 50K
    2017-09-20_1021.png
    1088 x 206 - 50K
    2017-09-20_1022.png
    1472 x 732 - 185K
    2017-09-20_1023.png
    1458 x 634 - 161K
  • Please consult your Apache and PHP error logs and provide any errors that are being logged.
  • /var/log/apache2 error.log

    [Wed Sep 20 10:48:01.259531 2017] [:error] [pid 2481] [client 10.1.7.254:64375] PHP Fatal error:  Uncaught exception 'ObjectNotUnique' with message 'One object was expected; however multiple objects in the database matched the query. In fact, there are 2 matching objects.' in /var/www/html/include/class.orm.php:1176\nStack trace:\n#0 /var/www/html/include/class.orm.php(545): QuerySet->one()\n#1 /var/www/html/include/class.list.php(297): VerySimpleModel::lookup(Array)\n#2 /var/www/html/include/class.list.php(384): DynamicList->getConfigurationForm(true)\n#3 [internal function]: DynamicList->getForm()\n#4 /var/www/html/include/class.list.php(112): call_user_func(Array)\n#5 /var/www/html/include/class.list.php(1327): CustomListHandler->__call('getForm', Array)\n#6 /var/www/html/include/class.list.php(1327): TicketStatusList->getForm()\n#7 /var/www/html/include/class.list.php(1143): TicketStatus->getConfiguration()\n#8 /var/www/html/include/class.ticket.php(300): TicketStatus->isReopenable()\n#9 /var/www/html/include/staff/ticket-view.inc.php(25): Ticket->isReopenable()\n#10 /var/www/html/scp/tickets.php(495): require_on in /var/www/html/include/class.orm.php on line 1176, referer: http://10.2.0.76/scp/tickets.php?id=31048
  • I spoke to a dev about this and he says:

    "He needs to check his `ost_form` table for duplicate types (type column) of `Lid` eg: `L12` or `L8`
    He needs to remove one of them (preferably the one not in use) from the table and his issue should be resolved."

    He seems to think that you have some dupelicate data
  • thoughts?
    image
    2017-09-20_1245.png
    1210 x 302 - 104K
  • row 7... L3 "Importance Properties" does not exist in my installation.
    My installation has L3 "Ticket Status Properties"
    I would write down all the information in the row 7 (in case you need it back later)
    and then remove it.
  • I modified row 7 to L4 for now and the data is visible. I will continue to test with the data updated as L4. So far so good. Thanks.
  • Very welcome.

    I'll mark this thread as resolved, but feel free to star ta new one or update this one if you have furhter issues with this.
  • Huh.
    Different but same problem shown in the SQL tables data as described above.

    Have two L1 in the type column of ost_form table
    L1 Ticket Status Properties
    L1 Ticket Default Template (HTML) Properties

    Changed L1 Ticket Default Template (HTML) Properties to L2.
    Data is now visible.

    Thank you

  • @TAS this is a resolved and closed thread.  You might want to start your own with your own specifics.
This discussion has been closed.