So I spent some time actually figuring out what the problem is, since as I've said it's *never* worked properly for me for a long time.
The rewrite filter for both boards and topics just injects the board prefix as in the DB, but while the default board seems to get the proper prefix (e.g. locally I get localhost/wedge prefixes), nothing else seems to, so everything ends up with a / prefix, e.g. /new-board-2 which obviously doesn't work properly.
Going into these boards' configuration after the event also doesn't work because the pretty URL is just listed as (localhost) / (empty box)
Storing all this directly in the DB also has other problems with respect to users who decide to move their site around, because they'll not only have URL issues to deal with for reindexing, they'll also have to cope with editing every board.
Seems to me that we might need to find some other method of dealing with this - because while it's fine on wedge.org, it's no good for most other sites.
The rewrite filter for both boards and topics just injects the board prefix as in the DB, but while the default board seems to get the proper prefix (e.g. locally I get localhost/wedge prefixes), nothing else seems to, so everything ends up with a / prefix, e.g. /new-board-2 which obviously doesn't work properly.
Going into these boards' configuration after the event also doesn't work because the pretty URL is just listed as (localhost) / (empty box)
Storing all this directly in the DB also has other problems with respect to users who decide to move their site around, because they'll not only have URL issues to deal with for reindexing, they'll also have to cope with editing every board.
Seems to me that we might need to find some other method of dealing with this - because while it's fine on wedge.org, it's no good for most other sites.
