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 Event Categories Template Pages Problem... | Event Espresso - Staging Server
I’m using archive-espresso_events.php in my theme…works great. However, for my individual categories (in my case, “Private” and “Public” with corresponding lowercase slugs) they revert back to the general archive page which isn’t how I want it to display. I’ve tried using custom taxonomy pages to no avail. All I want is the category pages to look exactly like the above archive page which list ALL events.
It seems taxonomy is the way to go…but I’ve tried many formats to get it to work:
You’ll likely run into some issues with using this right now though because there is some ongoing work with working though all the bugs in of Event Espresso 4 beta’s templating functionality now that it’s all based on Custom Post Types. When I checked into this I found another bug that I need to report to the team. I’ll keep you posted on this.
That’s one of the bugs I found too. I mentioned this to the dev team and it looks like what they’ll need to do is create a really wide scope template tag that will load the View helpers then that template tag can be put at the top of the base template files.
Okay, thanks, Josh. So we’ll just need to wait for the next version I assume. Is there anyway to manually load the view helpers into pages where I want to use them?
I’m not aware of a way to manually load the view helpers outside of the Event Espresso template hierarchy. There is another way to load up an archive of a category of events by using a shortcode like this on a page:
[ESPRESSO_EVENTS category_slug=”private”]
Viewing 5 reply threads
The support post ‘Event Categories Template Pages Problem…’ 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.