Issue: Tried to create wiki article, there was error, but I'm confused also

As for looking complicated, I'm not sure why. The forms, quick and full editor, both actually have fewer options than their VaultWiki 3 counterparts. But there are some new options you haven't seen before in VaultWiki 3, and maybe just that they're new makes them confusing.

Page functions aren't restricted by namespace in VaultWiki 4. There are no namespaces.

So, as an example: in order for you to have a template now, when you create a new page, you have to tell VaultWiki that you want the page to be a template. Otherwise it will just be a regular page.

As for editing the wiki article by default, I'm not sure if this is something we can do. We want to keep the form as simple as possible, required fields only and things you can't change later (page name, kind of page, save location). Maybe the page types could have more explanation, or maybe that is best for an FAQ entry.

Either way, the options are all controllable in the AdminCP. We have them all turned on at once for testing.

It seems also from your other reports, that you are confusing Prefixes with page types. The Prefix has no bearing on a page's functionality. It is just a word that you add before the title if you want to be more specific.

e.g. You have a page you want to name Fish, but there is an animal named Fish and a band named Fish. So if you had a Bands prefix and an Animals prefix, that's a way to tell the difference.

The reason we have namespace prefixes is because we upgraded from VaultWiki 3, so all the namespaces that were used in VaultWiki 3 were changed into prefixes, so the old articles would still work. There's really no reason to have that many for users who are new to VaultWiki, and no reason to use those words as Prefixes if you can avoid it. As mentioned in my previous post, you can limit the Prefixes users can select in various places from the AdminCP, but we have everything on for testing.

Page-types are different. They aren't related to a page's title at all, it's just an option you tick like "This page will be used as a template". You can also limit these for each area in your wiki, but we have them all turned on.

Yes, I must admit that I'm a bit confused, but in a way it can be a positive thing. You know what there is and why, but I don't. And from point of testing UI, this is always good, having someone who's confused and looks things with fresh set of eyes.

Now that you explained this to me, it looks like good idea (I never used prefixes in my wikis) and certainly this is something that regular users probably wouldn't see at all, as they wouldn't have privileges to create certain wiki types.

This will need explanation, probably that each wiki type have additional text explaining what this means. For example:

- Book (this creates ...)
- Category (this creates ...)
...

And you just need to phrase explanations so they could be translated in other languages. What do you think about something like this? It could help users know what each type does, what's the difference and why. Maybe even with links to corresponding section in FAQ where it is explaind with more detail?

I know that people need to know why they want to use something otherwise they won't use it at all (I don't use all features of VW3, and was delighted when I figured out what headers are, now I use them and couldn't live without them). So, just giving features to people isn't enough. People need to know what these features could do for them, how they can help them. I know this is a bit boring part, but it helps in selling all products. People buy things they want or need. If you want them buying something, make them want or need what you're selling.

You have great product, really exceptional, you give excellent support, but people don't know that they need it and want it and for what they need it and want it.

Made the options describe the options for "treat page as" a little more.

Marking as fixed.