-
Edit privilege
I gave all my test users and myself, of course, edit privileges on the namespace I created.
The setting in the forum says there are no edit privileges. ???
When setting the privileges, it was rather inconvenient since I could not find any way to set the default privileges for the wiki area of forum privileges.
I just noticed in reviewing namespace help that it is recommended to just use the default namespace, but the instructions say to create a namespace with a new forum etc. and then repeat that process for all the built in name spaces.
When navigating in a forum namespace combination where the namespace appears as a subforum due to the use of the show field, the name space does not navigate back to the forum, but rather takes me to the top level of my board where the namespace forum is located.
Will I be able to integrate the various articles into my existing forums as I expected or will navigation always return up the wiki namespace tree instead of the show in forum tree?
-
To answer your questions in order:
The tags are explained on this page: WikiCodeList
This page is available as of the unstable release 2.2.1, which I don't recommend installing on a fresh wiki until the "Unstable" flag is removed. On that page the top half of the codes are for creating links, the next half, for other stuff.
We are still working on documentation for admins - until then we are here to answer any and all of your questions. Beyond that documentation, it's very likely we will leave it to admins to create a FAQ that corresponds to the way they have chosen to set things up. There are a lot of customization possibilities between all the managers, and it would be very difficult to create a general FAQ (or else result in a very vague unhelpful FAQ) that considers all the various configurations and only tells your users what they need to know.
That database error is indeed very odd. If you can find out exactly what the user was doing and exactly what the status of the article was (had it even ever been saved, for one), also if there were any PHP errors around the same time, I can look into this.
-
It is possible the privileges are separated from each other in your Usergroup Permissions. Look for the heading "CES VaultWiki Permissions". These must be enabled globally in Usergroup Permissions before custom forum permissions will work.
I admit the installation instructions and the namespace help differ. This is because the install instructions point to a general tutorial about creating namespaces. However, for the install, the act of having to click "Add New Namespace" was already done for you, so you have to click "Edit" instead.
When the breadcrumbs show the forum root rather than the "Display in Forum" path, this is intended. There was a possibility for an infinite loop when it was initially allowed (pre-2.1.0). Since then stricter rules about what kinds of forums you can select for "Display in Forum" have been put in place, so perhaps we can add this as an option again.
-
starting to sort it out.
If you can put the breadcrumb navigation back in, that would be very good for us. We only have a few admins and I believe we all can follow restriction rules if we know what they are.
I found the global Vault Wiki permissions. I was confused during the first pass because of the two entries for Vault Wiki Special Pages fairly high up and Vault Wiki down at the bottom.
The database error has not repeated itself. I will check the php error log to see if there is anything there.
I tried moving an article into a non-wiki forum, which was interesting. I had hoped to be able to copy articles to strategic locations in other forums. When I did the move, it became a standard post, of course, which I should have anticipated. When I moved it back it wiki'd again. I think I am starting to get a clue how this works.
-
Breadcrumbs are back in for the patch level 1.
-
Please note that after 2.2.3, if your namespace uses "Display in Forum", make sure the Top-Level forum's "Display Order" is a number (NOT 0). If it's 0, no one (not even admins), will be able to view the pages.