RT: Request Tracker

rt:5.0/remove-attachment-and-filename-icons

  1. Git
  2. lp:rt
  3. 5.0/remove-attachment-and-filename-icons
Last commit made on 2022-09-18
Get this branch:
git clone -b 5.0/remove-attachment-and-filename-icons https://git.launchpad.net/rt

Branch merges

Branch information

Name:
5.0/remove-attachment-and-filename-icons
Repository:
lp:rt

Recent commits

7888a6d... by Blaine Motsinger <email address hidden>

Remove attachment/filename icons from transactions

This commit removes the filename and attachment icons from ticket
history transactions, as well as cleanup the styling to fix the
alignment overlap in light and dark theme.

7310a29... by sunnavy

Merge branch '5.0/add-dashboard-list-to-email-cli' into 5.0-trunk

02b9e1e... by Jason Crome <email address hidden>

Support to specify dashboards for rt-email-dashboards

e271ef7... by Blaine Motsinger <email address hidden>

Fix LDAP filter string debug output

The filter variable in UserExists isn't a Net::LDAP::Filter obj
so fails the as_string method.

Additionally, search_filter is more correct since it contains the
final constructed filter.

a5ed0c8... by Jim Brandt

Merge branch '5.0/add-callback-showsummary-aftercustomfields' into 5.0-trunk

bcc532c... by Brian Conry <email address hidden>

Add AfterCustomFields callback to /Ticket/Elements/ShowSummary

7e0ee70... by sunnavy

Merge branch '4.4-trunk' into 5.0-trunk

434a45c... by Jim Brandt

Merge branch '4.4/message-attachment-original-content' into 4.4-trunk

af39698... by sunnavy

Test textual and UTF-8 encoded "message/..." attachments

It covers both cases where $TreatAttachedEmailAsFiles is true or false.

b122dc2... by sunnavy

Encode content for textual "message/..." attachments

If $TreatAttachedEmailAsFiles is true, message-like attachments wouldn't
be split into parts in RT database, in which case "OriginalContent"
could return decoded strings(with utf-8 flag on), which "ContentAsMIME"
doesn't like(it feeds OriginalContent to MIME::Body::Scalar) and could
cause the following warning(when there are some non-ascii chars):

    Strings with code points over 0xFF may not be mapped into in-memory file handles

Even worse, it dies if you stringify the returned MIME::Entity object:

    open body: Invalid argument at .../MIME/Entity.pm line 1897.

This commit fixes the issue by encoding content accordingly.