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 Member/Subscriber log in No events...?! | Event Espresso - Staging Server
This is a strange one. If a subscriber is logged in and goes to the Upcoming Events (Main menu) page: http://ebwn.org/upcoming-events
The page content list No events…
Yet, if the subscriber is not logged in, then goes to the Upcoming Events page (events listed) and uses the sidebar log in widget which re-directs them to a profile page. Here, they again select Upcoming Events from the main menu and the events are listed and they can register.
Why does it list no events if one is previously logged in and list the events if one uses the side bar log in widget?
Please advise. Events should be listed regardless of when and where one logs in.
There might be an issue with Caching plugin serving up a cache file that was saved before there were any events. Can you try clearing the WP Super Cache plugin’s cache?
Along with that, since the upcoming events page is set to process the event registrations, it’s very important that this page gets set to not be cached. You can set specific pages to not be cached in the WP-super-cache advanced settings.
Under Settings->WP Super Cache Settings
under the “Advanced” tab and scroll down to “Accepted Filenames & Rejected URIs”
Viewing 3 reply threads
The support post ‘Member/Subscriber log in No 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.