> For the complete documentation index, see [llms.txt](https://phpface.gitbook.io/streamtube/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://phpface.gitbook.io/streamtube/acf-advanced-custom-fields.md).
# ACF - Advanced Custom Fields
Advanced Custom Fields (ACF) is one of the most popular plugins for adding custom fields to User, Post, and Taxonomy objects in WordPress. It is highly recommended.
1. [Enable Frontend Post Type Editing](#post-type)
2. [Enable Non-ACF Post Type Editing](#non-acf-post-type)
3. [Custom Post Type Capabilities](#post-type-capabilities)
4. [Enable Frontend Taxonomy Editing](#taxonomy)
5. [Enable Non-ACF Taxonomy Editing](#non-acf-taxonomy)
6. [Custom Taxonomy Capabilities](#taxonomy-capabilities)
7. [Custom Capabilities: Use Case & Caution](#capabilities-caution)
8. [Field Group Location](#user-fields)
9. [Custom User Fields](#user-fields)
***
#### Download:
{% hint style="success" %}
The Advanced Custom Fields plugin is available for free at:
* Official ACF Website
* WordPress Plugin Repository
{% endhint %}
***
#### Documentation
***
#### Enable Frontend Post Type Editing:
In the Edit Post Type screen, enable the "**Show UI Frontend**" option.
Enable "Show UI Frontend" option.
***
#### Enable Non-ACF Post Type Editing
For any custom public post types that are not created using ACF, navigate to: **Customize > Theme Options > Public Post Types**, here, you can enable them as needed.
***
#### Custom Post Type Capabilities
ACF and most Custom Post Type UI plugins do not support configuring the "capability\_type" parameter, which is essential for role-based content management. By default, "capability\_type" is set to "post", meaning it inherits the same permissions as the default WordPress post type.
**Example:**
*If you register a "Photo" custom post type and want only specific user roles to manage it (e.g., Add, Edit, or Delete actions), you must explicitly define the "capability\_type" parameter. Otherwise, it will default to "post", allowing any regular author to manage the Photo post type, which may not be the intended behavior.*
We have chosen not to automatically alter this behavior, even though it could be done easily. Instead, we leave it up to you to configure the settings as needed, giving you more flexibility rather than imposing restrictions.
If you want to assign custom capabilities to your post type instead of inheriting the default post capabilities, you can add the following code snippet to the end of **wp-content/themes/streamtube-child/functions.php** or your own plugin and change the $my\_post\_types value as desired.
{% embed url="" %}
After adding the code, you may not see the custom post type editing screens in the frontend Dashboard, even if you are logged in as an admin. This happens because the necessary capabilities have not been assigned yet.
You will need to assign capabilities as outlined here [Content Capabilities](/streamtube/content-capabilities.md)
***
#### Enable Frontend Taxonomy Editing:
Using the same approach as with post types, you can also enable the "Show UI Frontend" option for custom taxonomies.
***
#### Enable Non-ACF Taxonomy Editing
For any custom public taxonomies that are not created using ACF, add the following code snippet to the end of **wp-content/themes/streamtube-child/functions.php** or your own plugin and change the taxonomy name as desired.
{% embed url="" %}
***
For additional Custom Post Types and Custom Taxonomies capabilities, please refer to [Content Capabilities](/streamtube/content-capabilities.md)
***
#### Custom Taxonomy Capabilities
It follows the same structure and context as "[Custom Post Type Capabilities](#post-type-capabilities)."
{% embed url="" %}
***
#### Custom Capabilities: Use Case & Caution
Modifying the capabilities of custom post types or taxonomies created by other plugins may lead to permission issues. Many plugin authors may not account for custom capabilities and instead rely on general capabilities for access control.
For example, some plugins might use:
```php
if( current_user_can( 'edit_categories' ) ){
// Do something
}
```
Or
```php
if( current_user_can( 'edit_posts' ) ){
// Do something
}
```
This approach is incorrect for checking permissions on custom taxonomies or post types, as each would have its own **capability\_type**, as explained earlier.
Instead, you should retrieve the post type or taxonomy object and check its specific capabilities accordingly.
{% embed url="" %}
***
#### Field Group Location
The UI Location option allows you to set where the Field Group appears. Select "Both" to display it in both the backend and the frontend dashboard.
Field Group
{% hint style="success" %}
Looking for adding custom meta boxes programmatically? [Add Custom Meta Boxes](/streamtube/for-developers/add-custom-meta-boxes.md)
{% endhint %}
***
#### Custom User Fields
Any custom user fields created for the backend form will also be automatically applied to the frontend dashboard.
Please note that the **Dashboard > Account > General** Profile page will automatically display any custom fields you create for the User object. However, custom meta values will not be reflected on the public user profile page by default. To display them, you will need to use ACF functions or the **get\_user\_meta()** function programmatically.
*
*
Sample code snippets
{% embed url="" %}
Display a specific ACF custom field on the user profile content area
{% endembed %}
{% embed url="" %}
Display all Advanced Custom Fields (ACF) on the user profile content area
{% endembed %}
