Final Note for future readers:

The solution @Guenni007 provided above (adding code to enfold-child > functions.php achieves the goal (as of Enfold 4.6.3.1).
The error messages I got were caused by a custom post type plugin (Toolset Types).
In the end, I have reverted everything back to the defaults and will be using another custom post type solution to keep my team’s workflow close to what they have already learned.

• This reply was modified 4 years, 11 months ago by steed.

UPDATE
Here’s what I did that (mostly) worked:

1. Went to Settings > Permalinks and changed the Portfolio ‘custom bases’ to “titles” and “titles-entries”
2. In the enfold-child theme, I opened functions.php and pasted in this:<br />

   
   // portfolio args
   add_action( 'after_setup_theme', 'init_reg_portfolio' );
   function init_reg_portfolio() {
   	add_filter('avf_portfolio_cpt_args', 'avf_portfolio_cpt_args_mod', 50, 1);
   }
   
   function avf_portfolio_cpt_args_mod($args) {
   	$labels = array(
   		'name' => _x('Book Titles', 'post type general name','avia_framework'),
   		'singular_name' => _x('Title Entry', 'post type singular name','avia_framework'),
   		'add_new' => _x('Add New', 'portfolio','avia_framework'),
   		'add_new_item' => __('Add New Title','avia_framework'),
   		'edit_item' => __('Edit Title Entry','avia_framework'),
   		'new_item' => __('New Title Entry','avia_framework'),
   		'view_item' => __('View Title Entry','avia_framework'),
   		'search_items' => __('Search Title Entries','avia_framework'),
   		'not_found' =>  __('No Title Entries found','avia_framework'),
   		'not_found_in_trash' => __('No Title Entries found in Trash','avia_framework'),
   		'parent_item_colon' => ''
   	);
   
   	$args['labels'] = $labels;
   	return $args;
   }
   //END
   

3. In wp-content > themes > enfold > includes > admin I opened register-portfolio.php and made the $labels = array code block look like this:

   $labels = array(
   		'name' => _x('Book Titles', 'post type general name','avia_framework'),
   		'singular_name' => _x('Title Entry', 'post type singular name','avia_framework'),
   		'add_new' => _x('Add New', 'portfolio','avia_framework'),
   		'add_new_item' => __('Add New Title','avia_framework'),
   		'edit_item' => __('Edit Title Entry','avia_framework'),
   		'new_item' => __('New Title Entry','avia_framework'),
   		'view_item' => __('View Title Entry','avia_framework'),
   		'search_items' => __('Search Title Entries','avia_framework'),
   		'not_found' =>  __('No Title Entries found','avia_framework'),
   		'not_found_in_trash' => __('No Title Entries found in Trash','avia_framework'),
   		'parent_item_colon' => ''
   	);
   

[ NOTE: I’m not sure this is important, but I made the names match what I did in functions.php above ]

I said “mostly works” above because “Portfolio Categories” is still visible in the options.

I tried to follow what Ismael and mikeraymarketer were doing here to fix the same issue, but when I did it, I got errors so I walked it back.

Hey Guenni007,

Thank you! That first link looks exactly like what I’m asking about.
The child-theme URL goes to the same page as the link above it — was that intentional?

Thanks again for the help! I’ll follow that path.

Hi Mike,

Thank you for your deep investigation of this problem. I’ll start disabling plugins now, and see what happens.
In the meantime, I want to report a possibly related issue: how mobile views of multiple column layouts are showing up.
Scroll down this page in a mobile screen perspective: http://3tophd.org
Specifically you’ll see that the columns under “Concordia University + Faubion School” don’t stack (they used to) and same with the columns in the Color Section below that.

Thanks again.
Tom

Hi Rikard.

(( face palm ))

Tom

Thanks Jordan!

Hey, do I still need the custom CSS I added above or is that superfluous?

Tom

Hi Victoria,

First: Thank you!

Second, it’s working how I want it to. I just don’t know why.

I am aware of the page ID and that’s the source of my confusion. When I look in the QuickCSS for some special instructions for page-id-772, there are none.

When I compare the settings on the masonry gallery between this page and the other ones, it appears that my settings are identical.

I appreciate your help previously. We don’t really need to dig into this any further. Thank you.

Update: I figured it out, but now have another related question.

Here’s what worked:

.page-id-2344, .av-masonry-container,.page-id-2351 .av-masonry-container {
    pointer-events: none;
}

Is that the best way to write that?

New question: I have other pages that use masonry gallery in a similar way, but I didn’t need to do that trick with the QuickCSS to turn off pointer events.

I’m confused. Help me Obi-Kriesi, you’re my only hope.

Thanks for the clarification Andy. I’m a little surprised that Basillis and you went to the freelance developer solution so quickly.

Did something change over there that you guys do that rather than offer guidance or point to online resources known to you that it might take me a long time to find?

While I HOPED the initial reply would be something like “yes you can do it, just do x instead of y, and check out this other forum page for more,” what I feared you’d say is “the way your site is structured, this approach won’t work. We suggest you contact our developers and get a bid.”

Instead, sales pitch: “Yes it’s possible, but you need to pay us to do it for you.”

I use WordPress and Enfold as a way to get amazing websites on very tight budgets. I own two Enfold licenses myself and have bought 5 more through the clients whose websites I’ve built.

I know I’m venting, it’s not aimed at anyone personally. It comes from being surprised and disappointed in what seems to be a change in the Kreisi Way I’ve appreciated for the last 5 years.

Boo. That’s what I thought. I found a topic from 2 years ago where you said pretty much the same thing.

Feature request, here I come. :-)

Ah! I knew it was in there somewhere. I’ll try that. Thank you, Josue.