Site Settings

From Lorekeeper Wiki
Jump to navigation Jump to search

Site settings are editable in the admin panel (requires the Edit Site Settings power).


These are the site settings that are added by default during setup.

  • admin_user (2.0.0)
    • By default, this is used to direct notifications for comments on site pages to an account. Extensions may also use this setting. It's recommended that this correspond to the ID of an account that is not used by any one person and is solely for administrative purposes.
    • Default: 1
  • blacklist_key
    • Optional key to view the blacklist. Enter "0" to not require one.
    • Default value: 0
    • This is a password for the blacklist page (if the page is made available for viewing). Note that this is not a very secure method of protecting the blacklist, and is primarily intended for temporary use.
  • blacklist_link
    • 0: No link to the blacklist is displayed anywhere, 1: Link to the blacklist is shown on the user list.
    • Default value: 1
  • blacklist_privacy
    • Who can view the blacklist? 0: Admin only, 1: Staff only, 2: Members only, 3: Public.
    • Default value: 1
  • design_votes_needed (2.0.0)
    • The number of votes needed for consensus on a design update.
    • Default: 3
  • gallery_submissions_open (2.0.0)
    • Whether or not gallery submissions are open globally.
    • Default: 1
  • gallery_submissions_require_approval (2.0.0)
    • Whether or not gallery submissions require approval.
    • Default: 1
  • gallery_submissions_reward_currency (2.0.0)
    • Whether or not gallery submissions reward currency.
    • Default: 0
  • group_currency (2.0.0)
    • ID of the group currency used for gallery submission rewards, if enabled.
    • Default: 1
  • is_claims_open
    • 0: New claims cannot be made (mods can work on the queue still), 1: Claims are submittable.
    • Default value: 1
  • is_design_updates_open
    • 0: Characters cannot be submitted for design update approval, 1: Characters can be submitted for design update approval.
    • Default value: 1
  • is_myos_open
    • 0: MYO slots cannot be submitted for design approval, 1: MYO slots can be submitted for approval.
    • Default value: 1
  • is_prompts_open
    • 0: New prompt submissions cannot be made (mods can work on the queue still), 1: Prompts are submittable.
    • Default value: 1
  • is_registration_open
    • 0: Registration closed, 1: Registration open. When registration is closed, invitation keys can still be used to register.
    • Default value: 1
  • is_reports_open (2.0.0)
    • Whether or not reports are open.
    • Default: 1
  • open_transfers_queue
    • 0: Character transfers do not need mod approval, 1: Transfers must be approved by a mod.
    • Default value: 1
    • If set to 1, transfers and trades will go through the usual mutual acknowledge/accept process, then get placed into a transfer queue where staff can review the transfer. This also allows staff to edit the transfer cooldown periods of transferred characters.
  • transfer_cooldown
    • Number of days to add to the cooldown timer when a character is transferred.
    • Default value: 3
    • Note that in circumstances where a staff member has to officiate a transfer, the staff member will still be able to manually edit the cooldown applied in that case (the transfer cooldown is filled in automatically for convenience). This value primarily applies in situations where users transfer characters without requiring approval.

See Also