vBSupport v2.0.0 Beta 2

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:

		<td class="vbmenu_control"><a href="calendar.php$session[sessionurl_q]">$vbphrase[calendar]</a></td>

Add Below:

<!-- 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 -->

B) Template 'postbit_legacy':

Find:
[code]
<if condition="$show['postcount']">#<a href="showpost.php?$session[sessionurl]p=$post[postid]&amp;postcount=$post[postcount]" target="new" rel="nofollow" id="postcount$post[postid]" name="$post[postcount]"><strong>$post[postcount]</strong></a></if>
[code]

Add Above:

<!-- vbSupport start -->
			<if condition="$show['ticketcount']">#<a href="vbsupport.php?$session[sessionurl]do=viewpost&amp;pid=$post[postid]&amp;postcount=$post[postcount]" target="new" rel="nofollow" id="postcount$post[postid]" name="$post[postcount]"><strong>$post[postcount]</strong></a></if>
<!-- vbSupport end -->

C) Template 'postbit':

Find:

			<if condition="$show['postcount']">#<a href="showpost.php?$session[sessionurl]p=$post[postid]&amp;postcount=$post[postcount]" target="new" rel="nofollow" id="postcount$post[postid]" name="$post[postcount]"><strong>$post[postcount]</strong></a> &nbsp;</if>

Add Above

<!-- vbSupport start -->
			<if condition="$show['ticketcount']">#<a href="vbsupport.php?$session[sessionurl]do=viewpost&amp;pid=$post[postid]&amp;postcount=$post[postcount]" target="new" rel="nofollow" id="postcount$post[postid]" name="$post[postcount]"><strong>$post[postcount]</strong></a> &nbsp;</if>
<!-- vbSupport end -->

ENJOY!!

-CMX

[87accordlxi]

Originally Posted by CMX_CMGSCCC

It should be the same for the upgrade procedure.



Which template edit were u doing when u got this error?



The Unregistered access is hazy at best, I need to do more testing on it to verify all permissions are functioning properly for it.

In the end, it will use the Usergroup settings that you have specified for Unregistered inside the Usergroup Manager.

The other settings u need to setup inside Admin CP -> Usergroups -> Usergroup Manager -> And set the vbSupport Permissions for each usergroup you want to access the system and what features they are allowed to do.

-CMX

Ah thanks. Fixed the permission issue. I'm still getting some database errors though. When I'm in a ticket and click the check box next to "Delete this Ticket," I get this:
Fatal error: Registry object is not an object in /includes/class_dm.php on line 177

Other than that, I believe I've sorted everything out.

[mtha]

6) Bugfix: Usergroup Permissions are now working for Allowed Usergroups & Denied Usergroups.

It should take DEFAULT permission (usergroup permission) if group permissions for individual category it not set.

Now you have to set permission in Group Manager, then in Category manager, isnt it a duplication?

[ndahiya]

Originally Posted by Derekclarke

I was doing the first one.

<!-- 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 -->

I have done the other templates, just this one that has the error.

think it should be

PHP 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 --> 


[FireFish]

I noticed that in Beta 2; I cannot control the Assign To drop-down list.

Used to be that if a user was part of a usergroup that had Admin Ticket rights, their name was there. You could also add by UserID.

Now, I cannot get anyone else's name onto that list; mine is the only one there.

Any thoughts?

[dethfire]

permissions seem messed up, after upgrading to beta 2 I get "You are not authorized to create". I am admin and have all permissions set correctly in admincp

[EasyTarget]

awesome hack.

Just installed from scratch.. 1st hack on the forum and, besides the missing "]" in the navbar template edit that ndahiya pointed out, it seems to be working fine.

created, assigned, closed, edited and deleted tickets just fine.

some ideas:
have some sort of deletion verification so that if you mark a bunch of tickets and then accidentally choose delete that you don't lose them all.

for listing tickets maybe have the option to list them by category.

option to auto assign tickets according to the category they're placed in.

ability to assign tickets to usergroups.

ability to view who the ticket is assigned to/category while you're viewing the ticket/thread (maybe add categories in the navbit?).

*edit*
got this error when submitting a blank ticket:

Database error in vBulletin 3.5.4:

Invalid SQL:

		SELECT post.postid, IF(post.userid = 0, post.username, user.username) AS username,
			post.pagetext, post.allowsmilie, post.userid, post.dateline
		FROM vbs_ticket_post AS post
		LEFT JOIN user AS user ON(user.userid = post.userid)
		WHERE post.visible = 1
			
			AND post.threadid = 
		ORDER BY dateline DESC, postid DESC
		LIMIT 11;

MySQL Error  : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY dateline DESC, postid DESC
		LIMIT 11' at line 8
Error Number : 1064
Date         : Wednesday, May 17th 2006 @ 09:33:17 PM
Script       : XXX/vbsupport.php
Referrer     : XXX/vbsupport.php?do=newthread
IP Address   : XXX.XXX.XXX.XXX
Username     : XXXX
Classname    : vb_database

[zooman]

I have installed the beta 2 hack today, very good just what I need.

One thing when members go to post the Receive PM Upon Reply is not displayed (or any other notification option). I can not find any options for this. Where am I going wrong?

<if condition="$show['misc_options']">
<fieldset class="fieldset">
<legend>$vbphrase[miscellaneous_options]</legend>
<div style="padding:$stylevar[formspacer]px">
<if condition="$bbuserinfo['signature'] != ''"><div><label for="cb_signature"><input type="checkbox" name="signature" value="1" id="cb_signature" tabindex="1" $checked[signature] />$vbphrase[show_your_signature]</label></div></if>
<if condition="$show['parseurl']"><div><label for="cb_parseurl"><input type="checkbox" name="parseurl" value="1" id="cb_parseurl" tabindex="1" $checked[parseurl] />$vbphrase[automatically_parse_links_in_text]</label></div></if>
$disablesmiliesoption
</div>
</fieldset>
</if>

[Bigasses]

Does the new beta have the ability to send pm/email on assign user?
I think this is the killer feature this new version needs, otherwise, new version is much nicer

[Antivirus]

Originally Posted by Bigasses

Does the new beta have the ability to send pm/email on assign user? I think this is the killer feature this new version needs, otherwise, new version is much nicer

It's a good idea, but I would prefer for it to be a variable setting within vboptions so admin has a choice of whether or not to PM/email the staff member upon assigning the ticket.

[kurtbarker]

PMing staff on assign would be great, so that they know that a ticket is waiting for them in particular...

but something I wanted to ask about... When using 1.1, the member that created the ticket got a PM when it was replied to... This isn't happening on version 2... Was it an option I missed, or isn't it included in this version?