I suppose you could create folders/files here called "blog" or "gallery" too, but then IP.Content pages are not served out of the board root in most cases, so the issue is mitigated.
I just want to quote and disagree with this comment. I don't know how you know these statistics but I think MOST customers should want their IP.Content pages served out of their domain root, which is also their "Board Root".
You're probably right that most don't, but that's because they don't understand how to fix their fURL's. Even Marcher doesn't do it for complexity and testing purposes, but I argue it makes most sites look unprofessional.
This is exactly what we're talking about with the inconsistency of IP.Content and other IPS apps/fURLs. We could create a folder, or a Page called "blogs" in IP.Content, yet that is already a fURL for the application "IP.Blogs", and there is also a physical folder in your root_folder called "blog" when you install IP.Blogs.
If I visit the following URL (typo) I get my 'default 404 page' as I defined in ACP > IP.Content > Settings.
www.domain.com/blogz (typo, no page exists)
If I visit the following URL I get my IP.Blogs homepage:
If I visit the following URL I get a 403 Forbidden Access page (ugly):
www.domain.com/blog (this is the name of a physical folder installed by IP.Blogs)
In other words you can't access a URL that is same path as a physical folder installed by IP suite. Therefore there is quite a few 'reserved' names you can't use for folders and/or Pages in IP.Content
So basically whenever we go to create a Page or Folder in IP.C there should be some background check to notify the admin if it conflicts with anything in use (fURL or physical file/folder).
Desired structure - Goals
2. myipb.com/forums - Start page for forums
3. myipb.com/forums/topic... - forums should be also included into URL of topics
Did you get the desired URL's for your forums and topics? I don't want to change my links this late in the game, but I'm hoping you can change the IN and OUT regex from "topic" to forums/topic" easily.
Now, on to the "Library" issue.
If you read the spoiler bit above, you'll know that a physical folder/file takes 'preference' when browsing your site over any IP.Content generated Page.
If I have a Page in IP.Content:
And I have a physical folder/file:
Then when I browse to "domain.com/test" or "domain.com/test/index.php" it will serve me up the physical file!
What if you create a phsyical folder in FTP called "library" and dump "index.php" file in it. Now I'm not sure what code should be in that "index.php" file though. Maybe this is where you'd use "external.php" or "index.php" from the IP.Content Tools folder?
Another option is just create a Page in IP.Content called "mylibraryhome.php" and use mod_rewrite with RegEx in .htaccess so when someone goes to:
"domain.com/library" or "domain.com/library/" that it re-directs them to "domain.com/mylibraryhome.php" but rewrites the path as "domain.com/library/"
In very fussy with having neat URL's, so like the ideas coming from this thread, and hope IPS pay more attention to fixing things in the near future so it's easier to customize and understand.