BumperRM

BumperRM 1.0.1

No permission to download
Requires XF v2.1+, and PHP 7.2+, Bumper add-on, and XenForo resource manager v2.1+

License:

This add-on can not be repackaged or redistributed in any form without the consent of the author.

Description:

BumperRM adds new permissions to give members the the option to bump their own, or others, resources to the top of the resource list. You can also set when the bump expires. Expired bumped resources will fall back in their proper order as if they were never bumped.

BumperRM does not modify any resource tables. If you un-install this add-on all bumped resources will fall back into their original position.

Features:
  • Bumper statistics (AdminCP -> Content -> Bumper statistics): Here, admins with the View statistics admin permission can view a list of active and expired resource bumps, with bump counts. You can also choose to expire selected active bumps or all active bumps.
  • Widget: BumperRM bumps can be set to appear in the Bumper widget.
  • New bumps list (What's new -> New bumps): BumperRM active bumps will appear in Bumpers New Bumps tab,
  • Allowing bumping is resource category based (AdminCP -> Resources -> Resource categories -> Select a category -> Allow bumping in this category): Check to allow bumping of resource items.
Options (Setup -> Options -> [EAE] Bumper):
  • Resource bumps expire in: Set when bumped resources will expire. Defaults to 7 days on install.
Permissions:
  • Number of resources that a member can bump per day (general, user group): This should be set to one if you allow multi-bumping to prevent excessive re-bumping of x amount of resources.
  • Bump own resources (per resource category, user group): Set to allow members to bump their own resources.
  • Bump resources by others (per resource category, user group): Set to allow members to bump others resources.
  • Multi-bump resources (per resource category, user group): This permission will allow members to re-bump active bumped resources. If a resource does not have an active bump and a member has no remaining bumps, the resource can not be bumped. If a member has no bumps left and a resource has an active bump, it can be re-bumped by the member.
  • A resource can only be bumped this many times (per resource category, user group): Set the maximum number of bumps a resource can have. Once this number is reached, a resource can not be bumped again (unless set to a higher value for another user group, premium for example). If you allow multi-bumping this should be set to a reasonable lower value.
Phrases:
  • start with eae_bprm_ prefix.
Screen shots:
  • bumper_stats_resource.png
    bumper_stats_resource.png
    42.6 KB · Views: 15
  • resource_bumper_option.png
    resource_bumper_option.png
    64.3 KB · Views: 13
  • resource_bumper_perms.png
    resource_bumper_perms.png
    48.2 KB · Views: 15
  • resource_category_option.png
    resource_category_option.png
    51.6 KB · Views: 16
  • resource_list_bump_icon.png
    resource_list_bump_icon.png
    83.8 KB · Views: 16
  • resource_view_bump_button.png
    resource_view_bump_button.png
    60.3 KB · Views: 16
  • whats_new_new_bumps.png
    whats_new_new_bumps.png
    46.7 KB · Views: 14
  • widget_with_resource.png
    widget_with_resource.png
    61.9 KB · Views: 15
Author
Lawrence
Downloads
7
Views
73
First release
Last update
Rating
0.00 star(s) 0 ratings

More resources from Lawrence

  • Thread Count
    Thread Count
    Displays the number of threads started by members, and adds four permissions based on thread counts.
  • Admin Tools
    Admin Tools
    Added features and conveniences for administrators, and as well two new permissions.
  • Bumper
    Bumper
    Allow members to bump content and prevent double-posting.
  • Conversation Tools
    Conversation Tools
    Administrators can view and delete user conversations and batch prune conversations within the Admin
  • Viewers
    Viewers
    Displays a list of members viewing a category, forum, page, and threads.

Latest updates

  1. Clean up

    - removed unused visitor instance from the category controller.
Top