Users must input the Thread ID or URL in the Thread field while filling the New Contract form. Since editing or updating contracts is not possible, this feature only works when creating new contracts.

ougccontractsystem05.png (Size: 76.74 KB / Downloads: 414)

Users are only allowed to attach one contract per thread and only to their own threads.

To customize the display of contracts in threads, you need to place the {$post['ougc_contract_system']} variable inside the postbit and postbit_classic templates. You can also adapt the contents of both the ougccontractsystem_postbit and ougcfeedback_postbit_button templates to fit your design structure.

ougccontractsystem10.png (Size: 52.41 KB / Downloads: 398)

To be able to embed contracts, both the sender and recipient of the PM have to match the Owner and Vendor of the contract.

The MyCode to embed contracts in PMs is the following :

[contract]n[/contract]

Where n is the Contract ID, which should be visible in the contracts list found in the contracts page in the User Control Panel (UCP).

This will work in both the core PM system as well as in the Symposium plugin.

You should be able to paste this variable inside the ougcfeedback_postbit, postibt, and postbit_classic templates.

If used inside the ougcfeedback_postbit template, then the average value should be appended to the {$post['ougc_feedback']} variable, this last variable in turn replaces <!--OUGC_FEEDBACK--> inside the postbit_author_user template and can be used in both the postbit and postbit_classic templates ( default ).

A recommended setup would be to use the {$post['ougc_feedback_average']} variable only inside the ougcfeedback_postbit template. *

To edit the output of the {$post['ougc_feedback_average']} variable you would need to edit the ougcfeedback_postbit_average template itself.

The $stats array variable can be used inside the ougcfeedback_postbit_average template to display additional or other data than the average stat. A list of all stats variables follow : **

• []{$stats['total']} to display the total amount of feedback,
  []{$stats['positive']} to display the amount of positive feedback,
  []{$stats['neutral']} to display the amount of neutral feedback,
  []{$stats['negative']} to display the amount of negative feedback,
  []{$stats['positive_percent']} to display the percentage of positive feedback relative to the total,
  []{$stats['neutral_percent']} to display the percentage of neutral feedback relative to the total,
  []{$stats['negative_percent']} to display the percentage of negative feedback relative to the total,
  []{$stats['positive_users']} to display the amount of unique users that gave positive feedback,
  []{$stats['neutral_users']} to display the amount of unique users that gave neutral feedback, and
  []{$stats['negative_users']} to display the amount of unique users that gave negative feedback.
  

* Please note that the value for the {$post['ougc_feedback_average']} variable will be updated by Ajax actions only if used inside the ougcfeedback_postbit template. Specifically only if inside the tag with class value of ougcfeedback_info_{$post['uid']}.
** Please note that the {$class} variable only matches the value of the {$average} variable.
*** Please note that the rendering of this feature is dependent on both the Show In Posts and Show In Forums settings.

oauth2uri.jpg (Size: 18.94 KB / Downloads: 510)

The URL for this setting should be similar to the following:

Where localhost is your forum URL (including domain, subdomain, or sub directory). Some examples are found below:

Additional URIs are not required for this plugin.

settings.jpg (Size: 27.52 KB / Downloads: 523)

• []Aplication Client ID and Aplication Client Secret
  The values for these both settings are found under the same page.
  • []Go to the applications page in Discord Developer Portal. https://discord.com/developers/applications
    []Your application Client ID and Client Secret can be found in the OAuth2 section of your application page.
    []If you regenerate your Client Secret, the plugin settings have to be updated as well.
    
  oauth2.jpg (Size: 32.09 KB / Downloads: 534)
  []Oauth2 Scopes
  The minimum scope requirements and default value for this setting is: identify guilds.join
  []Application Bot Token
  • []Go to the applications page in Discord Developer Portal. https://discord.com/developers/applications
    []Your application Bot Token can be found in the Bot section of your application page under the Username setting.
    []If you regenerate your Bot Token, the plugin settings have to be updated as well.
    
  bottoken.jpg (Size: 32.04 KB / Downloads: 519)
  []Guild ID
  To get your Guild ID, go to your Guild (Server), right click over the Guild name and you should get a menu. The Copy ID menu item should copy the Guild ID to your keyboard. The Guild ID is usually a set number of 18 digits.
  
  guildID.jpg (Size: 14.49 KB / Downloads: 490)

