Bug Fix patch with plugin working update

• Changed plugin settings to activate and deactivate plugin by removing the update process for the config/app.php file.
• Changed plugin ServiceProvider registration technique by removing the hard-coded code AppServiceProvider.php file. Now We are registering all plugins' ServiceProvider classes available for active plugins with status as 1 in plugins table in the database. It provides more dynamicity to developers so they need not worry about registering their custom plugin's ServiceProvider.
• Added new event "after.ticket.created" which gets fired after tickets get created and contain ticket data. It can be useful for developers for creating new plugins which need to perform a certain action after the ticket is created.
• Updated helpers.php added new method carbon() to parse string date into carbon date object.
• Added Spanish language translation (translates system up to 60% in Spanish)
• Forget password validation exception removed dd() statement
• Updated isInstall() method get installation value from Config instead of directly calling from .env
• SLA deletion issue fixed #714
• Updates for Plugin working

Bug Fixes Patch

Bugs Fixed

• Fixed #702, agents are unable to view their tickets
• Fixed #701, turning off outgoing mails does not stop outgoing sending emails.
• Fixed email edit/create page does not show proper error messages

PHP7.2 compatibility patch

PHP7.2 compatibility patch

As we mentioned in the last release that the application is now compatible with PHP7.2 but as has not been tested completely there is the number of issues which occurred while using the application with PHP7.2. This release fixes the issues logged by the application in our issue track manager.

Bugs fixed

• PHP7.2 compatibility issues mentioned in this GitHub issue
• Agents are not able to view tickets in ticket pages
• Delete Forever button does not work
• Fixed logging method in CommonmailController
• Fixed mail config file
• Fixed attachment variable initialization in MailController
• Fixed sendEmail() method in PhpMailController passing empty array as default value for $template_variables
• Fixed Bugsnag reported an issue for sendmail() which is happening for reports
• Changes status change URL method to post for preventing CSRF attacks for ticket status manipulation
• Removed sla-escalate atrisan command from the kernel as the functionality is not working and which is causing the issue while running cron command in v1.10

Changelog

• Updated Laravel version to v5.6.38
• Initial commit for Unit testing using PHP unit. We are starting with TDD and every module and class will be tested using unit test cases.
• Updated Artful log in Readme.md, release notes and CLI installer
• Added phpunit.bat for running unit tests on windows machines
• Integrated slack channel for Travis build notifications
• Updated Bugsnag API key

update to v1.10.1

This update does not contain any database update so you just need to update your file system following the steps mentioned in this article

Error Reporting

Faveo uses Bugsnag to monitor application stability in the production environment. It helps us to provide bug fixes and feature updates after analyzing the logs and crash reports for the application. If you are customizing the application under the development environment, we request you to disable this error reporting. It will allow us to ignore the errors occurred during your development cycle and we can focus more on the exceptions/bugs occurring in the live system of other users of the Faveo community. It can be easily disabled from "Error logs and debugging" option in the admin panel or by updating your app environment to development in .env.

You can still report the issues on our Github Issue page by providing proper information about the changes you are trying to implement. We assure you that Faveo community will help you and your customization can be a part of Faveo application if it follows our contributing guidelines.

Framework updates

Faveo Helpdesk Community v1.10

It's been a while since we last updated the repository to release v1.9.6 and a failed attempt to release v1.10-Beta version. But Faveo team has been continuously working hard to update the project and providing the best Helpdesk system to Faveo Helpdesk community.

Faveo Helpdesk v1.10 introduces some major updates in the system along with Laravel framework update. While Faveo v1.9.6 was based on Laravel 5.2 this version updates the framework version to 5.6.33. Which might require some updates in server configuration to make sure system works flawlessly after the update. Check server requirements for Laravel 5.6 before updating the system.

What's new?

Faveo Probe

Many a times users have reported us about the problem in the installation process as they were not able to get through the first step and saw 500 error page while installation. As Faveo checks the system requirements in Laravel based route if server is not able to boot Laravel it will not show the installation step. While Faveo Probe an external PHP based script was already available to check server requirements, we have added Probe script in the system so users can directly test server for the requirements from Faveo itself.
To run probe test simply run your_faveo_url/probe.php in your browser which will show you the result as shown in the image below

Faveo Installers

• GUI Installer
  Some refinements have been implemented in Faveo GUI installer to make installation intuitive and simple.

• CLI Installer
  If you are a geek like us and love running commands in the terminals then you might like our CLI installer which allows you to install Faveo using two simple artisan commands.

  Run php artisan install:faveo to check server requirement and provide database details.
  

  Run php artisan install:db to migrate database and complete installation process

  

Advance localization options for language translation

As Laravel supports multilingual applications, Faveo can be translated into various languages. In previous version of Faveo translation only works on system level that is once you change the system's language from settings all users will see the system in that language. But now translation works on three levels.

• System level : Admin can select the default translation for system and system will load in that language by default.

• User level : Users can now select their preferred language to load system from the top nav bar language options. When logged in users select their language preference it will save in their account and next time when they login system will load in their preferred language.
  

