• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Please provide ability to disable user tagging

AndyB

Well-known member
#1
On my forum I don't want members using the new user tagging function. Please provide a master switch in the Admin CP to disable this feature completely.

When disabled, the drop down would not be displayed after typing the @ character followed by a few characters. Also the Alert Preferences options for tagging would not be shown.
 

AndyB

Well-known member
#3
You can turn it off via usergroup permissions.
That doesn't disable the user tagging function, that only turns off the Alert function if set to zero.

I would like to have user tagging completely disabled, no drop down, no BBCode link, no Alert Preferences.
 

Chris D

XenForo developer
Staff member
#5
Not disagreeing with the suggestion and I don't disagree with the logic of having an on off switch.

But what I don't understand is the reason why you would want to disable it.
 

Martok

Well-known member
#6
I'm curious to know why you want to disable user tagging?

I'm not saying you're wrong to request a global option to switch it off, just interested in your reasons. My users love it on my forums. :)
 

AndyB

Well-known member
#7
Not disagreeing with the suggestion and I don't disagree with the logic of having an on off switch.

But what I don't understand is the reason why you would want to disable it.
Starting off a message with @joeblow makes it very difficult to follow a conversation. I don't want my members to start a post with a user tag. Instead I want them to quote the message using the Reply function. The Reply function which quotes the message is extremely important for in-depth conversations on a forum.

The user tag is only useful for sites like Facebook which don't have a reply function.
 

Jeremy

Well-known member
#8
You can turn off the @ symbol in your options, and edit out the content from the templates. If you style it the same, they'll be none the wiser. The probability of a user 'stumbling' into this is probably rather low. And if they do, it just provides access to a member card. If it doesn't alert the user, the probability of a user quoting someone to get the alert is higher than a tag.

Turning off the functionality won't change posting habits if members decide they'd rather speak 'directly' to a person by putting their name in a post.
 

Martok

Well-known member
#9
Starting off a message with @joeblow makes it very difficult to follow a conversation. I don't want my members to start a post with a user tag. Instead I want them to quote the message using the Reply function. The Reply function which quotes the message is extremely important for in-depth conversations on a forum.

The user tag is only useful for sites like Facebook which don't have a reply function.
Interesting that you seem to be having users replacing the quote option with a user tag (I assume that you're running 1.2 beta/RC and this is what they are doing?) I've not found this to be the case on my forums, quotes are still being used and the user tag is generally invoked to get a user's attention or when simply referring to a user when there isn't something to quote.
 

AndyB

Well-known member
#10
You can turn off the @ symbol in your options, and edit out the content from the templates. If you style it the same, they'll be none the wiser.
Hi King Kovifor,

Your suggestion doesn't disable the drop down when a member types the @ character followed by a few characters.
 

AndyB

Well-known member
#11
...user tag is generally invoked to get a user's attention or when simply referring to a user when there isn't something to quote.
I don't want members doing this either because it disrupts the flow of reading when you have tags inline with the text.
 

Jeremy

Well-known member
#12
AndyB, I may have mis-phrased, but as you can see over at XenAdmins, we've disabled the @ symbol before a tag, so it won't disrupt it. It won't disable the drop down, but really, how often will someone type "@" in a post. There's also a slight delay in the @ drop down appearing, so it may even not even be noticed.

ACP -> Options -> User Alerts -> [ ] Keep the @ character with user tagging
 
Last edited:

xf_phantom

Well-known member
#13
yea, the @ is hardcoded in the javascript file and there's no option to deactivate it..:(

i've just removed the call of initAutocomplete in the bb_code_edit.js file
 

xf_phantom

Well-known member
#16
I've created a new option (enableUserTagging), created a new event listener for event editor_setup (could be probably done via the Template Modification System too, to avoid the extra event listener)
PHP:
$editorOptions['json']['usertagging'] = XenForo_Application::getOptions()->enableUserTagging;
and this is the change in the js file
HTML:
if (this.options.usertagging){
                this.initAutoComplete();
}
 
Last edited:

AndyB

Well-known member
#17
Hi xf_phantom,

Thank you for sharing your knowledge. I'm afraid my level of understanding this type of coding is not there yet. Please tell me if the following is correct:

1) Your modification disables the drop down when the @ character is typed followed by a few characters.
2) You modified two files to do this.

