mcsg

@GTServices Will this app allow us to add a user to a group when they register?
I do not want users to select a group, I want to automatically add them to the group on registration.

I know this is not the "right" way to do this, but I can hide it using js:
Theme > cms > databaseFilters
Add this at the bottom:
<script> var el = document.getElementsByName('cms_record_i_started_checkbox'); if(el[0]) { el[0].parentNode.parentNode.style.cssText = 'display:none'; } </script>  

How can I manage what groups can see different aspects of member profiles?
For instance, for RSVP events, Guests should not be able to view a member's RSVP events. Or posts.
And same for all activity in a member's profile. How does an admin hide the purchases, or Pages Databases from a Member's profile? Or from all profiles?
Ideally:
I do not want guests to be able to view other members profiles and data unless the member (or an admin) has chosen to have them fully public.
How do I (as an admin) selectively allow the different Member Profile sections to be viewable or not? By Group, by section?

And I realize it may not be possible to add a separate Cardholder name to the system, but when adding/entering a new credit card, I don't think the assumption should be that the Customer Name (which it does not show on the screen - though perhaps this is a setting somewhere...) is the same as the Card Holder name.

Thank you @bfarber. To sum up in case others come across this.
In order to display a Custom Field information in a Pages Database, determine the Pages <database_id> (a number) and use the following template code.
In this case, I am iterating over the custom fields that are marked to display above the content ('display_top') in the DatabaseTemplates > RecordDisplay > Record template.
 
{{foreach $record->customFieldsForDisplay('display_top') as $fieldId => $fieldValue}} <!-- fieldId is the field template identifier --> {{$field = \IPS\cms\Fields<database_id>::load( $fieldId, ‘field_key' );}} <!-- gets the field object --> Template Code: {$fieldId}<br/> Field ID: {$field->_id}<br/> Label: {$field->_title}<br/> Desc: {$field->_description}<br/> OR<br/> Label: {expression="\IPS\Member::loggedIn()->language()->addToStack( 'content_field_' . $field->_id )"}<br/> Desc: {expression="\IPS\Member::loggedIn()->language()->addToStack( 'content_field_' . $field->_id . '_desc' )"}<br/> Value: {$record->customFieldDisplayByKey($fieldId,'processed')|raw} {{endforeach}}  

This is default behavior in the default theme with 4.5 (and earlier?). Here, they're using a customized theme from the default that behaves differently.
There is no setting to change this behavior, however you could install or create a custom theme that addresses this.
No idea why it is the way that it is, but confirming it's not just you.

Thank you @Meddysong and @Paul E.!
I did not know that was there! I spend so much time in the AdminCP, I never thought to look there! Thanks very much!

Thank you @Meddysong and @Paul E.!
I did not know that was there! I spend so much time in the AdminCP, I never thought to look there! Thanks very much!

@Joel R Sorry this is old, but I'm interested in what you mean. Are you saying the IPS templates @Lindy was open sourcing for instruction are held by @opentype and @TAMAN? or to purchase the template pages plugins like SuperGrid, and Pages Article Styles ?
I am still very interested in real-world examples like @Lindy is suggesting about (I think) the IPS site. The IPS site is an excellent example of what can be done with Pages, but it remains beyond me to figure out how to duplicate some of the better parts of the site. With templates like from the IPS site, seeing the code behind the result would be an amazing boon to using Pages for CMS layouts.
Thanks.

If you're using the 1.1.0 version of the plugin with 4.4, I want to affirm that setting a dummy user as the anonymous user is a workaround to getting the plugin to work as TSP states above.
For our community, we cannot have all anonymous posts as one user, so we're waiting for an update to the plugin.

Thank you very much for letting us know! We really appreciate the work.
If I can be of any assistance: external testing, etc., please DM me. Happy to help in whatever way I can.

Hello, 
Sorry for the lack of updates. I have a lot to do at the moment, but I'll try to make something happen here this week. I'm sorry for the inconvenience. 

Is it going to be updated for 4.4.x ?