Help with full "fake" directory structure URL

[eluser]jedd[/eluser]
[quote author="alphane" date="1253764145"]
Have I made things any clearer?
[/quote]

Slightly. The problem I had with 'page' is you were using it to describe different things, in the one sentence!

I had a quick look through the user guide for any reference to this "__call()" feature, and can't find anything on the subject, can you shed any light on that?

I keep a documentation browser open all the time that has the CI UserGuide on one tab, the MySQL doc on the next, PHP on the third, and a git cheatsheet on the fourth.

In this particular case I'd point you at my third tab.

Remember, always, that CI uses PHP - and that means you can too.

For example ...

Where this is confusing me is that I can’t use a standard method as I will have an unknown amount of URI segments being passed to a given function, so I need to manually grab the URI segments and try to find a match in the database and work my way back through valid pages

You may want to look up the func_get_args() and func_num_args() functions, and see if they might be of assistance in dealing with your unknown number of URI segments. I've not used them before, but they seem fairly straightforward.

I'd encourage you to have a 'wiki' controller, and everything under http://site.name/wiki/ ... used some feature (maybe one of the ones I've mentioned) to give you this virtual mapping of All Things, but still provides for hard coded 'about us' (to pick a bad example) pages. It means you can still have an About_Us page that's owned and managed by your wiki - it'll just be different to the static one that your about_us() controller would offer. As I say, 'about us' is a very poor example, but there will definitely be occasions where you want some semi-static, or at least non-wiki-managed pages.