Issue: Blocked Access to Default Namespace

Issue Tools
- View Changes

May 8, 2009 12:14 PM

Mokonzi

Senior Member

Blocked Access to Default Namespace

Sudden blocked access from Default Namespace after no setting changes

Ok... not sure why this problem exists... all I can do is explain the issue and the steps I took to correct it temporarily...

After posting a number of articles in the default namespace today (around 20) I came back after a break to find that the main Wiki Namespace (the default one) had disappeared from my forum list... while the other sections (Headers, Templates, etc) were still there.

I tried to access the wiki direct from the URL ID... and got blocked access (much like the special pages bug I mentioned earlier).

I checked all the settings, and resaved them all, no difference.
I rebuilt the namespaces... no difference.
I resaved the forum and the namespace individually... no difference.
I checked the permissions, all showed as allowing me access.
I then manually saved my user permissions access mask (to yes rather than default)... I now had access.
I changed it back to default... no access.
I changed the Administrators usergroup to custom settings, while not actually changing any settings themselves... I got access.
Reverting them I lost access again.

I'm not sure what caused the change. It seems I can now access the special pages in the earlier thread... and that was the only thing I'd attempted to do different...

So... no idea what causes it... or even if it's a proper bug... but here's the report anyways.

Issue Details

Issue Number 580

Issue Type Bug

Project VaultWiki 3.x Series

Category Namespaces

Status Not a Bug

Priority 3 - Loss of Functionality

Affected Version 2.2.3 Patch Level 1

Fixed Version (none)

Milestone VaultWiki 2.3.0

Software DependencyAny

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

May 8, 2009 1:17 PM

Mokonzi

Senior Member

Further investigation has revealed all usergroups are suffering this access issue.

Reply
May 8, 2009 1:19 PM

pegasus

VaultWiki Team

Please check your admin logs around the time you lost access and report back. Thanks.

Reply
May 8, 2009 1:28 PM

Mokonzi

Senior Member

CP Logs show only me doing anything at the time.

After the last of the new posts (during the posts, I'd been going back to the start of a new article page and then working forward with each new entry, etc.), the only CP logs show me editing the options. At the time that had been in connection with banning IP ranges (though I'd actually done this prior to the wiki posts), checking the options I'd set there so I could copy the IP banning for some spammers to the server settings.

I don't believe I actually changed anything.

Reply
May 8, 2009 1:32 PM

pegasus

VaultWiki Team

Perhaps in the cron logs? Access wouldn't suddenly be lost for no reason.

Reply
May 8, 2009 1:44 PM

Mokonzi

Senior Member

Nothing in the Scheduled Tasks log either... last thing done was a cancellation of an infraction at 8 this morning, not 3:30 this afternoon (my time) when things went crazy.

Reply
May 8, 2009 1:45 PM

pegasus

VaultWiki Team

In the mean time, try Maintenance -> Update Counters -> Rebuild Forum Information.

I will not be available for the rest of the day, so I hope this helps.

Reply
May 8, 2009 2:16 PM

Mokonzi

Senior Member

I'm afraid it hasn't done anything. I tested resetting to default and I get the same no permissions access. Do you want me to send you debug mode results at all now I've got the debug online?

Reply
May 9, 2009 5:14 AM

pegasus

VaultWiki Team

Generally if the forum's Display Order is 0, vBulletin does not build forum permissions for it. This results in a 0 permission, so the forum becomes inaccessible.

This is overlooked when the forum has no Display Parent, because the Display Order of this kind of "Parent: No One" forums are ignored during the permissions build (a parent wasn't faked).

This is not really a bug on either end, but should be documented since it's confusing as hell. Don't use Display Order 0 for visible namespaces anymore. Make sure the number you choose is unique among the namespaces using that parent, because vBulletin is quirky about duplicate display order.

Reply
May 9, 2009 7:11 AM

Mokonzi

Senior Member

Ok, I think I get most of what you are saying, so I'll list what I need to do and you tell me whether I'm write or not

Each namespace has a unique Display Order... 1,2,3,4,5,6,7, etc where it relates to a parent forum.

This makes me wonder how I hide the categories the wiki's currently reside in, because setting Display Order = 1 will show it on the forums...

I assume setting it not to be visible (but accessible by forum URL) will leave it visible where it's faked as the child where I want it displayed (I hope that makes sense... not sure how to explain it any better).

Reply
May 9, 2009 1:26 PM

pegasus

VaultWiki Team

Since we added the inheritance changes that you requested last version,

The namespace is treated as a child of the Display Forum.
- In vB, a child forum doesn't inherit permissions when the Display Order is 0.
- Display Order doesn't need to be 0, because it only appears in the Display Forum anyway.

If there is no Display Forum, you want Display Order to be 0.
- The namespace will still have permissions, because it is not a child forum of anything.

Reply
May 9, 2009 5:42 PM

Mokonzi

Senior Member

Works a treat matey. Thanks for the great support.

Reply
May 12, 2009 2:30 PM

tommythejoat

Regular Member

I think I must be hitting this same problem, but it really is confusing.

Everything displays properly except the Template Namespace. For example the Help Namespace that is identical except fot the forumid being 256 instead of 255 works fine.

All my wiki forums are currently set to display order 0 as instructed in the previous release but only Template seems to have a problem.

All of the Namespaces are children of Wiki Base, which is a normal non-wiki category forum.

Should I understand that if I give the namespaces artificial display order values like 1001,1002,1003... that it will clear this up?

As a side note moving the basic control screen for the wiki from the ACP drop down for Vault Wiki to vBulletin Options was very confusing for me. I left the wiki disable for several hours because I could still see almost everything, but there were lots of display glitches like images not showing. That is not a bug, of course, but a warning would have been nice.

Reply
May 12, 2009 8:31 PM

pegasus

VaultWiki Team

The Display Order 0 hack is no longer necessary. In fact, it now causes undesired effects. Set the Forum's Display Order to NOT 0. Make each one unique.

Reply

+ Reply

All times are GMT -4. The time now is 9:17 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

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

Issue: Blocked Access to Default Namespace

Issue Tools