These are the essential settings required for the plugin features to properly work.

Configure additional settings to fit your board requirements.

botpermissions.jpg (Size: 57.44 KB / Downloads: 501)

• []Manage Roles
  []Create Invite
  []Change Nickname
  []Manage Nicknames
  
• Kick Members
  

All current features should work with these minimum permissions.

botpermissions2.jpg (Size: 37.25 KB / Downloads: 459)

To modify the display location of the side-box, follow the next steps.

1. []Open the portal template, find <!--OUGC_CRYPTO_PRICES--> and remove it.
   []Open any template, for example, header or footer templates, and place <!--OUGC_CRYPTO_PRICES--> anywhere within such desired template.
   

Please note that if <!--OUGC_CRYPTO_PRICES--> is found multiple times within the same page the side-box will be displayed multiple times as well. This is the reason removing <!--OUGC_CRYPTO_PRICES--> from the portal template is suggested.

* There are some templates where this will not work. Primarily, the Buddy List popup can not render the site-box. The amount of templates where this will not work is short but nonetheless should be considered.

To put it in short steps, as of the las update to this FAQ, the steps are as follow:

1. []Go to your API Keys account page by clicking here (https://www.coinpayments.net/index.php?c...t_api_keys).
   []Ideally you should create a new key to be used only by the OUGC Deposit Points plugin.
   []Once the key is created, you will need to edit its permissions.
   • []Key Enabled should be ticked.
     []Withdrawal Limits You must select the Currency to use for below limits value to match the plugin’s Requests Currency setting.
     []The following permissions are required:
     • []create_withdrawal
       []Allow auto_confirm = 1 in create_withdrawal (not recommended unless you absolutely need it) Is required if using the Auto Confirm Withdrawals plugin setting.
       
2. Save the key permission settings.
   
3. Paste the Public Key and Private Key values to the plugin’s CoinPayments Public Key and CoinPayments Private Key respectively.
   

These should be all the necessary steps in order to configure your CoinPayments API key settings for this plugin.

Below you would be able to see some images to help you understand what is described here.

apikey03.png (Size: 2.78 KB / Downloads: 414)

apikey02.png (Size: 6.44 KB / Downloads: 411)

apikey01.png (Size: 97.35 KB / Downloads: 428)

apikey00.png (Size: 5.54 KB / Downloads: 480)

Blockonomics wrote: The Blockonomics plugin will automatically update the order status when a bitcoin payment sent by your customer is confirmed. This works in all our ecommerce plugins. […]

However, it might be possible that even if Blockonomics displays a 200 status code the OUGC Deposit Points plugin will not display any IPN logs in the ACP.

To debug and resolve this issue please proceed to read the following Blockonomics help document to identify possible burdens in your side.

Order status not changing - callbacks failing
https://help.blockonomics.co/support/sol...ks-failing

emptytimecontract.png (Size: 33.69 KB / Downloads: 664)

The reason for this errors it that users don’t select a valid start time along the start date. To bypass this error users should select both a start date and a start time.

The error message should be improved in future versions to make this clear to users.

You can only grant a specific amount of new invite codes on a set interval of time to all users regardless of user active invite codes, or any other setting.

Follow the next steps to properly use this feature.

1. []First, go to ACP » User Groups » Edit User Group » Invite System » Maximum Active Invitations.
   []This setting allows you to set the amount of new invite codes to grant on a per group basis.
   []Then go to ACP » Board Settings » OUGC Invite System » OUGC Invite System.
   []This setting allows you to set the time interval between each new invite codes.
   []This setting allows you to set the amount of new invite codes to grant on a per group basis.
   []Finally, go to ACP » Task Manager » Edit Task » OUGC Invite System.
   
2. Make sure the task is enabled .
   

The task system has a limit of 50 users per execution so you might want to update the execution time based on the quantity of users your forum has.