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 Ignore front base in permalink structure | Event Espresso - Staging Server
I need to use a constant base in all my blog posts permalinks (/blog/) but changing this via the Settings > Permalinks also affects the permalinks used by Event Espresso. My understanding is that, when registering the custom post type, the parameter ‘with_front’ must be set to false in the rewrite arguments so that the permalinks for this new CPT do not use the constant base.
Besides EE, I use other CPTs and these are not affected by the permalink base, as I’ve set the with_front parameter to false when registering them.
My question is, where can I change this parameter in the plugin? If I change it manually, will these changes be overwritten when upgrading the EE version? Would you consider adding this parameter by default in future versions? or at least a way to change it from the Admin panel…
It turns out that you don’t change this in the plugin because there is a filter in place that lets you override the defaults. Here’s something you can add to a custom snippet plugin that will keep the slug as events (which you can also change) and change the WP default from true to false for ‘with_front’:
The support post ‘Ignore front base in permalink structure’ 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.