Download
That's good to hear then 
I suppose it would be a self-tooting of the horn to support the feature
Your method seems the most easily workable at the moment, and it does the job just fine. Other methods you can think of (if they are achievable) are:
- Tickboxes for normal components that make them public/members only when output
- Your own [membersonly] [/membersonly] tags or something with a similar feature to this to put around the desired content
- A css class in the body tag called .loggedin or .member that is echoed once logged in so individual (and mass) html elements can be displayed as 'auto' or 'none' with css (in fact, this could be the quickest way for you to put the feature in: people just ensure that when their elements are within the 'logged in' class that the display setting is different). Downside: it is merely cosmetic, so the content will still be in the source code for people to see.
I suppose it would be a self-tooting of the horn to support the feature
Your method seems the most easily workable at the moment, and it does the job just fine. Other methods you can think of (if they are achievable) are:- Tickboxes for normal components that make them public/members only when output
- Your own [membersonly] [/membersonly] tags or something with a similar feature to this to put around the desired content
- A css class in the body tag called .loggedin or .member that is echoed once logged in so individual (and mass) html elements can be displayed as 'auto' or 'none' with css (in fact, this could be the quickest way for you to put the feature in: people just ensure that when their elements are within the 'logged in' class that the display setting is different). Downside: it is merely cosmetic, so the content will still be in the source code for people to see.
