Version: 1.2.0, by MaryTheG(r)eek
Developer Last Online: Mar 2012
Category: Major Additions -
Version: 3.8.2
Rating:
Released: 05-07-2009
Last Update: 05-10-2009
Installs: 41
DB Changes Uses Plugins Auto-Templates
Additional Files Translations Is in Beta Stage
No support by the author.
Removed by the Author because:
For 7 mods, there are 1905 downloads but only 577 clicked installed.
For these 577 installs I got 4 donations for Brand Free. Make a simple search on the net using the product name and you'll find that 50% have illegally removed my copyright.
I found 3 vb.org style sites, offering for download my mods but after PAID SUBSCRIPTION, or DONATION
I developed this module for my own use. I used to use in the past Kayako and DeskPRO. Really professional support scripts but with so, so, so many features for my needs, so finally I was wasting more time trying to use them, than to offer real support. That's why I decided to code my own module, having in mind to be easy like usining emails, but of course with much more features. Now, I'm sharing this with you, wishing to become a useful tools in your hands.
2.- Installation
The installation is pretty easy, has been checked many times for installing and uninstalling the product. Just follow these steps below:
Download and unzip the file microSUPPORT.zip
Open the folder vbulletin and select all files and subfolders inside it
Connect to your website and open the directory where is your vBulletin installation (usally forum, forums, portal etc).
Upload the selected files to your site. If you fellow the right way then the file support.php must be on the same level as the index.php file of vBulletin.
Before any new installation is good to backup your database before, even if nobody is doing it (including me). At lease turn your site off
Check at your AdminCP->vBulletin Options->Plugin/Hook System that Plugin system is enabled.
From your AdminCP->Plugin System->Manage Products choose Add/Import Product and import the product: product-microsupport.xml
3.- Configuration
As every vBulletin product, you need to make some initial configuration before it goes live.
MicroSUPPORT Options
Setup FAQ categories, Support Departments, Supported Products. Setting Ticket statuses is optional as you can only edit them. Actually this is only for those operating a non-English site, to translate the statuses. Otherwise you can't add/delete statuses.
Setup usergroup permissions.
4.- Template Modification
The module is using it's own templates, so it doesn't needs any template modification except if you want to add a link to the navbar. In this case you need to modify the NavBar template.
You can modify the code as you like to meet your special needs
You can distribute this module AS IS, but NOT FOR PROFIT
My copyright link must remain always visible.
Even if there is an option to automatically turn off my copyright link, you can't do that unless you're member of my club.
6.- Others
There is no commercial version, but in the upcoming days should be a special version just for my club's members.
Support is limited due to lack of FREE TIME.
7.- Version 1.1.0 New Features & Bug fixes
Fixed the bug where the email didn't sent to client by using mail function instead vbmail.
Added attachment option to new tickets and replies
Added filtering option to ticket listing (Tech section). Now a Technician can eliminate the amount of tickets by filtering them by Department and/or Product and/or Ticket status.
More options in microSUPPORT general options:
Different email to user for new ticket than the reply
Default email address (Technician) for notifications for new tickets or new replies.
Email footer
HTML emails to user
Email priority
User salutation in email
Allowed attachment types.
8.- How to upgrade
Unzip and upload all files and folders
CMOD 777 directory microsupport/attachments/
Import product-microsupport.xml checking to overwrite.
Set the extra options
9.- Version 1.2.0 Bug fixes
In ticket view the data of original post were wrong. Fixed.
When a ticket was closed View and Close appeared in the select list. Fixed. Now shows only Open for reopening it.
10.- Upgrade from 1.1.0 to 1.2.0
Upload file support.php
Import product-microsupport.xml checking to overwrite.
Enjoy it
Maria
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
When a member add a new ticket, he can add (of course) a description in the ticket. But after, when a technician replies to the ticket, the original description (added by the member) disappears and the original description is replaced by the technician response.
When a member add a new ticket, he can add (of course) a description in the ticket. But after, when a technician replies to the ticket, the original description (added by the member) disappears and the original description is replaced by the technician response.
Is it normal?
Of course is NOT normal But it's so starnge too, as there is no any logic way to do something like this, just because original ticket (text) goes to different table (microsupport_tickets), while all replies are storing to microsupport_ticket_replies.
Give me some time to check it, maybe I did code overwrite in my last release yesterday. But as I can see in the screenshoots above, the texts are different on all posts. Maybe have you confused from the listing? At the top appears the original ticket and below you can see a listing of all replies. At the end is the editor to add reply. Can you see them?
Bug reported : The title of a ticket doesn't show in the navbar (when you view a ticket).
Suggestion :
We can't edit ticket content and title.
We can't delete tickets.
We can't edit technician replies
We can't delete technician replies
And every technician should be able to make them
microSUPPORT (Ticketing & F.A.Q) Details »»
About Developer
Visit Web Site
DB Changes 
Is in Beta Stage 
05-11-2009, 05:56 AM
But it's so starnge too, as there is no any logic way to do something like this, just because original ticket (text) goes to different table (microsupport_tickets), while all replies are storing to microsupport_ticket_replies.
Thanks in advance.
