Well, the weird part was caused by my code, it seems 🙂
This is how it works: ACF is checking the manage_terms
capability.
At first I didn’t understand because manage_terms
is not listed here:
https://codex.wordpress.org/Roles_and_Capabilities
It’s also not available in the User Role Editor plugin, which I was using to assign capabilities to roles.
But manage_terms
is a special capability that is created when you use register_taxonomy()
to register a taxonomy:
https://codex.wordpress.org/Function_Reference/register_taxonomy
It is set up as a reference to another capability, in the example it is manage_categories
. But in my case I had a custom taxonomy where the manage_terms
was set to edit_users
for some reason, and that explains it all!
Actually, by trial and error I nailed it down to a combination of edit_users
and manage_network_users
. If I add those two capabilities to a user that otherwise just have the read
capability (like a subscriber) then the add term button appears and works.
I discovered that by making the user a super admin (this is a multisite) the add term button appeared. Not even ordinary administrator worked.
This is a related question (tell me if I rather should open a new issue instead):
In order to add terms to a taxonomy a user must have the correct permissions to do so. In WP for categories this would be manage_categories.
I have a logged in user with the manage_categories
capability but I still do not see the ability to add new terms from the front-end. Is there any other capability that is needed as well?
Moving acf_form_head()
before get_header()
as JustinCase suggested solved this problem for me.
I can confirm that the newer-but-still-the-same-version-number 5.6.0 solves the image problem. (Honestly, it would be less confusion if bugs where fixed with a new version rather than patched on already released versions.)
I’m seeing this issue as well, the image field in my front end form is broken after upgrading to 5.6.0.
Just a quick comment; if anyone tries the code above by @acf-support there’s a period missing before “acf-label”:
.acf-field-1234567890 > acf-label {display: none;}
should be
.acf-field-1234567890 > .acf-label {display: none;}
I’ve tried from the main site as well. Wonder if it has anything to do with WordPress being installed in a sub directory?
Anyway, as you said earlier, I should probably open a support ticket instead, I am a paying customer after all.
That would have been great, if it worked.
When I try to access that page I only see “You do not have sufficient permissions to access this page.” (and I am a super admin).
Digging into this I found this thread that had a slightly different URL:
/wp-admin/network/update-core.php?page=acf-upgrade
but the result is the same (and that is what that thread is about).
Oh, well then I’ll just bite the bullet this time, I guess. Thanks anyway for the informative answer, it’s nice to know it won’t happen too often. I’ll go ahead and mark this solved with your answer, even though it wasn’t the answer I was hoping for 🙂
Ah! I missed that part about setting the return type, that explains the code in the example. Thanks!
This is marked as solved, but there still is no built-in way to make a field non-editable, right?
Thank you Jonathan for your investigation. I was going to try your filter code, but after updating WordPress to 4.3 the problem is gone!
I tested on two installations and saw the same thing on both. After updating WordPress to 4.3 the scrolling and fixed size of multiple ACF wysiwyg editors is back.
(Before updating to WordPress I also updated ACF to 4.4.3 so it could be a combination of WP 4.3 and ACF 4.4.3, but only updating ACF did not change anything.)
I’m going to mark this answer as “This solved my question” but I’m still thankful for your previous answers.
Oh, I assumed ACF was using wp_editor()
. Maybe I was confused by the ACF WordPress WYSIWYG Field.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.