Private Messages Enhancements - Can't Use Private Messages Before X posts

Can't Use Private Messages Before X posts.

Version 1.0.1

Description::.

This is a ported version from my hack to vb3.5.4
This hack allows to you to put a certain number of posts that a user should have before Use Private Messages but the can still send to staff groups .. admin, moderators, super moderators

[Hack Features::.

1-easy yo install
2-members can read pms but can't send
3-but they can still send pms to saff members ...
4-admin Controllable

Admin Controllable

From vBulletin Options ==> vBulletin Options ==> Can't Use Private Messages Before X posts , Enable/Disable the hack. AND Posts Count.]

Installation::.

1-Import The Product.

History::.

1.0.0 On 15. Aug 2007 Initial Version.
1.0.1 On 19. Aug 2007 Slight bugfix.

Hack Languages

English

Details

1 plugin , 6 phrases , 3 options

[vitrag24]

**EDITED**
Working.
Thanks.

But i would like to make an upgrade in which users even can't see pm window .as if users see pm window and click on send and see msg they can not use pm then they will be frustrated if pm was longer as they wasted itme in writing.

[ParsianSat_Net]

what is doing?

[DPtheGod]

It is working fine on my 3.6.8.

Nice hack. Saved me time of editing usergroup promotions!

[redlabour]

Does it still work in 3.7?

[Julrou]

Originally Posted by redlabour

Does it still work in 3.7?

Yes, of course.

But it still doesn't work with members already registered on the board, it works only with the new members...

[tanujdude91]

Can we disable this option for some usergroups???

[AngelBlue]

I suggest :

(1) You should add a URL tag to your product, so that they can find this page again more easily:

PHP Code:

<url>https://vborg.vbsupport.ru/showthread.php?t=155308</url> 


(2) That you consider implementing a version of this hack simply with template changes.

Example: I find that by adding the following to the beginning :

<if condition="in_array($bbuserinfo['usergroupid'], array(6,4,2,1,3,9,8,18,13,14,15,10))">
<table class="tborder" cellpadding="$stylevar[cellpadding]" cellspacing="$stylevar[cellspacing]" border="0" width="100%" align="center"><TR><TD class="tcat">Sorry, you cannot send private messages.</TD></TR>
<TR><TD>
<BR><B>This is usually caused by a low post count</b>, although other possible causes are :
<UL>
<LI>A negative reputation score</LI>
<LI>A recent infraction</LI>
<LI>Your account awaiting email or admin activation</LI>
</UL>
<BR>To contact the webmaster or a moderator, you should instead post a new thread in <a href="http://www.ourdomainname.org/forum/forumdisplay.php?f=XXX">the requests forum</a>.
</TD></TR></TABLE>
<else />

and the following to the end :

</if>

of the "pm_newpm" template, I can very effectively stop certain usergroups from sending PMs. Combined with using the "promote based on posts" options in the promotions system, this can be a very effective alternative to your hack. Not only does it stop them seeing the "send pm" box at all (as opposed to letting them fill it out, but then giving them an error when they try to use it), but it has less overhead, too.
The downsides of my versions are :
(1) not as flexible as having php code to define who can and who can't send PMs
(2) can't know who you are sending the PMs to, unfortunately... so not very effective for blocking the sending of PMs to all but certain people. I get around this restriction by having a "requests" forum which anyone can post a thread in and reply to their own thread in... but only moderators can see or reply to other peoples' threads. This hack still lets the affected users be *sent* pms... so staff can contact the users concerned via PMs... the users are just forced to use a requests forum or email if they want to talk back.

(3) Have you considered having a pre-filled in "to" field in the send_pm template?
Say, you could make a product that, when someone loads the new_pm page, creates a $restricted_pm_html variable, and populates it with a drop-down menu of the names of the administrators or people designated to handle pms by new/restricted users.
If the template detected the user being restricted and, instead of giving them a free text entry box for the recipient name, simply gave them a drop-down menu... that could be a very effective way of limiting PMs.

For example, if you want people with zero posts to only be able to send PMs to the administrator, you could take :

					<if condition="$show['popups']">
					<script type="text/javascript" src="clientscript/vbulletin_ajax_namesugg.js?v=$vboptions[simpleversion]"></script>
					</if>
					<div>$vbphrase[recipient_usernames]</div>
					<div id="pmrecips"><textarea id="pmrecips_txt" name="recipients" rows="<if condition="is_browser('mozilla')">1<else />2</if>" cols="50" tabindex="1">$pm[recipients]</textarea></div>
					<if condition="$show['popups']">
						<div class="vbmenu_popup" id="pmrecips_menu" style="display:none; z-index:50"></div>
						<script type="text/javascript">
						<!--
						vbmenu_register('pmrecips', true);
						recip_sugg = new vB_AJAX_NameSuggest('recip_sugg', 'pmrecips_txt', 'pmrecips');
						recip_sugg.allow_multiple = true;
						//-->
						</script>
					</if>
					<span style="display:none" onclick="return swapbcc(this);" id="bccspan1">[<a href="#">$vbphrase[bcc]</a>]</span>
					<span id="bccspan2">$vbphrase[bcc] $vbphrase[recipient_usernames]<br /></span>
					<div id="bccpmrecips"><textarea id="bccpmrecips_txt" name="bccrecipients" rows="<if condition="is_browser('mozilla')">1<else />2</if>" cols="50" tabindex="1">$pm[bccrecipients]</textarea></div>
					<if condition="$show['popups']">
						<div class="vbmenu_popup" id="bccpmrecips_menu" style="display:none; z-index:50"></div>
						<script type="text/javascript">
						<!--
						vbmenu_register('bccpmrecips', true);
						bccrecip_sugg = new vB_AJAX_NameSuggest('bccrecip_sugg', 'bccpmrecips_txt', 'bccpmrecips');
						bccrecip_sugg.allow_multiple = true;
						<if condition="$show['bcclink']">
						fetch_object('bccpmrecips').style.display = 'none';
						fetch_object('bccspan2').style.display = 'none';
						fetch_object('bccspan1').style.display = '';
						function swapbcc(obj)
						{
							obj.style.display = 'none';
							fetch_object('bccpmrecips').style.display = '';
							fetch_object('bccspan2').style.display = '';
							return false;
						}
						</if>
						//-->
						</script>
					</if>

and put the following before it :

<if condition="in_array($bbuserinfo['usergroupid'], array(1,2,3,4,etc)">
<input type="text" name "pmrecips" value="ADMINNAME" DISABLED>
<input type="hidden" name="bccrecipients" value="">
<else />

and the following after it :

</if>

That limits members of those groups to sending PMs only to ADMINNAME.

[feldon23]

Surprised this mod is not more advanced and used than it is. And I am guessing the feature did not make it into vB 3.7?

[feldon23]

The simplest form, blocking users with 0 posts from sending PMs, can be accomplished by inserting this at the top:

<if condition="$bbuserinfo[posts] < 1">
  <table class="tborder" cellpadding="$stylevar[cellpadding]" cellspacing="$stylevar[cellspacing]" border="0" width="100%" align="center">
    <tr>
      <td class="tcat">Send a Private Message</td>
    </tr>

  <tr>
    <td class="panelsurround" align="center">
      <div class="panel">
<p><b>Because of concerns with unsolicited e-mail, we are now asking that visitors to our forums participate in our forum before sending private messages.</b><br /><br />
Please introduce yourself and tell us a little bit about yourself before sending private messages to other members.</p>
      </div>
    </td>
  </tr>
<else />

and this at the bottom:

</if>

of the pm_newpm template.

[tafreeh]

stilll ok wid vb3.7 ?