The table describes the possible commands and keywords for the plugin in the “Share on: (name)” column.

nojsbSuch a button should not be inside a “JS Share Button” (“dropdown” buttons). If not specified, then by default the button will be inside the “JS Share Button”. More details with examples here
afteractivityUsed for buttons in Activity Buddypress. Such a button should appear after the message content in the Activity. By default, the button will appear before the message content in the Activity. More details with examples here
intxtUsed for buttons that should appear in the body of a blog post and/or page text. Such buttons will be inserted into the post or page text instead of Shortcode
Shortcode:[yr-bpshare-button]. Only one Shortcode [yr-bpshare-button] is replaced in the post text. “intxt” buttons don’t appear elsewhere on the site. Marks for site sections for such a button are ignored. More flexible terms for “intxt” buttons can be provided upon request. More details with examples here
imgsrc=For example: imgsrc=
The image for the button will be taken from the specified link. You can give a link to any image of any size and see how they are displayed on the site. The keyword “imgsrc=” is more priority than setting the icons from the plugin sub-directory. The image settings from the plugin sub-directory on the admin page remain unchanged. More details with examples here
$buttonstyle=< >Recorded in a separate line of the table. You can change the style of the buttons below in the settings table. Example #1: $buttonstyle=<height: 32px; width: 80px; >
Example #2: $buttonstyle=<border: 2px solid red;>
Example #3: $buttonstyle=< > for style reset for buttons below
ifintitle=<xxx>Such a button will appear on the site only if the xxx text is in the title of the article (post) or in the name of the Buddypress group, or in the $title variable in the button link. Thus, for example, you can set different Join Viber Community buttons for different Buddypress groups.
$jsbname=<Button name1>Gives a name for the “JS Share Button”. Recorded in a separate line of the table, above the buttons that should go into the “JS Share Button”. There can be many buttons with different names. More details with examples here
buttonfblikeCommand for the appearance of the Like Facebook button. Large and small letters can be used. For example: fblike buttonFBlike afteractivity. (fblike is the name of the button, buttonFBlike is to generate the Like button, afteractivity is to be placed after the message in the Activity). Before this command, in separate lines, there should be commands for setting the Like button: style, size, and others.
$fblikeappid=<your-app-id>You must replace the value in your-app-id with the ID of your own Facebook App. You can find this ID using the App Dashboard. Optional parameter.
$fblikesize=<small>Button Size according to Like API (small, large, …). The default is small.
$fblikelayout=<button_count>Layout ccording to Like API (standard, box_count, button_count, button). The default is button_count.
$fblikeloc=<en_US>You can change the language of the Like Button. for example, fr_FR for French (France). Def en_US. One command in the table works.
$fblikedatashare=<true>true – display both buttons: Like+Share. false – display only Like. Default: false
$fblikestyle=< … >Additional styles for Facebook Like API buttons. For example: $fblikestyle=<display:inline;vertical-align:middle;position:relative;bottom:4px;>
Table 1. Commands and keywords in the “Share on: (name)” column

Leave a Reply

Your email address will not be published. Required fields are marked *