[stevland]

Yup.

Upgrading from 1.9.x to 1.10.x required a database upgrade. As did upgrading from 1.10.x to 1.11. In both cases an osTicket Awesome user would need to upgrade osTicket itself.

1.11 to 1.12, however, does not require a database upgrade.

[stevland]

1.11 to 1.12 is a very straightforward upgrade.

1. Assuming your osTicket Awesome installation is in a directory named /support, rename it to /support-backup.
2. Upload the the 1.12 /upload folder, rename it to /support.
3. Copy over your /support-backup/include/ost-config.php file from  to /support/include/.

 

The upgrade is complete but unfortunately any osTicket Awesome settings will have to be manually recreated.

Incidentally the next release will move all settings into the database to simplify things going forward.

[stevland]

Sorry for the delayed response.

This will be fixed in the next release. In the meantime it is a very easy fix:

• open /include/staff/ticket-view-inc.php
• remove data-dropdown=”#action-dropdown-statuses” from line 93

[stevland]

Oh! I’ll look into this… thank you.

[stevland]

That’s great, glad its sorted.

[stevland]

Super!

[stevland]

Hi David,

Have you tried clearing your browser cache?

Would it be possible to zip (after stripping out ost-config.php and other files) your demo for 1.12 and make it available?

That is exactly what you have already installed. Something else has gone wrong.

If you would like me to look into this for you I will need you to create a temporary agent account (Admin Panel > Agents > Add New Agent) using info@osticketawesome.com. Be sure to give the account full administrative privileges.

[stevland]

Okay guys, make sure you add this code to /osta/user-styles.css exactly as below and you will no longer have images in the footer in desktop or mobile orientation:

#footer #osticket a,
#footer #ostawesome a {
    display: none !important;
}

If you don’t see the changes right away, be sure to clear your browser cache.

[stevland]

@mein-textiletikett.de,

Unless I am missing something, I don’t believe that osTicket has the ability to merge tickets.

https://forum.osticket.com/d/91904-how-merge-two-tickets-into-one

[stevland]

Hi @hunterrd,

It seems to be working on my end. Here are the steps I took to test using the demo database.

I have two tickets with the subject “Attachment test user”. One is open, the other closed.

Advanced Ticket Search > Keywords “Attachment test user” > TicketStatus / State > Is > Closed

The search results include the closed ticket and not the open one as expected.

—

I can’t help but wonder if your issue is actually with osTicket (rather than an issue specific to osTicket Awesome). But I am happy to investigate further if you can provide more information. How can I reproduce the issue?

[stevland]

Yikes!

Please open /include/staff/staff.inc.php and replace its contents with the source code.

[stevland]

The file exists exclusively for you to add your own CSS modifications. So — until you do — it is blank.

[stevland]

If you would like me to look into this for you I will need you to create a temporary agent account (Admin Panel > Agents > Add New Agent) using info@osticketawesome.com. Be sure to give the account full administrative privileges.

[stevland]

What browser are you using?

[stevland]

Hi guys,

I didn’t keep my promise… this wasn’t included in the 1.12 release after all. I will include something in the next release for sure.

In the meanwhile, you can easily add this functionality back by adding some CSS to your /osta/user-styles.css file.

 

The following code will display tickets with new replies in a darker text:

td[style="font-weight:bold"].osta_subject a {
color: #0c3d50 !important;
}

 

If you really want to go nuclear you can use a bold font instead:

td[style="font-weight:bold"].osta_subject a {
font-weight: 600 !important;
}