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 Calendar 404 if not at root | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Event Calendar 404 if not at root

Event Calendar 404 if not at root

Posted: April 12, 2014 at 3:29 pm

Viewing 3 reply threads


Greg Cole

April 12, 2014 at 3:29 pm

Just updated to the latest build (4.2.003.beta) and the Event Calendar (3.0.01.beta) but the calendar page will not display (throws a 404 Error) if it is nested/a child document. I have a page (/events) and then the calendar (/events/calendar) and the calendar page has the correct shortcode. If I move the calendar page to the site root (just /calendar), it works. I have tried to reset permalinks, re-save template settings, etc. with no joy.


Greg Cole

April 12, 2014 at 3:51 pm

If I change my Event Listing page to /event-list, the problem goes away. It looks like having a page at /events gets ignored as the plug-in uses this as the custom post-type archive page, and child pages beneath this will not properly display.

How can I use the default /events display (vs. using the [ESPRESSO_EVENTS] shortcode on my page) and still add child documents? I know I can use the menu manager to fix the top site navigation, but breadcrumbs would leave the calendar at the root.


Dean

  • Support Staff

    •

April 14, 2014 at 1:24 am

Hi Greg,

I don’t believe there is a way to have /events/calendar. The reason being is the archive over rules the page with the same name so it is assuming that the calendar is a post type, and fails to find it.

This is a limitation of the permalink structure that’s built into WP. I did some research to see if there is anything out there that might be able to get around this, and I tried a few things but nothing achieved the required result.


Greg Cole

April 14, 2014 at 7:32 am

Thanks Dean. I left the calendar page at the site root and removed my page at /events. It solves the access issue and the only drawback is the breadcrumbs. Not a huge deal since the menu manager can be used to address the presentation of the main site nav structure.

Cheers!
Viewing 3 reply threads

The support post ‘Event Calendar 404 if not at root’ 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.

The original Forum description...

Status: closed

Updated by Greg Cole 10 years, 9 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server