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 Options to show a logged in user's registered events | Event Espresso - Staging Server
I was looking to find out what are the options for a given user to see their registered events on the front-end of the website after login.
I found [ESPRESSO_MY_EVENTS] shortcode; however, it doesn’t seem that there are any options available around controlling how that output looks and what goes there. 1) Is that the only option we have? 2) If so, how can I customize the output (add/remove columns), the way it renders the data. 3) It appears [ESPRESSO_MY_EVENTS] doesn’t follow the exiting template I have for event registration page. Is it intentional, how can I change that?
The [ESPRESSO_MY_EVENTS] is indeed the only front facing way the users can access that data. They can of course to the My Events section in their WP Admin.
Currently there isn’t a template available for that shortcode, meaning in order to customise it you will have to customise the core code in the WP User Integration (my_events_page.php).
In what way is it not following the existing template?
It looks like on my test site that the themeroller style sheets are getting loaded, but the html of the my-events shortcode may not have the required ids and classes to be picking up the themeroller rules. If you look in the file plugins/espresso-members/my_events_page.php starting on line 21 it starts outputting the html, line 74 it starts the html for the table head, and down on line 168 it is outputting the html for each row entry. If you can identify the classes and ids in the registration page that you want the themeroller rules to pick up, perhaps you can adjust the html output of the my events page to match those classes and ids.
Viewing 3 reply threads
The support post ‘Options to show a logged in user's registered 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.