Skip to content
Snippets Groups Projects
  1. Oct 09, 2019
    • JediKev's avatar
      i18n: OpenSSL Error · af6f0e92
      JediKev authored
      This addresses issue 5095 where installing a Language Pack and visiting the
      Dashboard > Information page without OpenSSL installed/configured will throw
      a fatal error of `Call to undefined function openssl_pkey_get_public()`.
      This is due to no check for the `openssl` extension before the dependant
      method is called. This adds a check so that if OpenSSL is not available we
      can return a useful error code of `VERIFY_EXT_MISSING` (which is error code
      `2`) and continue without disrupting the content.
      af6f0e92
  2. Oct 08, 2019
  3. Oct 07, 2019
  4. Oct 04, 2019
  5. Oct 02, 2019
    • JediKev's avatar
      issue: Revert fefed147 · c9be2e00
      JediKev authored
      This addresses issue 5084 by partially reverting commit `fefed147`. In said
      commit, we updated `THIS_VERSION` to utilize `MAJOR_VERSION` which is fine.
      However, we also updated the deploy module to copy the same format. This
      interferes with the osTicket Version check by not including the entire
      subversion and not starting with a `v` (ie. `v1.12.3`). This reverts the
      copied format section of the commit so that `THIS_VERSION` will be the full,
      non-git version when deployed/packaged.
      c9be2e00
    • JediKev's avatar
      Add Release Notes for v1.12.3 · bcf1a6f1
      JediKev authored
      v1.12.3
      bcf1a6f1
    • Peter Rotich's avatar
      Merge pull request #5079 from JediKev/issue/mbstring-ext-requirement · 2e6d1e55
      Peter Rotich authored
      issue: Mbstring Extension Requirement
      2e6d1e55
    • JediKev's avatar
      issue: Mbstring Extension Requirement · 5a96884d
      JediKev authored
      This addresses an issue reported on the forum where printing a ticket in
      v1.12 and above requires `mbstring`. This updates the print call to check
      for the `mbstring` extension and if not loaded will fail with a detailed
      error `mbstring extension required to print ticket to PDF`.
      5a96884d
  6. Oct 01, 2019
  7. Sep 24, 2019
  8. Sep 23, 2019
    • JediKev's avatar
      issue: Complete Thread Var Padding (Outlook) · d96285f7
      JediKev authored
      This addresses issue 5007 where when using the complete thread variable
      there is no padding between thread messages in Outlook desktop app and makes
      the thread hard to follow. Outlook does not respect some CSS rules that are
      accepted in most (if not all) modern email clients. Since we can’t use
      normal CSS the workaround is to add a blank table row (with a single space)
      so that it forces "padding" between the end of a message and the start of
      another.
      
      Before
      (image)
      
      After
      (image)
      d96285f7
  9. Sep 20, 2019
    • JediKev's avatar
      issue: Revert 453e8152 · ddde34b0
      JediKev authored
      This addresses an issue where upgrading from v1.6 to a release on or after
      v1.12 will hang on login and eventually timeout. This is due to the system
      not being able to fetch the config which logs a db error which calls the
      config and continues the loop. For now, we need the config in the
      constructor so that the loop doesn't occur and we can continue to upgrade as
      normal.
      
      TODO:
      - For a permanent fix, we need to figure out why the loop occurs when not in
      the constructor and vice versa.
      ddde34b0
  10. Sep 19, 2019
  11. Sep 18, 2019
    • Peter Rotich's avatar
      Merge pull request #5054 from aydreeihn/issue/empty-due-date · d7120e97
      Peter Rotich authored
      Issue: Empty Due Date
      d7120e97
    • aydreeihn's avatar
      Issue: Empty Due Date · 30f3b553
      aydreeihn authored
      This commit fixes an issue that allowed Agents to clear the Duedate on a ticket using inline edit. We were saving the value 0000-00-00 00:00:00 to the database which the ticket would then display as 12/1/02 06:09 pm.
      
      Instead, if an Agent clears the Duedate field, we should save the duedate as null and the ticket should continue using the est_duedate.
      30f3b553
  12. Sep 17, 2019
    • JediKev's avatar
      issue: PHP 7.3 New Agent Set Password · 1bcd0e2f
      JediKev authored
      This addresses an issue reported on the Forum where creating a new Agent and
      setting a password hangs when using PHP 7.3. This is due to too few
      arguments passed to `PasswordPolicy::checkPassword()`. This updates the call
      to include a second argument of `null` so the method is satisfied and we can
      continue with checking the password.
      1bcd0e2f
  13. Sep 13, 2019
  14. Sep 06, 2019
    • Peter Rotich's avatar
      Merge pull request #5030 from aydreeihn/issue/annul_events · 2313dd8a
      Peter Rotich authored
      Issue: Annul Closed Events
      2313dd8a
    • Peter Rotich's avatar
      Merge pull request #4992 from JediKev/issue/csv-patch-adv-search-error · fd2bd479
      Peter Rotich authored
      issue: CSV Patch Adv. Search Error
      fd2bd479
    • JediKev's avatar
      issue: CSV Patch Adv. Search Error · 6ea7526d
      JediKev authored
      This addresses an issue where the previous CSV security patch causes an
      error when creating an Advanced Search with criteria like `User / Email
      Address => contains => @domain.tld`. The system tries to validate the field
      and since `is_formula` is the default validation for TextboxFields the
      system sees `@domain.tld` criteria as a formula and throws the `Content
      cannot start with the following characters: = - + @` error. Advanced
      Searches do not need the `is_forumal` validation as the fields are not
      exportable. This adds a check to see if the field's form is
      `AdvancedSearchForm` and if there is no `validator` set it gets set to `adv`
      which bypasses the validation.
      6ea7526d
    • aydreeihn's avatar
      Issue: Annul Closed Events · 8029b1b0
      aydreeihn authored
      This commit fixes an issue where if you were to change a Ticket to the Resolved status and then to Closed, the dashboard statistics would show that you had closed 2 Tickets even though both events were done on the same Ticket.
      
      We should only count one closed event per Ticket.
      
      This was reported in Issue #5018.
      8029b1b0
  15. Sep 05, 2019
  16. Sep 04, 2019
Loading