• 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
    • Bug
    • Cannot edit certain wiki page

    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: Cannot edit certain wiki page

    • Issue Tools
      • View Changes
    1. issueid=4279 April 20, 2015 11:24 AM
      beernuts beernuts is offline
      Junior Member
      Cannot edit certain wiki page

      For some reason, after the latest patch upgrade, we are completely unable to edit one (possibly more) wiki page on our site. What are the potential causes for this issue?
    Issue Details
    Issue Number 4279
    Issue Type Bug
    Project VaultWiki 4.x Series
    Category Permissions / Security
    Status Fixed
    Priority 3 - Loss of Functionality
    Affected Version 4.0.3
    Fixed Version 4.0.4
    Milestone (none)
    Software DependencyAny
    License TypePaid
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. April 20, 2015 11:42 AM
      pegasus pegasus is offline
      VaultWiki Team
      There are no changes to default edit permissions in 4.0.3.

      If this is only happening for some articles:
      • The article might have an edit that is waiting for a moderator to review it.
      • The article might be protected.

      I would know more by looking at the article that you can't edit.

      Between 4.0.2 PL and 4.0.3, the only global change is a check to bypass the query for moderators if the wiki moderator group is not defined. This would not have any negative effects.

      Since 4.0.2 PL, NEVER permissions work again. "Never" overrides all Yes for the user that has a Never. It was not working in 4.0.2. So: If any of your usergroups has "Never" for edit permissions, and you are a member of that usergroup, then you are not allowed to edit, even if a different group would allow you.

      Before 4.0.2 PL, it was possible to moderate things if you were not a moderator. This is no longer possible.

      Since 4.0.1 PL, users in banned primary groups no longer inherit permissions from secondary groups (reading the description of some banned settings, this is the expected behavior). Therefore: If your primary group is not allowed to have secondary groups, and your edit permissions were earned only from the secondary group, then you are not allowed to edit.
      Reply Reply
    2. April 20, 2015 2:51 PM
      beernuts beernuts is offline
      Junior Member
      Our Wiki mod who noticed the problem is listed under the Wiki moderators page in the admincp.

      I'm submitting a support ticket now.
      Reply Reply
    3. April 20, 2015 3:34 PM
      pegasus pegasus is offline
      VaultWiki Team
      This occurs for any pages that someone has used "Undo" on an edit since 4.0.2 PL. It looks like it treats every user doing this (even admins) as if they need to wait for approval. You can restore the affected pages by going into the history for the page and approving/denying the most recent undo action.

      I am still trying to find out why all users are being treated as needing moderation for Undo.
      Reply Reply
    4. April 21, 2015 9:14 AM
      beernuts beernuts is offline
      Junior Member
      1. Our main Wiki manager does not see the "Approve" option. Only an "Undo" option.

      2. Even after approving / denying ALL pending changes, we're still not able to edit it.
      Reply Reply
    5. April 21, 2015 10:43 AM
      pegasus pegasus is offline
      VaultWiki Team
      If we are looking at the same wiki article that you sent me, the reason for #2 is that there is still a pending change. I literally checked the article right now and it says "This page has an edit awaiting moderation." I can see the edit at the very top of the History tab. I also only made my previous post after confirming this behavior and that I was able to edit the post after using the "Approve" option.

      I can tell you that I can see the "Approve" option on the page in question when using the test account you provided. If your main wiki manager does not see an "Approve" option, then he is either not defined as a Wiki Moderator on the Admin Panel's Moderators page, he does not have "Can moderate wiki content?" under the "Moderator Permissions" heading, or one of his other usergroups has "Never" selected for "Can moderate wiki content?" I do not know who your main wiki manager is to check any of that myself.

      I figured out why all "Undo" was requiring moderation, even from moderators using "Undo". It was due to a failed merge with one of the code branches in 4.0.2 last month. This is fixed in 4.0.3 build 002, which you can download now.
      Reply Reply
    6. April 22, 2015 10:08 AM
      pegasus pegasus is offline
      VaultWiki Team
      Okay, it seems an article can become in this locked state if it already has an edit awaiting moderation and someone performs an undo action before that other moderated edit is approved or denied. It should not be possible to make any changes, including undo, while moderation is pending. It is also an issue that the logic for the article's locked state differs from the logic for 'can-approve' (if an edit is not the newest edit, it is assumed that it is not waiting for moderation, but the code that removes the edit lock checks for any pending edit without checking how new it is).

      This would get you into the state you have now where there is an edit waiting for moderation but no one is allowed to approve it.

      The first thing you need to do is make sure this doesn't happen again. In vault/core/controller/dm/revision/vw.php, find:
      Code:
      			$pending = vw_DB::get()->query()->select(array(
      				'fields' => array(
      					'revisionid',
      					'userid'
      				),
      				'table' => 'vw_revision',
      				'where' => array(
      					vw_DB::get()->query()->eq('pageid', $pageid),
      					vw_DB::get()->query()->eq('visible', 0)
      				),
      				'order' => array('dateline' => 'DESC'),
      				'first' => 1
      			));
      Replace with:
      Code:
      			$pending = vw_DB::get()->query()->select(array(
      				'fields' => array(
      					'revisionid',
      					'visible',
      					'userid'
      				),
      				'table' => 'vw_revision',
      				'where' => vw_DB::get()->query()->eq('pageid', $pageid),
      				'order' => array('dateline' => 'DESC'),
      				'first' => 1
      			));
      
      			if ($pending AND $pending['visible'] != 0)
      			{
      				$pending = false;
      			}
      Next you will need to remove the lock from the affected page with a query like so:
      Code:
      UPDATE vw_page
      SET has_pending = NULL
      WHERE pageid = 8298
      LIMIT 1
      This fix is now included in 4.0.3 build 002.

      Regarding the user you mentioned... The permission that says whether a user can approve edits or not is in the wiki permissions under the "Moderator Permissions" heading. It asks "Can moderate wiki content?" There is only one usergroup that I have seen that has been given this permission, and it is the Administrators group. I checked all the usergroups that the user in question is part of, and this permission is set to No for all of them. If you want the user to be able to approve or deny moderated content, including edits, then he needs to be in a group that has this permission. And that is not the case currently.

      Another issue I see that may creep up eventually. It is not related to this issue but I wanted to point it out. The user is listed on the Wiki Moderators page, however when I look at that user's settings in the regular user settings admin page, it looks like you manually removed at least that one user from the related "Wiki Moderators" usergroup after adding him as a moderator. So he is listed as a moderator but will not gain any permissions from being a moderator (all the permissions for the "Wiki Moderators" group are set to No anyway, so it does not matter right now). However, if you start changing the permissions of the "Wiki Moderators" group or give the user personal overrides on the Moderators page, those changes will have absolutely no effect and this will be the reason.
      Reply Reply
    7. April 22, 2015 10:31 AM
      pegasus pegasus is offline
      VaultWiki Team
      This is fully fixed in the next release. While 4.0.3 build 002 prevents this from happening anymore, the 4.0.4 upgrade script fixes articles (and attachments) that were damaged in this way.
      Reply Reply
    8. April 22, 2015 11:32 AM
      beernuts beernuts is offline
      Junior Member
      Thank you for your reply. We have fixed the article in question.

      Regarding the users, however, we did not add those users to the Wiki moderators. We've never touched that part of the system. In fact, it just looks like a list of administrators on our site. Are you sure Vaultwiki didn't auto add administrators as Wiki moderators at some point in the install or upgrade process?

      Similarly, we have never messed with the "Wiki Moderators (Default)" usergroup. We've never added anyone to that group and we've never removed anyone from that group. So I'm not sure what's going on with the moderators / usergroups but the user in question has never had a problem editing, protecting, deleting articles and we've never messed with that usergroup.
      Reply Reply
    + 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 12:44 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 © 2025 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2025 DragonByte Technologies Ltd.
    Copyright © 2008 - 2024 VaultWiki Team, Cracked Egg Studios, LLC.