I created a page for a particular user (User-1 Information page). The User Specific Content plug-in adds meta information to the page creation page and I can select who can view this page by Role or by specific username (or whether the user is logged in or not),

After creating that page I use your redirect plug-in and point the use to that page as their redirect. It works beautifully! If another user logs in and plays with the address bar trying to guess at another user's page, they see a message telling them their current login does not allow viewing the page content.

There are only a few users who will use this. (Less than 25). So I'm not sure if or how this would work on a much larger scale, but for my purposes it works perfectly.

So, thank you again for the help!

-- Charlie

I can think of a couple of options:
- Build a special page type on WordPress with its own template that responds to the username variable in the URL so that the page content is built based on the URL variable
or
- If you have a small number of user-specific pages, you could build a mapping of username to page ID. To have that take effect in the redirect plugin, though, you'd have to build that mapping in the rulRedirectFunctionCollection::rul_get_variable() function in the plugin file.

Both options require coding in PHP.

This is for a site having to do with race horses. I'd like to give the clients a way to go to a personal page with any notes about training progress, race results, etc, but the information would be only pertaining to that client and the clients will not be able to see anyone else's information but their own.

This user name in the URL has me stopped at the moment :)

Thanks

In short, you can redirect to any page on your site, as long as the user has the permissions to view it. To manage permissions, though, you'd need a different plan, as my plugin only deals with redirects.

Yes, by using the syntax "[variable]username[/variable]" (documented in the plugin's readme.txt) you could craft URLs that are specific to users. However, this plugin does not cover user permissions — for that you'll have to use a plugin for that purposes, or build some logic into the relevant template to do the necessary checks.