I believe I finally found a solution. I REPLACED this first block of code in the child theme’s function.php file with the second block of code below. I hope it helps someone.

————————–
OLD
————————–
add_filter(‘avf_builder_boxes’, ‘add_builder_to_posttype’);

function add_builder_to_posttype($metabox)
{
foreach($metabox as &$meta)
{
if($meta[‘id’] == ‘avia_builder’ || $meta[‘id’] == ‘layout’)
{
$meta[‘page’][] = ‘team’;
$meta[‘page’][] = ‘careers’;
}
}

return $metabox;
}

————————–
NEW
————————–
function avf_alb_supported_post_types_mod( array $supported_post_types )
{
$supported_post_types[] = ‘careers’;
return $supported_post_types;
}
add_filter(‘avf_alb_supported_post_types’, ‘avf_alb_supported_post_types_mod’, 10, 1);

Anyone have ideas on how to use Enfold’s child theme to handle “with_front” on Enfold’s default Portfolio post type?

Apologies. I included a temporary admin login but not the login to view the site. You will need both. Enter the login credentials to view the site (below) and then enter the admin login once the WP Admin login screen appears. Please help.

Thank you Ismael. I have the CPT UI plugin and debated creating a new Post Type. This helps. For now, I will stay with the parent theme fix while I look for a less programmatic solution or can devote time to try this in our dev environment.

Thank you for your reply Srishti. If I were to do what you did above, I believe I would see the following: 1) domain.com/blog/<individual-blog-entry> and 2) domain.com/blog/paintings/<individual-painting-entry>. I’m trying to prevent such a parent-child permalink structure between my blog and portfolio.

My previous solution regarding “with_front” ended up working. Perhaps it was a time-based or cache issue. The edits to the register-portfolio.php file finally saved. But, only on my main Enfold theme. I can’t copy the file to my Child theme and get it to save any updates. Now, I have to worry about theme updates overwriting my edits to this file.

Thank you again for your insight!

includes/admin/register-portfolio.php
I believe changing the rewrite “with_front” to “false” (lines 34 and 54) will solve all my problems. But, my changes to the file do not appear even thought WP says they saved. I tried saving the file to “includes/admin/register-portfolio.php”, but that did not work.

Line 34 ‘rewrite’ => array(‘slug’=>_x($permalinks[‘portfolio_permalink_base’],’URL slug’,’avia_framework’), ‘with_front’=>true),
Line 54 “rewrite” => array(‘slug’=>_x($permalinks[‘portfolio_entries_taxonomy_base’],’URL slug’,’avia_framework’), ‘with_front’=>true),

—————————–
c_srishti, I’m not sure what your solution was. It doesn’t matter what I add to the portfolio item base or custom structure. The portfolio base incorrectly will fall under my custom director structure (see below) which is what I do NOT want. This should not require site access. I can’t be the first person to NOT want portfolio to be within my blog directory.
—————————–

EXAMPLE:
Permalinks > Custom Structure = /blog/
Permalinks > Portfolio Items Base = portfolio

This happens (bad) = domain.com/blog/portfolio/item-in-my-portfolio
I need this = domain.com/portfolio/item
I need this = domain.com/blog/item

I have the CPT UI plugin, but portfolio is already built into Enfold. Why can’t I use it the way I need?

Added:
It looks like others had this issue in older versions on WP/Enfold. I’m not sure it was ever solved. I’m working my way through this thread. https://kriesi.at/support/topic/change-with_fronttrue-from-portfolio-entries-custom-post-type/

• This reply was modified 5 years, 11 months ago by contiorg.

Bump. Anyone? Please help!