vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.6 Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=194)
-   -   Private Messages Enhancements - Can't Use Private Messages Before X posts (https://vborg.vbsupport.ru/showthread.php?t=155308)

Developer 08-14-2007 10:00 PM

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

alessai2 08-15-2007 03:30 PM

Nice Hack ...

Thanks Sir ,,,,

FreshFroot 08-15-2007 10:13 PM

Finally! this way I don't have to waste space by creating a new usergroup :D

Thanks for a great hack.

Ricsca 08-15-2007 11:05 PM

Dont work :(

Smoothie 08-16-2007 02:10 AM

If the user can still send to staff before "x" number of posts, can the member also receive pm's from same before "x" number of posts? Like the welcome pm?

blogtorank 08-16-2007 03:05 AM

Very nice, a guy was asking about one of these the other day, I pointed him to another one, but your's seems to be a better version noting this:

Quote:

2-members can read pms but can't send
Great job!

Lionel 08-16-2007 03:18 AM

Quote:

Invalid SQL:
SELECT username, usergroupid FROM user WHERE usergroupid IN (5,6,7) AND username IN (username ,);
seems there is a problem when attempting to send a message to one recipient

dellow 08-16-2007 08:32 AM

Quote:

Originally Posted by Smoothie (Post 1318582)
If the user can still send to staff before "x" number of posts, can the member also receive pm's from same before "x" number of posts? Like the welcome pm?


Same quistion here..

bela-meaad 08-16-2007 10:39 AM

does this work on 3.6.5?

thanks

Developer 08-16-2007 11:07 AM

Quote:

Originally Posted by Ricsca (Post 1318507)
Dont work :(

why?
Quote:

Originally Posted by Smoothie (Post 1318582)
If the user can still send to staff before "x" number of posts, can the member also receive pm's from same before "x" number of posts? Like the welcome pm?

yes he can as i mentioned at first post he can read pms but cant send
Quote:

Originally Posted by Lionel (Post 1318615)
seems there is a problem when attempting to send a message to one recipient

i'll look at this problem today ...
Quote:

Originally Posted by dellow (Post 1318778)
Same quistion here..

[answerd]
Quote:

Originally Posted by bela-meaad (Post 1318829)
does this work on 3.6.5?
thanks

it should works ..

Njm 08-16-2007 11:27 AM

nice one thanx doood ^_^

Smoothie 08-17-2007 02:06 AM

Installed and tested and promptly got a Database error....

AngelBlue 08-17-2007 09:57 PM

Gives database errors. Avoid.

Smiry Kin's 08-19-2007 02:43 PM

Quote:

Originally Posted by AngelBlue (Post 1319910)
Gives database errors. Avoid.

tested - and agreed.

Avoid, gives error with 3.8.6 - un-edited files.

Developer 08-19-2007 04:26 PM

Updated .. update to the new version to make hack work correctly ...

redlabour 08-19-2007 04:42 PM

BUG :

XML-Fehler: Mismatched tag in Zeile 74

Julrou 08-19-2007 04:54 PM

Quote:

Originally Posted by redlabour (Post 1321041)
BUG :

XML-Fehler: Mismatched tag in Zeile 74

Same.


Quote:

Erreur XML : mismatched tag ? la ligne 74.
:confused:

Developer 08-19-2007 05:24 PM

sorry for that, download the product again ..

Julrou 08-19-2007 05:44 PM

Quote:

Originally Posted by Developer (Post 1321070)
sorry for that, download the product again ..

Thanks a lot. :)

Installed. :)

:up:

ABDALWAHID 08-24-2007 11:47 PM

i have a old user with 7 post my config ist 25 post, and dont work sorry...

Mazinger 08-27-2007 08:55 PM

Not working here also. :(

They are still able to send.

dacho 09-01-2007 11:40 AM

Is it possible to repair or to add allowed (before "x" number of posts) there can be to send PM's only to the admin ?

There is users that not entered to advertise in the system, will be able to communicate with the owner

NukeOZ 10-01-2007 01:43 AM

Installed:

Just one question though...
We have an issue on our site where new registered users are PM ing the wrong Admins.
As we have several admins.

Can this hack be modified so that I can choose which Admins recieve PM,s from New members.?:confused:

Regards Nuke..:up:

J3rico 10-02-2007 11:12 AM

Quote:

Originally Posted by dacho (Post 1330067)
Is it possible to repair or to add allowed (before "x" number of posts) there can be to send PM's only to the admin ?

There is users that not entered to advertise in the system, will be able to communicate with the owner

hi, i had the same request, and resolve with this small modify in the file product-pmbefdeveloper.xml:

before mod : WHERE usergroupid IN (5,6,7) AND userid IN (" . $recipients . ")
after mod : WHERE usergroupid IN (6) AND userid IN (" . $recipients . ")

AngelBlue 10-17-2007 12:49 PM

Two comments.
First, I would suggest that the default error for users affected by this mod be changed to :
Quote:

Originally Posted by new_phrase_suggestion
Sorry, but you may only send private messages to forum administrators and moderators.
This limit is due to your post count ({2}) being very low.
Once you have reached a post count of {1}, the limit will be removed and you will be able to send messages freely.

The second thing I would suggest is that when this mod is installed, someone who is limited to sending pms only to staff should get an error when they click on the "send PM to..." link in a non-staff member's profile. This would stop them wasting their time typing a message only to be frustrated because the system won't deliver it.
Even better would be if the link to send a PM diddn't even appear to them, but was replaced by a "Contact this user via privmsg (requires X posts)".
Best of all would be if:
* there was an admincp option to replace the "send PM to..." link in profiles with custom text for people affeted by this mod
* there was an admincp option to give the same treatment to email addresses and other contact details in profiles

elrafei 10-19-2007 08:31 PM

Nice Hack

Desesperao 11-17-2007 02:14 PM

This hack doesn?t work with 3.6.8 :(

ragtek 11-17-2007 02:21 PM

this can be done very easy without a add-on
http://www.vbulletin.com/docs/html/usergroup_promotions

MediaHound 11-23-2007 04:07 PM

Quote:

Originally Posted by ragtek (Post 1384394)
this can be done very easy without a add-on
http://www.vbulletin.com/docs/html/usergroup_promotions

How would you do that for PMs to admin only?

ParsianSat_Net 11-24-2007 01:03 PM

dear
Do'nt worked for 3.6.8
why?

vitrag24 11-24-2007 05:20 PM

**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. :D

ParsianSat_Net 11-25-2007 12:44 PM

what is doing?

DPtheGod 12-09-2007 07:21 AM

It is working fine on my 3.6.8.

Nice hack. Saved me time of editing usergroup promotions!

redlabour 01-29-2008 05:02 PM

Does it still work in 3.7?

Julrou 02-06-2008 01:09 PM

Quote:

Originally Posted by redlabour (Post 1431851)
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 02-08-2008 11:41 AM

Can we disable this option for some usergroups???

AngelBlue 02-14-2008 08:39 PM

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 :
Code:

<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 :
Code:

</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 :
Code:

                                        <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 :
Code:

<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 :
Code:

</if>
That limits members of those groups to sending PMs only to ADMINNAME.

feldon23 04-15-2008 04:23 PM

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 04-15-2008 07:23 PM

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

Code:

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

Code:

</if>
of the pm_newpm template.

tafreeh 05-19-2008 02:58 AM

stilll ok wid vb3.7 ?


All times are GMT. The time now is 05:02 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01397 seconds
  • Memory Usage 1,857KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (7)bbcode_code_printable
  • (1)bbcode_php_printable
  • (16)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (1)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (40)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete