Enforces that users attempting to access the area have either forum or helpdesk administrative privileges, loads the SimpleDesk administrative CSS and Javascript and promptly directs users to the specific function for the task they are performing.

• since: 1.0

This function primarily collects information about SimpleDesk before handing over to the template:

• list of helpdesk staff
• totals of tickets in the system (open/closed/deleted)
• credits
• also, in the template, whether this is a current or outdated version of SimpleDesk

• since: 1.0

This function handles all the sub areas under General Options, and adds the options listed below in $modSettings. Display options

• 'shd_staff_badge' (dropdown) - selects the type of badge(s) to display:
  • nobadge (default): Display no badges, just a small staff icon for staff members
  • staffbadge: Display nothing for normal users, and badge/stars for staff
  • userbadge: Display nothing for staff and normal badge/staff for regular users
  • bothbadge: Display regular badges/stars for both staff and users
• 'shd_display_avatar' (checkbox) - whether to display avatars in the replies area or not
• 'shd_ticketnav_style' (dropdown) - selects the type of navigation in the ticket area:
  • sd (default): use the original SimpleDesk style, icons+text in the bar just above the main ticket area
  • sdcompact: use the SimpleDesk icons, in the bar just above the main ticket area, but no captions
  • smf: use an SMF style button-strip above the ticket menu
Posting options
• 'shd_allow_ticket_bbc' (checkbox) - one-stop enable/disable of bbcode in tickets (see {@link} for where this is used)
• 'shd_allow_ticket_smileys' (checkbox) - one-stop enable/disable of smileys in tickets (see {@link} for where this is used)
• 'shd_attachments_mode' (dropdown) - selects the presentation of attachments to users:
  • ticket (default): treat attachments as if they are attached to the ticket overall; do not enforce max number per ticket
  • reply: treat all attachments as attached to replies; enforce same limit per reply as with posts normally
• 'shd_bbc' (bbc) - enable/disable individual BBC tags around the helpdesk (see {@link} for where this is used)

• 'shd_disable_action_log' (checkbox) - if checked, no actions are added to the action log.
• 'shd_staff_ticket_self' (checkbox) - if checked, a ticket opened by a staff member can be assigned to them to action.
• 'shd_privacy_display' (dropdown) - whether to display privacy or not:
  • smart (default): Display ticket privacy if it's likely to be relevant (if users can alter ticket privacy, and/or see private tickets AND the ticket is private, show it)
  • always: Always display ticket privacy; likely to be confusing

• 'shd_helpdesk_only' (checkbox) - if checked, Standalone mode is active.
• 'shd_disable_pm' (checkbox) - if checked, personal messages will not be available at all when SimpleDesk is in (active) Standalone mode
• 'shd_disable_mlist' (checkbox) - if checked, the memberlist will not be available at all when SimpleDesk is in (active) Standalone mode

• see: \shd_format_text()
• since: 1.0

Parameter: $return_config

Expected type: mixed

Parameter: $override

Expected type: mixed

Default: ''

SMF 2.0 features an admin search area, and to identify what settings there are, it calls the function that will handle the searching, which is required to then return a list of possible options' language strings. Since all of the SD options are currently handled in a single parameterised function, we have to provide a non-parameterised version that the ACP can call, which is this function.

• since: 1.0
• see: \shd_admin_options()

Parameter: $return_config

Expected type: bool

Whether to return configuration items or not; this is provided solely for SMF ACP compatibility (it expects to pass bool true in to get a list of options)

SMF 2.0 features an admin search area, and to identify what settings there are, it calls the function that will handle the searching, which is required to then return a list of possible options' language strings. Since all of the SD options are currently handled in a single parameterised function, we have to provide a non-parameterised version that the ACP can call, which is this function.

• since: 1.0
• see: \shd_admin_options()

Parameter: $return_config

Expected type: bool

Whether to return configuration items or not; this is provided solely for SMF ACP compatibility (it expects to pass bool true in to get a list of options)

SMF 2.0 features an admin search area, and to identify what settings there are, it calls the function that will handle the searching, which is required to then return a list of possible options' language strings. Since all of the SD options are currently handled in a single parameterised function, we have to provide a non-parameterised version that the ACP can call, which is this function.

• since: 1.0
• see: \shd_admin_options()

Parameter: $return_config

Expected type: bool

Whether to return configuration items or not; this is provided solely for SMF ACP compatibility (it expects to pass bool true in to get a list of options)

SMF 2.0 features an admin search area, and to identify what settings there are, it calls the function that will handle the searching, which is required to then return a list of possible options' language strings. Since all of the SD options are currently handled in a single parameterised function, we have to provide a non-parameterised version that the ACP can call, which is this function.

• since: 1.0
• see: \shd_admin_options()

Parameter: $return_config

Expected type: bool

Whether to return configuration items or not; this is provided solely for SMF ACP compatibility (it expects to pass bool true in to get a list of options)

This function loads the language strings, and hands off to {@link} to perform the actual log generation. Before doing so, however, this function will also prepare for deletion of old entries, as well as sorting out the columns and ordering rules before handing control to the other function.

• since: 1.0

Very small function because essentially it just loads a template; there is no logic or processing to actually perform.

• since: 1.0

This defines the list of peoples' names, and none of it will be in language strings; the actual category titles and positions will be, but the names themselves can live in this file normally.

• since: 1.0