• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 4.x Series
    • Feature
    • Giving each wiki article it's own editorial rights?

    1. Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: Giving each wiki article it's own editorial rights?

    • Issue Tools
      • View Changes
    1. issueid=2316 April 21, 2010 1:40 PM
      Jaxel Jaxel is offline
      Junior Member
      Giving each wiki article it's own editorial rights?

      Right now wiki article editing rights are handled through usergroup permissions... and forum permissions...

      What I want to be able to do is, I want to disable all editing rights to my registered members. They can CREATE articles, and edit their own articles, but they should not be able to EDIT any article that does not belong to them. Then I want owners of articles and administrators to be able to give editing rights individually to users and articles. So an owner of an article/administrator can say "I want to give userX the ability to edit articleY". Each article should be able to have it's own editing rights.

      Is something like this possible?
    Issue Details
    Issue Number 2316
    Issue Type Feature
    Project VaultWiki 4.x Series
    Category Permissions / Security
    Status Implemented
    Priority 8 - Major Features / Enhancements
    Suggested Version 3.x
    Implemented Version 4.1.0 Beta 2
    Milestone VaultWiki 4.2
    Software DependencyAny
    License TypePaid
    Votes for this feature 1
    Votes against this feature 0
    Attachments 0
    Assigned Users (none)
    Tags (none)


    Page 2 of 2 FirstFirst Previous 12


    1. April 23, 2012 3:28 AM
      pegasus pegasus is offline
      VaultWiki Team
      Bringing this to the front so that the default protection setting is added for 4.0.0 Alpha 1. caneditown is not needed so long as the default protection is author-only.
      Reply Reply  
    2. April 23, 2012 5:48 AM
      Alan_SP Alan_SP is offline
      Regular Member
      Just found this.

      What is my suggestion and I think you already have that in mind is that there's always check if user is thread or article starter. That we can give some permissions based on fact if user started thread or article.

      For example, I installed mod that enables indefinite editing of first post of any thread by thread author.

      And with thread headers (similar to now existing forum headers, but they work in threads in the same way (or more advance)) for example, I'd like to enable that thread starter could work on them, but other users don't.
      Reply Reply  
    3. April 23, 2012 5:45 PM
      pegasus pegasus is offline
      VaultWiki Team
      Default protection added to the Area Manager.
      Reply Reply  
    4. April 26, 2012 5:32 AM
      pegasus pegasus is offline
      VaultWiki Team
      Unnecessary to disable caching for user-defined and user-level permissions. Instead, we can use a flag in the vw_user table like hasmask to alert us that this user requires an extra query. But the rest can be fetched from cache. Likewise, we can use the user's moderator membergroup to tell us that the user is a moderator, and query the permissions table for the extra moderator stuff. This way we aren't clogging up the cache with user-level permissions, but we're still caching permissions that apply to everyone.
      Reply Reply  
    5. April 26, 2012 10:53 PM
      pegasus pegasus is offline
      VaultWiki Team
      Or, make some changes to the permissions fetcher...

      Remove permissionkey field (node type id : node id : permission type : applies to id)
      Replace with applykey field (applies to id : permission type)

      Then we can search on applykey to get all permissions relevant to the current user, rather than all permissions relevant to the current page. Doing it this way is more intuitive and saves 5 queries on the all-feature test page.

      Surely we can save 1 more query (except masked users and mods) by implementing the change in the previous post (caching group-level permissions), but the question is should we?
      Reply Reply  
    6. July 7, 2013 10:16 AM
      Alfa1 Alfa1 is offline
      Distinguished Member
      Has this been implemented?
      Reply Reply  
    7. July 7, 2013 10:44 AM
      pegasus pegasus is offline
      VaultWiki Team
      Not yet, the form controls and handling for this have not yet been created. However, our permissions system already saves by page-ID rather than area-ID since Alpha 1 Badger in order to prepare for this feature.
      Reply Reply  
    8. October 15, 2013 10:58 AM
      pegasus pegasus is offline
      VaultWiki Team
      Originally suggested for 3.0.11.
      Reply Reply  
    9. June 24, 2019 1:15 PM
      pegasus pegasus is offline
      VaultWiki Team
      As a way of implementing something akin to XenForo's "Reply Bans" feature, but with slightly more control,
      This is implemented in 4.1.0 Beta 2:

      There is now a form where you can Allow/Block against specific users, for specific actions for permanent/temporary durations. If Block is used, the user's permissions are ignored, and they cannot perform the selected actions on that content. If Allow is used, the user's permissions are ignored, and they are allowed to perform the selected actions on that content anyway. If there are competing Allow and Block rules for the same user-action combination, the Block is used.

      For pages:
      - The form is part of the Protect tab. You may allow/block the Edit action.
      This should allow pages which are collaboration protected, or have any other protection, to be editable by specified users.

      For feeds:
      - The form is part of the Protect tab. You may allow/block Adding entries to the feed.
      This should allow feeds which have entry protection, to receive new entries from specified users.

      For discussions:
      - The form appears under the "Manage Reply Bans" link. You may allow/block Replies.
      This should roughly emulate the reply-bans function.
      Reply Reply  
    Page 2 of 2 FirstFirst Previous 12
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 5:49 PM.
    This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Learn more… Accept Remind me later
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2023 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2023 DragonByte Technologies Ltd.
    Copyright © 2008 - 2013 VaultWiki Team, Cracked Egg Studios, LLC.