• Browser level : Users who are not logged in can change and see the system in translated language without login.
  

Email configuration alert

As Faveo system requires an email to be configured for incoming and outgoing mails to fetch tickets and reply on tickets. System will now show the alert until the incoming and outgoing mail setup has not been configured.

Dummy data clean up

Faveo had dummy data installation option to check and test the system working in test environment with test data. But after testing users had to drop the tables to clear database manually and then again reinstall the Faveo. Which is somewhat annoying if you value your time like us. Faveo now has an option to clean up the dummy data installed during test installation so system can be used after testing without performing other actions.

Change logs

• Deprecated single URLs for ticket list pages for inbox, open, closed etc. Now all tickets can be get using single URL and passing parameters to it which renders data faster than the old URLs. All old routes have been updated with the new route with required parameters and will be removed in next update.
• Deprecated functions in Agent/helpdesk/TicketController.php and routes in web.php can be found under deprecated block.
• System is now compatible with PHP7.2 though it has not been tested thoroughly. If you use PHP7.2 and encounter any issues in the system please raise the issue on our GitHub page.
• API response fix when debugging is enabled and JSON response comes with HTML data.
• Language packages: Various updates have been made in language packages to make system translation more consistent in Italian, German and Chinese language. We would like to thank various members who sent pull requests and helped to improve Faveo translation
  • Yang.l (Chinese)
  • Philippe Aellig @philippeaellig (German)
  • Luca @volp1s (Italian)

Bug fixes

• Custom form data not visible in ticket timeline or ticket detail page in agent panel.
• Ticket thread iframe of ticket details page in agent panel and client panel is not visible completely in all browsers.
• Removed rendering of password in email settings edit page for security reasons.

How to update?

Follow steps mentioned in this article to update Faveo from v1.9.6 to v1.10. You will find database update SQL dump in

Faveo_root/DB/update from v1.9.6 to v1.10/updatedatabase.sql

NOTE If you are updating from v1.9.6 to v1.10 you might have to update your email settings to make incoming and outgoing mail functionality working.

What's next

In coming month we will release various updates with bug fixes and code cleaning to optimize system performance. We are also working on developing API version 2.

Facebook login bug fix patch

Bug Fixed

• Token parsing issue for Facebook which prevents users from login the system using Facebook oAuth API.

To fix the issue

Just make some changes in vendor/laravel/socialite/src/Two/FacebookProvider.php file

Check this commit for the required changes.

Security bug fix patch

Bug fix patch

• Preventing execution of backdoor scripts
• Preventing php file uploads in user's profile pic
• Handling token mismatch error when the page is opened for too long and session gets expired.
• Excluding APIs from CSRF token verification

Security-patch v1.9.4

This release provides a security patch against CSRF attacks using Laravel's CSRF token verification.

The issue was reported by one of the member of Faveo community and it helped us to take a step forward for making the application more secure for these attacks.

Thanks! @rungga for reporting this issue #446.

We are also testing the application for backdoor script injection attacks which may make the system vulnerable for attackers. We'll soon release the next version with updated Laravel version, new enhancements and further security improvements.

To update your existing Faveo system from v1.9.3 to v1.9.4 follow File System Update process mentioned in this wiki article.

bug-fix-patch

Bug fixed

#344
System is storing the attachment in chosen storage medium(DB/file system) but not showing the attachments in ticket detail page or ticket timeline page.

How to Fix (for Faveo v1.9.2 users)

See this commit for the details of changes made for bug fix.

Or

Open this file: Root_directory of faveo/app/Model/helpdesk/Ticket/Ticket_attachments.php
search and replace
if ($this->poster == 'ATTACHMENT')
with
if ($this->poster == 'ATTACHMENT' || $this->poster == 'attachment')
at line 49

v1.9.2

Bugs Fixed

• Single cron issue fixed [refrenced to #366, #347 ]
• Corrected notification counts
• Fixed canned response error
• Correct message for registration
• Removed routes of PRO features
• Exception handling while adding language
• Showing agents in alphabetical order in various drop down menus
• Handling the case when agent/admin adds same owner while changing ticket's owner
• Fixed priority and auto assignment while creating ticket form cleint panel
• Fixed typos in english language translation
• Fixed counts of tickets of every categroy
• Removed duplicate option from top nav bar
• Fixed empty database check while installation
• Assigning team leader in a team while creating new team
• Fixed #361

Enhancements

• Sending email notfications to users while merging their duplicate tickets
• Implemented Yajra in users table
• Custom filter and search option in users table
• Check if JavaScript is enabled or not while installation
• Put max execution time and "mbstring" extension check while installation

Upgrade Guide

If you are already using an older version of Faveo then follow this wiki article to update your Faveo system.

Bug Fix Patch

Fixed Bugs

Major bugs

• Admin was not able to save/update cron settings in new installation.
• Incorrect count of tickets in dashboard while login as an agent .
• In client panel users/clients were able to reply without entering any comment in comment field.