The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
vBSupport v2.0.0 Beta 2 Details »» | |||||||||||||||||||||||||
vbSupport v2.0.0 BETA 2 by CMX (http://www.cmgsccc.com)
Official Homepage - http://www.vbplaza.com v1.1 of this modification was found to contain an SQL injection. If you run v1.1 of this modification, you are hereby advised to update to v1.1a of this modification. To update from v1.1 to v1.1a, grab the v1.1a ZIP and overwrite the vBSupport.php file on your server with the new version. Note that while no other vulnerabilities were noticed by vBorg Staff, this does not mean that such things do not exist. vBorg Staff fixed the one SQL injection according to these rules. Any other fixes that may be needed now or in the future are left to the original author. -- vBorg Staff Welcome to the latest hack by CMX for your vBulletin Message Board. This is a fully featured Ticket based support system for you website. If you had installed the older version of vBSupport v1.1, then you already have an idea what this sytem is all about. Basically, this system will allow your Forum Members to create new support tickets using the same login as your vBulletin forums login for your users. There have been many improvements from the older v1.1 vBSupport System I made a while back. New Features for v2.0.0+: 1) Permission Checks are better implemented and are more useful now. 2) AJAX Open/Closing tickets by double clicking the thread icon when listing tickets. 3) AJAX Ticket Title editing just like the forums Thread editing as well. 4) Post Quick Reply is now using the AJAX system where possible to post replies to tickets. 5) You can now Edit posts inline using the AJAX system as well. 6) Inline Moderation when listing tickets includes Delete Ticket, Open Ticket, Close Ticket. 7) You can now delete individual Posts from Tickets via the Inline Moderation as well. 8) MASSIVE performance load improvements. On my forums with 200,000 members, it would take 4 seconds to view a ticket due to a very strenuous query. Now it loads tickets in 0.13 seconds. 9) Category Administration has now been moved into the Admin CP instead of on the vbSupport page itself. 10) Everything should be fully phrased now as well. Other Features: 1) IF you have installed the older vBSupport version, it will auto uninstall it for you. (It will NOT delete the old tickets!) 2) Admin CP -> vbSupport Maintenance -> Import Old Tickets is now in and working to import the old tickets if you had vBSupport installed. 3) A ton of permissions per Usergroup to set the settings up the way you want them. vbSupport v2.0.0 BETA 2 Updates: 1) Bugfix: Quick Reply functions properly when you have the Quick Reply option enabled for Yes - Click Required. 2) Bugfix: Normal Reply/Closed button is there when viewing a ticket. 3) Bugfix: Admin CP Deleting a ticket now functions properly. 4) Bugfix: AJAX Edit feature does not display an alert(postid) anymore. 5) Bugfix: Active On/Off works for each category when enabled/disabled from the Admin CP. 6) Bugfix: Usergroup Permissions are now working for Allowed Usergroups & Denied Usergroups. 7) Bugfix: Changed some templates that linked to the wrong PHP files. 8) Bugfix: New Thread template is cleaned up a bit and it displays properly in Firefox too now. 9) Bugfix: Active phrase now is installed as a vbSupport phrase. PLEASE NOTE: This is the very first release of vbSupport 2.0.0. Which means that this is a BETA release. I will try to correct any issues found ASAP. I have vbSupport v2.0.0 BETA 1 running on my production site at www.cmgsccc.com, so I should be able to find most bugs since there are over 200,000 registers members there and it will get put to the test quite a bit. However, if you find something, please post it here. By installing this BETA version, it will uninstall the previous vBSupport system automatically. It will leave the old ticket tables upon installation. It should import the older Ticket Categories that you had before as well. I would also like to recommend that you backup your MySQL database, just in case a mishap occurs as this is BETA. ALSO: The older version vBSupport v1.1 will be here for download until v2.0.0 comes out of BETA. vBSupport v1.1 is NOT in the BETA stage, only vbSupport v2.0.0 is in the BETA stage. Upgrading Instructions From vBSupport v1.x NOTE: These are ONLY applicable if you are upgrading from vBSupport v1.x! 1) Delete all of the older vBSupport files from your server. If you are not sure which files they are, the vBSupport v1.1 is still available for download here so you can download that and look at the files in there. 2) Upload all of the files in the upload folder to your forums ROOT folder. Make sure that if it asks about any files, that you set Overwrite to overwrite all files as well. 3) In your Admin CP, goto Plugin System -> Manage Products -> Add/Import Products at the bottom -> Select the XML file that you have downloaded in the package named product-vbsupport.xml -> Set Allow Overwrite to YES -> Import. 4) Perform the template edits below and you have vbSupport v2.0.0 up and running! 5) Refresh your forums Admin CP page. 6) Admin CP -> vbSupport Maintenance -> Import Old Tickets if you want to save the older tickets. Otherwise you can skip this feature. New Installation Instructions: 1) Upload all of the files in the upload folder to your forums ROOT folder. Make sure that if it asks about any files, that you set Overwrite to overwrite all files as well. 2) In your Admin CP, goto Plugin System -> Manage Products -> Add/Import Products at the bottom -> Select the XML file that you have downloaded in the package named product-vbsupport.xml -> Set Allow Overwrite to YES -> Import. 3) Perform the template edits below and you have vbSupport v2.0.0 up and running! Template Edits: A) Template 'navbar': Find: Code:
<td class="vbmenu_control"><a href="calendar.php$session[sessionurl_q]">$vbphrase[calendar]</a></td> Code:
<!-- vbSupport start --> <if condition="$vboptions['vbsupport_enabled']"><td class="vbmenu_control"><a href="vbsupport.php$session[sessionurl_q">$vbphrase[vbsupport_title]</a></td></if> <!-- vbSupport end --> Find: [code] <if condition="$show['postcount']">#<a href="showpost.php?$session[sessionurl]p=$post[postid]&postcount=$post[postcount]" target="new" rel="nofollow" id="postcount$post[postid]" name="$post[postcount]"><strong>$post[postcount]</strong></a></if> [code] Add Above: Code:
<!-- vbSupport start --> <if condition="$show['ticketcount']">#<a href="vbsupport.php?$session[sessionurl]do=viewpost&pid=$post[postid]&postcount=$post[postcount]" target="new" rel="nofollow" id="postcount$post[postid]" name="$post[postcount]"><strong>$post[postcount]</strong></a></if> <!-- vbSupport end --> Find: Code:
<if condition="$show['postcount']">#<a href="showpost.php?$session[sessionurl]p=$post[postid]&postcount=$post[postcount]" target="new" rel="nofollow" id="postcount$post[postid]" name="$post[postcount]"><strong>$post[postcount]</strong></a> </if> Code:
<!-- vbSupport start --> <if condition="$show['ticketcount']">#<a href="vbsupport.php?$session[sessionurl]do=viewpost&pid=$post[postid]&postcount=$post[postcount]" target="new" rel="nofollow" id="postcount$post[postid]" name="$post[postcount]"><strong>$post[postcount]</strong></a> </if> <!-- vbSupport end --> -CMX Supporters / CoAuthors Show Your Support
|
Comments |
#282
|
|||
|
|||
Quote:
Plus I have setup a category assigned an admin Now I would assume that this function is here so when that category is sellected that admin would have the ticked assigned to them however even if a category is selected by the person raising the ticket its still sits in the system as unassigned If im on the wrong track here can you please explain the usage of categories Thanks in advance |
#283
|
||||
|
||||
Quote:
He seems to have put this hack on the back burner.. But I cant complain.. He has been releasing features for the estore left and right.. If you end up figuring out the problem though, I am still having the issue.. |
#284
|
|||
|
|||
I found some radio buttons to close it just scroll down in the thread but yeah the button by itself with no name is dangerous seeing how it deletes the ticket
still no joy with assigning the ticket to the category admin though and as a few others have requested some sort of notification that a ticket is created would be good PM would be the best but email would do Great hack but could be an Awesome one with a little polishing |
#285
|
||||
|
||||
Quote:
But as for your category issue.. I think that you have all tickets unassigned by default.. There needs to be a notification pm for this and it would rule.. And if a specific category is selected, it would be cool if it either a) defaulted to a user and b) radomiz or cycle through a usergroup... That would be sweet... Thanks for the heads up on where I can reassign these tix.. I will just keep the delete option off for the mods.. and I wont have to worry about the delete button |
#286
|
|||
|
|||
The delete button appears, but the value/text for this button is blank. Where would I go to correct this?
-see attached image- |
#287
|
|||
|
|||
Are there any screenshots for this?
|
#288
|
|||
|
|||
I've corrected this problem by removing "$vbphrase[support_delete_selected_tickets]" and replacing it with "Delete"
|
#289
|
||||
|
||||
Quote:
To fix it another way, just add a phrase Phrase Type: vBSupport Phrases Product: vBSupport System Varname: support_delete_selected_tickets Text: Delete Selected Tickets |
#290
|
|||
|
|||
Staff notification is a must imo
Is this going in at anytime? |
#291
|
||||
|
||||
Quote:
He has been living there for awhile. I wouldnt expect much on this project until that slows down. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|