Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Hide Member's Only Events? | Event Espresso - Staging Server
Is there a way to hide members only events on a per event basis? I see the option for “public” but the list does not include Private. I’m asking because some of our events we would only like for the Members to know the location of, and I can hide the related post with the membership plugin, but the event still displays the information in the event list, so it kind of defeats the purpose of having the related post hidden.
One thing you could is set up 2 categories, one for members only events and another for non-members only events. Then you could use the [EVENT_LIST category_identifier=members_only_event] shortcode on a page that is only viewable by members, and use the [EVENT_LIST category_identifier=non_members_only_event] shortcode on a page that is viewable by anyone. Of course your category identifiers may be different than what I have here.
Then you could remove the [ESPRESSO_EVENTS] page from the navigation. But, do not delete this page or remove the shortcode. Only remove it from the navigation.
Viewing 1 reply thread
The support post ‘Hide Member's Only Events?’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
This is a meta description test for the WP User integration.