[stevland]

Hi @NIcholasjansen,

Add the following to /osta/user-styles.css

table.list tbody tr td {
    border-top: .1px solid #a6acaf !important;
}

Note that you’ll want to back up and restore this file when upgrading osTicket Awesome in the future.

[stevland]

Hi @mstrust,

Sorry for the late reply!

I recommend making a backup of your database before upgrading, just to be safe.

These instructions assume your osTicket Awesome installation is in a directory named /support

Create a copy of the /support directory called /support-old
# cp -a /support /support-old

Using your FTP pogram, upload the contents of the /upload folder to /support, overwriting any files.

That’s it. 

[stevland]

Hi @mcz_michalch.admin,

1. That is very odd.
   Do you experience the same issue when you go to the Theme page in the demo?
   What web browser are you using?
   What error message(s) appear in your web server logs when you try to change the theme?
2. When you try to edit the custom field by clicking the Edit icon, nothing happens. This is a glitch with osTicket itself, it is not an osTicket Awesome issue. I have opened a report with the osTicket devs and hopefully they will have a fix soon.
   In the meantime you can edit the ticket itself and then edit the contents of the custom field. 

[stevland]

Hi @bcrawley,

Thank you for your report.

But what you have stumbled upon is actually an osTicket issue — not a glitch introduced by osTicket Awesome.

Nevertheless I have submitted a bug report to the osTicket devs regarding this:
https://github.com/osTicket/osTicket/issues/5581

[stevland]

Hi @NIcholasjansen,

Please see the temporary fix I posted here:
https://osticketawesome.com/forums/topic/custom-form-fields-not-editable-v1-14-2/

[stevland]

Hi @netesi,

Hmmm. Exporting a ticket works in the demo. Does it work for you?

What exactly happens when you try to export a ticket in your own installation?

Are there any relevant errors in your logs around the time that you try to export a ticket?

What version of osTicket Awesome are you using?

What web browser are you using?

[stevland]

Hi @abcauto,

Yes, the Annotations tab has been intentionally removed in osTicket Awesome.

As osTicket Awesome uses its own specific layout for each type of the most common annotations, our design cannot accommodate extra random icons appearing here and there.

But thank you for your report!

[stevland]

A green screen? Hmmm. No, I have not seen that. There is absolutely nothing else on the screen?

Please open /scp/js/scp.js and ensure lines 1142 – 1152 are commented out.

Is the green the same color as the header or footer of in color theme? It sounds like the browser may be rendering part of the page and then crashing.

Are there any relevant errors in your logs around the time that the blank screen occurs?

[stevland]

Hi @JODellAgC,

Unfortunately, I don’t have a lot of familiarity with IIS servers. But I’m keen to help you find a solution.

Have you been using osTicket and/or osTicket Awesome for a long time, or is this your first time upgrading? 

Are there any verbose errors in the Event Viewer?

Please review the steps in the original setup instructions. Perhaps there is a step that needs to be repeated after upgrading.

After updating, please edit the scheduled task to ensure that the path to cron.php is still correct (although it should be the same as the cron.php doesn’t move).

Is it possible that there is a permissions issue? When you first set up the Scheduled Task, did you need to perform an additional step to allow the Task Scheduler to access the cron.php file?

Have you seen this?
https://forum.osticket.com/d/1148-cronphp-doesnt-seem-to-work

I hope these ideas help you find a solution. Please let me know either way.

[stevland]

Hi @skyler360,

Hmmm. I can’t find an issue. Deleting a ticket works as expected in the demo.

Please help me understand the problem you are seeing.

Is it in the Client or the Staff side?

Does it happen when you delete the ticket from the Ticket List, or when you are editing an individual Ticket?

What version of osTicket Awesome are you using?

Thanks.

[stevland]

Actually, that ended up messing with the normal ticket layout. But I found another fix. And display:contents is a useful property to know. 🙂

[stevland]

dot green no reply button in client side, is moving in left

This is an intentional design decision for the Client side. All the rest will be fixed in the next release. Thank you.

[stevland]

@visimitra,

That is an amazing fix. THANK YOU!

[stevland]

Sorry for your trouble, and thank you for taking the time to report this. We’ll look into it and have a fix soon.

[stevland]

Hi guys, sorry for the late reply.

This will be fixed in the next release.

For now, please open /include/staff/ticket-view.inc.php in a text editor and change line 1000 from

<a class="inline-edit" data-placement="bottom" data-toggle="tooltip" title="<?php echo __('Update'); ?>"

to

<a class="ticket-action inline-edit" data-placement="bottom" data-toggle="tooltip" title="<?php echo __('Update'); ?>"