Skip to content
Snippets Groups Projects
  1. Mar 14, 2014
  2. Mar 03, 2014
  3. Feb 28, 2014
  4. Feb 27, 2014
  5. Feb 04, 2014
  6. Feb 03, 2014
  7. Dec 10, 2013
  8. Dec 09, 2013
  9. Dec 01, 2013
    • Jared Hancock's avatar
      ui: Fix large image display · e3845ad1
      Jared Hancock authored
      Fixes oversize image display to be resized in both the ticket thread and
      the redactor editor in (at least)
      
        * Ticket-view boxes
        * Client new-ticket form
        * Staff new ticket
        * Page add/edit
        * FAQ add/edit
        * Canned response add/edit
      
      Fixes osTicket/osTicket-1.8#247
      e3845ad1
  10. Nov 27, 2013
  11. Nov 26, 2013
  12. Nov 23, 2013
  13. Nov 16, 2013
  14. Nov 15, 2013
  15. Nov 14, 2013
  16. Nov 13, 2013
  17. Nov 12, 2013
  18. Nov 09, 2013
  19. Nov 05, 2013
    • Jared Hancock's avatar
      Add concept of system information page · f47c427d
      Jared Hancock authored
      Add information about current software versions, server software, php
      extensions loaded, and database space usage.
      
      In the future, this will offer a nice place to add an import/export button
      for data backup and restore, announcements, and more
      f47c427d
  20. Nov 04, 2013
  21. Oct 31, 2013
    • Jared Hancock's avatar
      Fix parsing issue in strtotime() · b9ab14c1
      Jared Hancock authored
      PHP can't discern the difference between d/m/Y and m/d/Y when just the date
      is submitted to strtotime(). Unfortunately, strptime() is not available
      until PHP 5.1.0. This patch forces datepickers to change their values to
      YYYY-MM-DD upon submission to disambiguate parsing issues.
      
      Fixes #832
      b9ab14c1
  22. Oct 10, 2013
  23. Oct 09, 2013
    • Jared Hancock's avatar
      Rebase onto feature/html-thread · 9e4e35d7
      Jared Hancock authored
      9e4e35d7
    • Jared Hancock's avatar
      f7384359
    • Jared Hancock's avatar
      Completion of dynamic forms concept · 43b74f4a
      Jared Hancock authored
      Moved to an initial form which specifies the ticket's priority and issue and
      changed the rendering to render things properly. Now the user can decide
      where priority shows on the client side, and the priority privacy setting is
      placed in the dynamic form wizard.
      
      The standard form is added to every ticket without option. Extra forms can
      be defined and associated with help topics which can additionally be added
      to tickets upon creation. This allows for standardization of the dynamic
      data location for searches and filtering.
      
      Implemented advanced search for dynamic data. Along with reinstating the
      basic ticket search on keywords
      
      Implemented ticket filtering on dynamic data for both keyword searches as
      well as searches for special fields (drop-down lists, etc.)
      
      Phone number for users is now completely optional
      43b74f4a
    • Jared Hancock's avatar
      Move client information to separate formset · 53666db6
      Jared Hancock authored
      This moves client information like name and email address out of the general
      dynamic forms data for a ticket. It really paves the way for the first-class
      user of the future.
      53666db6
    • Jared Hancock's avatar
      Dynamic data for osTicket · 9e75169e
      Jared Hancock authored
      *This is a major redesign / rework of the osTicket base*
      
      This patch drops the concept of static ticket metadata and allows for an
      admin-configurable arbitrary data that is attachable to tickets
      
      The system is architected such that the base osTicket install now comes with
      a "default" form that has fields for subject, name, email, and phone number.
      This form is editable to allow for the addition of arbitrary other fields;
      however, the basic fields must remain in order to be associated with a
      help-topic and attached to a ticket.
      
      This concept can be expanded to allow for arbitrary data associated with
      registered clients or ticket thread items.
      
      Forms are comprised of sections. Sections have a title and instructions
      properties and a list of fields. Fields have various implementations to
      represent different data such as text, long answer, phone number, datetime,
      yes/no, and selections, and are configurable to define the look and feel and
      interpretation of the respective form field.
      
      Dropdown lists are represented as "Dynamic Lists", which are
      admin-configurable lists of items. Dropdowns can be optionally represented
      as Bootstrap typeahead fields.
      
      This also adds the start of a simple ORM which will hopefully be expanded in
      the future to support multiple database platforms. Currently, only MySQL is
      implemented.
      9e75169e
    • Jared Hancock's avatar
      HTML ticket thread, inline images and draft support · 864d3539
      Jared Hancock authored
      Process inline attachments in thread entry and support inline images in
      piped emails
      
      Support inline images across the system, with draft support
      
      Migrate to a single attachment table
          That way we don't need a new table for everything we need to attach an
          inline image to (like a signature, for instance)
      
      Add richtext support for internal notes
      
      Implement images on site pages
      
      * Image paste in Redactor
      * Make non-local images optional
      * Placeholder for non-local images
      * Fix local image download hover
      * Don't re-attach inline images
      864d3539
  24. Jul 23, 2013
    • Jared Hancock's avatar
      Fix CSS style issues · b039bb3a
      Jared Hancock authored
        - Logo selection radio buttons not vertically centered (Firefox)
        - font-size value incorrect in login.css
        - Incorrect : placement in FAQ category edit
        - Incorrect block width declaration (700 vs 700px)
        - Browsers disagree on the placement of CSS3 outline properties
        - Correctly place check boxes and radio buttons
      b039bb3a
  25. Jul 03, 2013
Loading