If these two assumptions are correct, it would be great if you could explain which files were modified and where to place the code.

Thank you.
 

AndyB

Well-known member
#20
That works perfectly, xf_phantom. Thank you kindly.

Your one line template modification disables the user tagging function.

I prefer to add the code to the editor_js_setup template directly and here's what I did.

Code:
<xen:require js="js/redactor/redactor.js" />
<xen:require js="js/xenforo/bb_code_edit.js" />
<xen:require css="editor_ui.css" />

<script>
/* added code to disable user tagging */
XenForo.BbCodeWysiwygEditor.prototype.initAutoComplete = function(){};

if (typeof RELANG === 'undefined')
{
   var RELANG = {};
}

RELANG.xf = {
   image: "{xen:jsescape {xen:phrase image}}",
   link: "{xen:jsescape {xen:phrase link}}",
   link_insert: "{xen:jsescape {xen:phrase link}}",
   unlink: "{xen:jsescape {xen:phrase unlink}}",
   quote: "{xen:jsescape {xen:phrase quote}}",
   code: "{xen:jsescape {xen:phrase code}}",
   bold: "{xen:jsescape {xen:phrase bold_ctrl_b}}",
   italic: "{xen:jsescape {xen:phrase italic_ctrl_i}}",
   fontcolor: "{xen:jsescape {xen:phrase text_color}}",
   unorderedlist: "{xen:jsescape {xen:phrase unordered_list}}",
   orderedlist: "{xen:jsescape {xen:phrase ordered_list}}",
   outdent: "{xen:jsescape {xen:phrase outdent}}",
   indent: "{xen:jsescape {xen:phrase indent}}",
   none: "{xen:jsescape {xen:phrase none}}",
   align_left:   "{xen:jsescape {xen:phrase align_left}}",
   align_center: "{xen:jsescape {xen:phrase align_center}}",
   align_right: "{xen:jsescape {xen:phrase align_right}}",
   deleted: "{xen:jsescape {xen:phrase strike_through}}",
   underline: "{xen:jsescape {xen:phrase underline_ctrl_u}}",
   alignment: "{xen:jsescape {xen:phrase alignment}}",
   undo: "{xen:jsescape {xen:phrase undo_ctrl_z}}",
   redo: "{xen:jsescape {xen:phrase redo_ctrl_y}}",

   remove_formatting: "{xen:jsescape {xen:phrase remove_formatting}}",
   font_size: "{xen:jsescape {xen:phrase font_size}}",
   font_family: "{xen:jsescape {xen:phrase font_family}}",
   smilies: "{xen:jsescape {xen:phrase smilies}}",
   media: "{xen:jsescape {xen:phrase media}}",
  
   drafts: "{xen:jsescape {xen:phrase drafts}}",
   save_draft: "{xen:jsescape {xen:phrase save_draft}}",
   delete_draft: "{xen:jsescape {xen:phrase delete_draft}}",
   draft_saved: "{xen:jsescape {xen:phrase draft_saved}}",
   draft_deleted: "{xen:jsescape {xen:phrase draft_deleted}}",

   switch_mode_bb: "{xen:jsescape {xen:phrase use_bb_code_editor}}",
   switch_mode_rich: "{xen:jsescape {xen:phrase use_rich_text_editor}}",
  
   reply_placeholder: "{xen:jsescape {xen:phrase reply_placeholder}}",
  
   drop_files_here_to_upload: "{xen:jsescape {xen:phrase drop_files_here_to_upload}}",
   uploads_are_not_available: "{xen:jsescape {xen:phrase uploads_are_not_available}}"
};
</script>