Re: Why using pages for BP sections is a bad idea
Yes pages can be deleted, but that’s not the big problem, rather the fact that the plugin uses pages at all to accomplish something so simple. What was wrong with the current system? It’s important to make the software easy, but somethings should be left to the developer of the site and not the admin guy who just writes blog posts, I much preferred changing the URLS in the code behind, but a settings page would be much nicer and slicker than the messy pages.
Here is another point: The pages don’t add that much flexibility anyway as most of the urls are still coded behind e.g. all the urls inside the members directory such as settings, profiles, followers, etc.
I think their should be a proper coded page in the plugin somewhere that has the urls in the system where a developer can go and edit to their hearts content to get the system they want. So for example say I didn’t want the members slug on profiles and just wanted: domain.com/driz/activity, using code behind would give true flexibility instead of using the pages which are for static content and NOT url building!
