Can I rename "Portfolio Items" to something my content team will relate to?

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.

Good morning!
I did leave the <?php up at the top of the functions.php file.
When I used your code, everything worked, including “Books Categories.” The problem was that I also got errors:

Notice:  permalinks in /home/tpen/jorvik.press/wp-content/themes/enfold-child/functions.php on line 24
Notice: Undefined variable: permalinks in /home/tpen/jorvik.press/wp-content/themes/enfold-child/functions.php on line 24

Warning: Cannot modify header information - headers already sent by (output started at /home/tpen/jorvik.press/wp-content/themes/enfold-child/functions.php:24) in /home/tpen/jorvik.press/wp-includes/functions.php on line 5946
Warning: Cannot modify header information - headers already sent by (output started at /home/tpen/jorvik.press/wp-content/themes/enfold-child/functions.php:24) in /home/tpen/jorvik.press/wp-admin/includes/misc.php on line 1252
Warning: Cannot modify header information - headers already sent by (output started at /home/tpen/jorvik.press/wp-content/themes/enfold-child/functions.php:24) in /home/tpen/jorvik.press/wp-admin/admin-header.php on line 9

I got that error using your code before I edited register-portfolio.php and I get it now.
I wonder if there’s another plugin creating the problem.

Thank you so much for your time. I’m learning a lot!

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 5 years ago by steed.