Issue: Allow areas to have prefixes

Sounds like you've got a firm grasp on areas and prefixes.

As for your request, there was a particular problem during early development of 4.x that preventing areas themselves from having prefixes resolved, although I can't remember what it was at the moment. The only things I can think of are possible scope issues when trying to link directly to the area, or it might have just been fieldname confusion before the area's prefixid field was changed to prefixlist (so no longer a valid reason). If I can't think of a great reason after a while, I'll accept this request.

Since areas are titled by the admin anyway, why can't you hard-code the prefix into the title itself for now? If you don't like the way it looks in the final page, use this BB-Code in the area's Edit tab:
The defined prefix select box is meant more as a convenience for your end-users.

1. There are two problems. Changing the display title doesn't change how it looks in the breadcrumbs.

2. If I require a certain prefix in an Area, I can't use that prefix on the area itself, so I get an error when I try to edit an area page. The error says:

Can you clarify #2? There are at least two things I think you could mean.

Case 1:
- Area requires 'Prefix-A' but does not allow [No Prefix]
- Area title has no prefix
- Editing Area but leaving area title with no prefix shows prefix_not_allowed error because [No Prefix] is not allowed

Case 2:
- Area requires 'Prefix-A'
- Attempting to set area title as 'Prefix-A:Area' shows prefix_not_allowed error

Requiring a prefix in an area shouldn't require the prefix on the area itself, so I think it's a bug. If I create a new area, and the only prefix I allow in it is "SMBC", then I should not have to use that prefix on the area itself, only pages in that area. It should however, require that all child areas require that prefix. But this is not possible.

Even if I put "SMBC:" before the title, I still get the error.

Both case 1 and 2 are true. Case 2 I only tried on a subarea.

I've moved that to a new bug: https://www.vaultwiki.org/issues/4048/

This way your OP doesn't get hijacked or this feature request closed when only the bug is addressed. Any follow-up to the prefix_not_allowed issue should be posted in that new report.

This is implemented in 4.1.0 Beta 3. This resolved a bug since 4.1.0 Alpha 1 where area titles that included a prefix as part of the title text had undefined behavior: the prefix-matching part was stripped in some cases, or editing the area threw a prefix-not-allowed error.