I have a default installation, created categories, products, faqs.. i do not see anywhere to create new tickets..
What did you do ? (i assume you followed the instructions)..but maybe u did more in more details ? .
thanks!
When you click on the NavTab, there should be links under it. There should be "New Ticket", "My Tickets". and "Technician". Do you not have these links?
Trying to find answer to this, but searches don't show. I like this mod, but a few questions.
I am the senior site admin for Agares Media and need to configure this support ticket system to be available under the following conditions:
The user has purchased an extended or premium license to one of our products which include the ticket support with the purchases
Ticket support entitlement has not expired (extended expires after 1st year)
User can purchase support tickets in batches of 30 which are valid for 180 days then expire
Could you possibly point me in the right direction? What files am I to edit and about where? I am a programmer and can probably figure it out if I were pointed in the proper direction. Thanks.
Trying to find answer to this, but searches don't show. I like this mod, but a few questions.
I am the senior site admin for Agares Media and need to configure this support ticket system to be available under the following conditions:
The user has purchased an extended or premium license to one of our products which include the ticket support with the purchases
Ticket support entitlement has not expired (extended expires after 1st year)
User can purchase support tickets in batches of 30 which are valid for 180 days then expire
Could you possibly point me in the right direction? What files am I to edit and about where? I am a programmer and can probably figure it out if I were pointed in the proper direction. Thanks.
You could create a new usergroup that would only have access to the microSupport system. ie. usergroup X (premium members). So basically you'd maybe have to use the paid subscription system in Vbulletin as the payment gateway, and then when people purchased through it their usergroup would be changed to usergroup x, and then they would have access to the microSupport ticketing system. Also when their subscription expires etc, they would be returned to their original usergroup and thus wouldn't be able to access the ticketing system.
I love your product from 4.2.2 version and it worked just fine for me.
I had to reinstall the database, due to a corruption, from a backup that never had Microsupport on it.
Now I am running VBulletin 4.0.3 pl1 and tried installing Micro Support, when I tried importing the product.xml file I get the following error from the database
Database error in vBulletin 4.0.3:
Invalid SQL:
INSERT INTO `microsupport_ticket_status` VALUES (1, 'Open', 1);
I love your product from 4.2.2 version and it worked just fine for me.
I had to reinstall the database, due to a corruption, from a backup that never had Microsupport on it.
Now I am running VBulletin 4.0.3 pl1 and tried installing Micro Support, when I tried importing the product.xml file I get the following error from the database
Database error in vBulletin 4.0.3:
Invalid SQL:
INSERT INTO `microsupport_ticket_status` VALUES (1, 'Open', 1);
This is because there is already a record with id 1 from your previous installation. Even if you've manually deleted the records, the ids remain there. So, its better to delete (drop) the table microsupport_ticket_status and re-import the product_microsupport.xml or if you're familiar with phpMyAdmin (I assume that you know to use it, so you can drop the table), you can click on SQL and enter:
Code:
CREATE TABLE IF NOT EXISTS `microsupport_ticket_status` (
`id` int(11) NOT NULL auto_increment,
`name` varchar(50) NOT NULL default '',
`displayorder` int(11) NOT NULL default '0',
PRIMARY KEY (`id`),
KEY `displayorder` (`displayorder`)
) ENGINE=MyISAM;
INSERT INTO `microsupport_ticket_status` VALUES (1, 'Open', 1);
INSERT INTO `microsupport_ticket_status` VALUES (2, 'Progress', 2);
INSERT INTO `microsupport_ticket_status` VALUES (3, 'Closed', 3);
ATTENTION *** Assuming that there is no table prefix. If you're using table prefix you must add it before microsupport_ticket_status (4 instances).