Skip to content
Snippets Groups Projects
  1. Jul 09, 2019
  2. Jul 03, 2019
    • JediKev's avatar
      issue: Search Reindexing Thread Entries · bbf1010c
      JediKev authored
      This addresses an issue where `IndexOldStuff()` doesn't reindex everything
      it's supposed to. The reindex leaves out all of the Thread Entries with
      empty titles or bodies. This is due to the SQL statement that retrieves
      thread entries. In the SQL statement, we check if the sum of the Thread
      Entry Title length and the Thread Entry Body length is greater than 0. If so
      we reindex the entry, otherwise we exclude it. The problem is both
      ```LENGTH(A1.`title`)``` and ```LENGTH(A1.`body`)``` can return `NULL` and
      you cannot add `NULL` (a string) to an integer. This updates the SQL to add
      `IFNULL()` statements around the possible `NULL` values so that if `NULL` we
      typecast to integer of 0 which can be added to integers successfully.
      bbf1010c
  3. Jul 01, 2019
    • aydreeihn's avatar
      Reformat Incorrect Reply-To Headers · e9dda94a
      aydreeihn authored
      In the event that we receive an email where the reply-to header is formatted with the name being an unquoted email, we should correct the name by inserting the quotes.
      
      Incorrect Format:
      adriane@enhancesoft.com <adriane@enhancesoft.com>
      
      Correct Format:
      "adriane@enhancesoft.com" <adriane@enhancesoft.com>
      e9dda94a
  4. Jun 28, 2019
    • JediKev's avatar
      issue: ISO-8859-8-i Charset Issues · 4da0324b
      JediKev authored
      This addresses an issue where emails with `ISO-8859-8-i` character-sets
      appear as "(empty)" in the system. This is due to `ISO-8859-8-i` not being a
      valid character-set for `iconv()`. When you pass `ISO-8859-8-i` to `iconv()`
      you will receive an error similar to `iconv(): Wrong charset, conversion
      from 'ISO-8859-8-i' to 'UTF-8//IGNORE' is not allowed`. I don’t know why
      it's not a valid character-set for `iconv()` but the trailing `-i` is used
      to say "keep the text in logical order instead of visual order". Logical
      order just means to keep the text in true right-to-left format instead of
      transcoding the characters to left-to-right format.
      
      This adds a new case to the `Charset::normalize()` switch statement to match
      against `ISO-XXXX-X-i`. If a character set matches the criteria we will
      remove the trailing `-i` and set the charset to `ISO-XXXX-X`. This charset
      format is valid in `iconv()` which will return the correctly formatted email
      instead of "(empty)".
      4da0324b
    • Peter Rotich's avatar
      Merge pull request #4907 from aydreeihn/issue/empty-list-item-extra · 40ad7c2a
      Peter Rotich authored
      Empty extra in list_items
      40ad7c2a
    • Peter Rotich's avatar
      Merge pull request #4902 from JediKev/issue/account-registration-throws-errors · e4cb4e98
      Peter Rotich authored
      issue: Account Registration Throws Errors
      e4cb4e98
    • Peter Rotich's avatar
      Merge pull request #4901 from JediKev/issue/retained-deleted-listitem-errors · 14bfc4cb
      Peter Rotich authored
      issue: Retained Deleted ListItem Errors
      14bfc4cb
    • Peter Rotich's avatar
      Merge pull request #4931 from JediKev/issue/iframe-single-quotes-devnext · 98860344
      Peter Rotich authored
      issue: iFrame Single Quotes
      98860344
    • JediKev's avatar
      issue: iFrame Single Quotes · 4b59b4f0
      JediKev authored
      It's all about the single quotes baby! Apparently I can't read; the single
      quotes are only meant for word options such as `'self'` and `'none'`. When
      adding single quotes to the `<host-source>` options it takes them
      literally…too literally. For example, if your options are `'localhost:80
      localhost:8080 localhost:8000'` then `'localhost:80` and `localhost:8000'` will
      be seen as "invalid" due to the single quotes. This removes the single
      quotes from every line that sets the CSP so all options are valid. This also
      adds single quotes around the `self` option so it stays valid as well.
      4b59b4f0
    • Peter Rotich's avatar
  5. Jun 13, 2019
  6. Jun 11, 2019
    • aydreeihn's avatar
      Issue: Ticket Alerts vs Dept Recipients · 581f1f9c
      aydreeihn authored
      If an alert is enabled for only the Department Manager and the Department Recipients field is set to No one, the Department Manager still receives a notification.
      
      If the recipients field is set to no one, nobody should receive an alert regardless of what is checked on the New Ticket Alert selections.
      
      To fix this, we can do a count of what the getMembersForAlerts function returns. This function compares what is set for a Department's group_membership in the database to the ALERTS_DISABLED constant to return a query set of members that should receive an alert. If the count is 0, we know that alerts should be disabled.
      581f1f9c
  7. Jun 03, 2019
    • Jared Hancock's avatar
      task: Implement edit of task thread · 394ddee8
      Jared Hancock authored
      This fixes an issue where, for task threads, if an agent has the thread edit
      permission, the agent was neither able to edit his or her own entries, nor the
      entries of other agents.
      394ddee8
  8. May 29, 2019
    • aydreeihn's avatar
      Empty extra in list_items · 1309a6c7
      aydreeihn authored
      If you have a custom field that's based on a list and the default value is set to a list item where the extra field is empty ('') instead of NULL, you cannot set the default value back to 'Select a Default'. You CAN set it to other default values
      
      Extra is set to empty if you erase the abbreviation and save it. Should save as NULL instead of empty
      
      Note: for some reason this didn't work
      
      if ($k == 'abbrev' && empty($vars[$k]))
                      $this->set($v, NULL);
      1309a6c7
  9. May 23, 2019
    • JediKev's avatar
      issue: Account Registration Throws Errors · a7205073
      JediKev authored
      This addresses issue 4898 where a User that clicks the ticket link in an
      email alert to view the ticket, in that ticket view clicks the link to
      register for an account, fills out the registration form, and clicks Create
      will throw a an "Unable to register account. See messages below." error.
      When the Users get this error there are no messages below so they can't see
      anything to fix which prevents them from creating an account. This is due to
      the email field being disabled which means the value is not sent in POST so
      the system thinks the User sent no email address which throws a hidden
      "Email field required." error. We disabled the email field to prevent an
      attacker from accessing the user’s guest login and registering the user with
      a different email (possibly his own). This sets a POST value called 'email'
      to the client's email so that the registration process acknowledges and
      validates the email allowing registration to continue.
      a7205073
  10. May 22, 2019
    • JediKev's avatar
      issue: Retained Deleted ListItem Errors · a3297a25
      JediKev authored
      This addresses an issue where New Tickets will fail for Users with a deleted
      ListItem retained in their Contact Information form. This is due to the
      system deleting the `list_id` for the ListItem so when we run
      `getFilterData()` for the User we can't find the list which causes a fatal
      error later down the line. This adds an OR statement to the
      `SelectionField::getFilterData()` method to skip said ListItems if no
      `list_id` is present.
      a3297a25
  11. May 15, 2019
  12. May 10, 2019
  13. May 09, 2019
  14. Apr 30, 2019
Loading