Major Changes in Template Function and New Feature

Exciting New Feature: Ticket Changelog

Changelog

• Major changes in the function ns_get_template_part() - the function is redefined
• New feature: Log the changes to the tickets and display them on both front end and admin panel
• New filter hooks: nanosupport_locate_template, nanosupport_log_ticket_changes
• Fixed: Knowledgebase was visible with absolute URL even was inactive
• Fixed: Knowledgebase Category wasn't bulk selectable - an undefined index was there
• Improvements: A11y (Accessibility) improvements

Download

Download from WordPress.org

Bug Fix Release

Changelog

• E-Commerce: Check Purchase Receipt's authenticity on the submission of a ticket
• New filter hook: ns_ticket_responses_arg, ns_check_receipt_validity
• Fix: Account creates even when the ticket form has an error
• Security Fix: Clickjacking fixes on new tabbed links
• A11y (Accessibility) Fixes in both front end and admin end
• Minor Fixes where PHP notices were visible

E-Commerce Support

Changelog

• New Feature: E-commerce — Support to products of Easy Digital Downloads (v2.5+) and WooCommerce (v2.2+)
• Additional Feature: Let the admin end users filter tickets based on Priority and/or Status and/or Agent
• 7 new icons to NanoSupport Icons
• New filter hooks: 'ns_date_time_format', 'ns_mandate_product_fields'
• Issue Fixed: Email Template background was repeating
• Issue Fixed: Date Time format was not changeable
• Issue Fixed: Throwing javascript error in browser console due to old focus-ring.js
• Minor fixes on A11y issues

Bug Fixed Release

Changelog

• Bug fixed: Ticket additional info was affecting on show/hide in smaller devices
• Bug fixed: Ticket assignment on behalf of support seeker was getting only administrators
• Code of Conduct added for contributors
• Some other minor fixes

Bug fixed + New Feature Release

Changelog

• New Feature: Ticket can be copied into a Knowledgebase document
• Requested Feature: ReEngineering Knowledgebase Doc URL strucuture
• Bug fixed: Ticket cannot be added on behalf of client
• New filter hook: ns_nanodoc_arguments, nanosupport_copied_content, nanosupport_assigned_user_role

Bug fixed release

Changelog

• Bug fixed: Support agent loses his status on profile update
• Bug fixed: Ticket updated dates failure
• Assured partial accessibility features
• CSS are completely modularized into SCSS files
• Grunt version and clean implemented
• Several minor issues fixed

Quick Bug Fix Release

Changelog

• Quick bug fixed introduced with version 0.3.2 with same user and same date for ticket date and update date

Bug fixed release

Changelog

• Ticket update date fixed syncing with replies
• Bug Fixed: pending ticket link was not working in agent notifying email
• Withdrawn Composer dependency in development, as no PHP library is required to depend on

Bug fixing release

Changelog

• Fixed: Assigning ticket to Support Agent was not triggering any email
• New filter hook: nanosupport_notify_agent_assignment
• Fixed: Users can set themselves as a Support Agent
• Priority assignment by public made dynamic using Settings API
• Various i18n functions fixed
• Several other minor fixes all over the plugin code and texts

Major and minor changes as well as fixes release

Major changes

• Rich Text editor for ticket body text
• New filter hook: ns_wp_editor_specs, ns_back_to_knowledgebase
• Pending ticket notification using admin menu bubble
• Fixed translation strings to strip out dumped HTML and made most of them SQL injection proof
• Composer, npm dependency and Grunt incorporated for easy development collaboration
• Default assignment of 'Support' department is made deprecated
• User can choose Support Department on submitting new ticket (Settings available)
• CSS is changed from LESS to Sass
• System Status admin page

Minor changes

• Reorganized third party libraries
• contributing.md added
• Github issue template added
• A warning on upgrading process fixed - props @prionkor
• jshint error fixed with procedural code
• Agent email was not sending - fixed
• Ticket response content added to email body
• Back link to Knowledgebase added after Knowledgebase contents