Forum Replies Created
-
In reply to: OS 1.11 Advanced Search not display values
March 29, 2019 at 1:24 pm #3407stevland
KeymasterHi @Absolute,
Thank you very much for taking the time to post your screenshot… it made this very easy to understand and fix.
The fix will be integrated into the next release (osTicket-Awesome-1.11-v1.1).
If you would like a quicker solution please add the following to /osta/user-styles.css:
.advanced-search .adv-search-val .select2-container--default .select2-selection--multiple .select2-selection__rendered {
height: initial !important;
}In reply to: osTicket 1.10.5 and 1.11 have been released
March 29, 2019 at 1:02 pm #3399stevland
KeymasterThanks for your support everyone!
In reply to: osTicket 1.10.5 and 1.11 have been released
March 29, 2019 at 12:56 pm #3393stevland
Keymasterany advice on how to properly upgrade the theme [from 1.10.x to 1.11.x]?
Hopefully you still have a separate osTicket core installation. You’ll need to upgrade that installation to osTicket v1.11 using the standard instructions provided by Enhancesoft. By doing so you will upgrade your database and prepare it for the new features that are included in v1.11.
Assuming your osTicket Awesome installation is in a directory called /support, rename it to /support-backup.
Create a new directory called /support.
Upload the files from the osTicket-Awesome-1.11-v1.0 release into the /support directory.
Copy your ost-config.php file from /support-backup/include to /support/include.
Enjoy!
In reply to: Glitches in 1.10.2-v1.0 and 1.10.4-v1.0
March 29, 2019 at 12:44 pm #3391In reply to: Footer colours
March 29, 2019 at 12:34 pm #3389stevland
KeymasterHmmm. Try this…
html,
#osticket,
#ostawesome,
#footer {
background: <your color here> !important;
}In reply to: 1.11.1 and IE11 Display issues or Compatibility
March 21, 2019 at 2:48 am #3327stevland
Keymasterhaha.. unfortunately so..
In reply to: 1.11.1 and IE11 Display issues or Compatibility
March 20, 2019 at 5:33 am #3314stevland
KeymasterI second this issue.. ie11 is a highly used browser so for this not to work is a real issue.
In reply to: Loading Page on Ticket Creation Missing
March 17, 2019 at 4:25 pm #3240stevland
KeymasterIf you’re interested, I just released osTicket-Awesome-1.11-v1.0.
In reply to: Open Calls – Back to Open Calls
March 15, 2019 at 5:57 pm #3225stevland
KeymasterThat sounds very odd. The Open link should always be there. But you can always click your company logo to get back to the main list of Open Tickets as well.
In reply to: Loading Page on Ticket Creation Missing
March 15, 2019 at 5:53 pm #3222stevland
KeymasterTruthfully, I am still struggling with this one.
I understand what the issue is but I haven’t figured out a resolution (yet).
I am working very hard to get some new releases for 1.11.x out the door and then this will become my top priority to resolve.
Thank you for your patience on this guys.
In reply to: French trad error
March 15, 2019 at 5:51 pm #3219stevland
KeymasterThanks for reporting this. But, unfortunately, this is an issue with osTicket’s language pack and can only be properly fixed through the following channel:
In reply to: Color priority and change priority
March 15, 2019 at 5:47 pm #3216stevland
KeymasterI’m sorry for the delay in responding!
While I am not sure what is causing this glitch on your end, all of this code has had to be reworked for 1.11.x.
Please upgrade to the next osTicket Awesome release when it becomes available next week and it will likely fix the issue.
In reply to: Feature removed in awesome osticket
March 15, 2019 at 5:44 pm #3214In reply to: DB Error #1146
March 15, 2019 at 5:41 pm #3211stevland
KeymasterAh, yes.
The ability to change the ticket priority from the ticket list is an osTicket Awesome-only mod that has been troublesome. It is being removed temporarily from the next release and will return better than ever in a future release… with a no db-error guarantee!
In reply to: unreadeable search results list on mobile
March 15, 2019 at 5:33 pm #3208stevland
KeymasterThank you for taking the time to post this screenshot.
This issue will be fixed in the next release.