<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									osTicket Awesome Forum - Recent Topics				            </title>
            <link>https://osaweso.me/community/</link>
            <description>osTicket Awesome Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sat, 02 May 2026 15:45:57 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Email Fetching</title>
                        <link>https://osaweso.me/community/general-issues/email-fetching/</link>
                        <pubDate>Wed, 15 Apr 2026 07:18:30 +0000</pubDate>
                        <description><![CDATA[]]></description>
                        <content:encoded><![CDATA[]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>Jeremy Bernstein</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/general-issues/email-fetching/</guid>
                    </item>
				                    <item>
                        <title>Custom columns | Text overflow clipping not working</title>
                        <link>https://osaweso.me/community/bugs/custom-columns-text-overflow-clipping-not-working/</link>
                        <pubDate>Fri, 03 Apr 2026 00:52:56 +0000</pubDate>
                        <description><![CDATA[Hello,
There seems to be an issue when trying to utilize the custom column text overflow behavior options (Text wrap, Clipping, etc.), specifically the text clipping option.
Attached are the...]]></description>
                        <content:encoded><![CDATA[Hello,
There seems to be an issue when trying to utilize the custom column text overflow behavior options (Text wrap, Clipping, etc.), specifically the text clipping option.
Attached are the OSTA and native osTicket displays.
Also the preview tab would be a great addition.
Thank you in advance.<img src="https://osticketawesome.com/wp-content/uploads/hm_bbpui/25431/4f1nnf4heok0aerqtyvb2tmfy0d8tdyo.png" alt="osta-view" />&nbsp;<img src="https://osticketawesome.com/wp-content/uploads/hm_bbpui/25431/x6wt7wky6up54sp8xja8t3t33asn2xck.png" alt="osticket-view" />]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>Daniel Rosta</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/bugs/custom-columns-text-overflow-clipping-not-working/</guid>
                    </item>
				                    <item>
                        <title>Client reply editor builds invalid draft URL (.../ajax.php/draft/.../index.php)</title>
                        <link>https://osaweso.me/community/bugs/client-reply-editor-builds-invalid-draft-url-ajax-php-draft-index-php/</link>
                        <pubDate>Mon, 30 Mar 2026 02:59:12 +0000</pubDate>
                        <description><![CDATA[]]></description>
                        <content:encoded><![CDATA[]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>Carsten Bækmand</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/bugs/client-reply-editor-builds-invalid-draft-url-ajax-php-draft-index-php/</guid>
                    </item>
				                    <item>
                        <title>Task creation from ticket fails when Department is not selected (missing require</title>
                        <link>https://osaweso.me/community/bugs/task-creation-from-ticket-fails-when-department-is-not-selected-missing-require/</link>
                        <pubDate>Wed, 25 Mar 2026 12:28:23 +0000</pubDate>
                        <description><![CDATA[]]></description>
                        <content:encoded><![CDATA[]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>Carsten Bækmand</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/bugs/task-creation-from-ticket-fails-when-department-is-not-selected-missing-require/</guid>
                    </item>
				                    <item>
                        <title>Feature Request: Additional API endpoints</title>
                        <link>https://osaweso.me/community/suggestions-and-feedback/feature-request-additional-api-endpoints-125323/</link>
                        <pubDate>Tue, 17 Mar 2026 16:42:50 +0000</pubDate>
                        <description><![CDATA[Hi! New customer here. Love the product.

I&#039;m wondering if there is any interest in expanding upon the default osTicket API endpoints to include some new ones that allow access to things lik...]]></description>
                        <content:encoded><![CDATA[Hi! New customer here. Love the product.

I'm wondering if there is any interest in expanding upon the default osTicket API endpoints to include some new ones that allow access to things like general Client and Organization information, including custom fields we've created to capture CMS data. Would be great to read more than just specific ticket info via the API!]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>Michael Rebar</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/suggestions-and-feedback/feature-request-additional-api-endpoints-125323/</guid>
                    </item>
				                    <item>
                        <title>Dark mode no longer working, except for in the header</title>
                        <link>https://osaweso.me/community/bugs/dark-mode-no-longer-working-except-for-in-the-header-125278/</link>
                        <pubDate>Sun, 15 Mar 2026 16:59:13 +0000</pubDate>
                        <description><![CDATA[Hello,

Since I updated form 1.18.2 to 1.18.3 (rev4), the ticket list is no longer in dark mode.

I tried in a IN PRIVATE session, disabling/enabling dark mode.

osTicket v1.18.3 // osTicket...]]></description>
                        <content:encoded><![CDATA[Hello,

Since I updated form 1.18.2 to 1.18.3 (rev4), the ticket list is no longer in dark mode.

I tried in a IN PRIVATE session, disabling/enabling dark mode.

osTicket v1.18.3 // osTicket-1.18.3-Awesome-104

PHP 8.3.30 // MySQL 8.0.45 // Apache web server

Thank you.]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>cglmicro</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/bugs/dark-mode-no-longer-working-except-for-in-the-header-125278/</guid>
                    </item>
				                    <item>
                        <title>In the dialog box to open a new ticket, new fields are NOT opened.</title>
                        <link>https://osaweso.me/community/bugs/in-the-dialog-box-to-open-a-new-ticket-new-fields-are-not-opened-125258/</link>
                        <pubDate>Sun, 15 Mar 2026 08:05:07 +0000</pubDate>
                        <description><![CDATA[In the dialog box to open a new ticket, new fields are NOT opened.

After create new ticket this error shows.

&quot;Unable to create a ticket. Correct any errors below and try again.&quot;

And the r...]]></description>
                        <content:encoded><![CDATA[In the dialog box to open a new ticket, new fields are NOT opened.

After create new ticket this error shows.

"Unable to create a ticket. Correct any errors below and try again."

And the required fields "Ticket Details" is present and now possible to create the ticket.

V. 1.18.3 Firefox and Opera tested. Same problem on both!

&nbsp;

-Roger-

&nbsp;

&nbsp;

&nbsp;

&nbsp;]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>Roger Iverin</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/bugs/in-the-dialog-box-to-open-a-new-ticket-new-fields-are-not-opened-125258/</guid>
                    </item>
				                    <item>
                        <title>Request for API or HTTP Auth Download Option for Automated Updates</title>
                        <link>https://osaweso.me/community/installation/request-for-api-or-http-auth-download-option-for-automated-updates-125198/</link>
                        <pubDate>Sat, 07 Mar 2026 22:35:10 +0000</pubDate>
                        <description><![CDATA[We would like to ask if it is possible to download the latest version of osTicketAwesome using an API or HTTP authentication method.

Our goal is to automate our update process so that our s...]]></description>
                        <content:encoded><![CDATA[We would like to ask if it is possible to download the latest version of osTicketAwesome using an API or HTTP authentication method.

Our goal is to automate our update process so that our servers can securely download the newest version when it becomes available.

We have attempted to automate the process by performing a login through a script and then downloading the file, but the download page does not accept the session afterwards.

Is there a supported way to download the latest version programmatically while still authenticating with our username and password? For example:

API access
HTTP Basic Authentication
Token-based authentication
A direct authenticated download URL

We are not trying to bypass authentication; we simply want a secure and supported method to automate updates while still validating our account credentials.

Any guidance on how this could be implemented would be greatly appreciated.]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>Carsten Bækmand</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/installation/request-for-api-or-http-auth-download-option-for-automated-updates-125198/</guid>
                    </item>
				                    <item>
                        <title>CC users not visible when selecting multiple users</title>
                        <link>https://osaweso.me/community/bugs/cc-users-not-visible-when-selecting-multiple-users-125185/</link>
                        <pubDate>Sat, 07 Mar 2026 22:30:09 +0000</pubDate>
                        <description><![CDATA[I have just updated to version 104, and when I create a new ticket and select multiple users in the input field cc_users_open, I am not able to see all the users I have selected. As a result...]]></description>
                        <content:encoded><![CDATA[I have just updated to version 104, and when I create a new ticket and select multiple users in the input field cc_users_open, I am not able to see all the users I have selected. As a result, the users are listed outside of the input field.

This line of CSS from staff-desktop.css appears to be causing the issue:

.tickets-page .tickets .form_table .select2-container--default .select2-selection--multiple {
height: 32px !important;
}]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>Carsten Bækmand</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/bugs/cc-users-not-visible-when-selecting-multiple-users-125185/</guid>
                    </item>
				                    <item>
                        <title>disable advertise and color picker link in footer main page</title>
                        <link>https://osaweso.me/community/installation/disable-advertise-and-color-picker-link-in-footer-main-page-125144/</link>
                        <pubDate>Tue, 03 Mar 2026 07:37:26 +0000</pubDate>
                        <description><![CDATA[Hi there,

since the brand new version 1.18.3-Awesome-104 we get 2 links in the footer:

One on the left side: back to osticketawesome.
One on the right side: color theme picker.

So we dont...]]></description>
                        <content:encoded><![CDATA[Hi there,

since the brand new version 1.18.3-Awesome-104 we get 2 links in the footer:

One on the left side: back to osticketawesome.
One on the right side: color theme picker.

So we dont want this! How we can get rid that?&nbsp;

Thanks in advance!

&nbsp;]]></content:encoded>
						                            <category domain="https://osaweso.me/community/"></category>                        <dc:creator>bit111</dc:creator>
                        <guid isPermaLink="true">https://osaweso.me/community/installation/disable-advertise-and-color-picker-link-in-footer-main-page-125144/</guid>
                    </item>
							        </channel>
        </rss>
		