switchdan
Forum Replies Created
-
I’m actually getting some unexpected behaviour now as a result of this latest change.
I think the change makes sense in general – the admin area should be translated to the language you have selected in the admin bar as opposed to the language of the post you’re editing. But we’ve noticed that this also affects things like links added through the WYSIWYG and post object/relationship fields in ACF.
The WYSIWYG only seems to let me select posts created in the site’s Primary language, and ACF post object/relationship fields only return posts from the language selected in the admin bar – making it difficult to edit translated content.
If I disable the new setting, ACF returns posts from all languages which equally difficult to work with.
Historically these fields only returned posts from the same language as the one being edited (which I would think is the preferred behavior).
I’ve reverted to V3.3.3 for the time being but would you please be able to let me know if this is intended behaviour going forwards as we may need to implement our own solution in our theme if so.
Hi Loic,
Thanks for the reply – in our case it would be for some custom user roles we have set up.
I suppose it would be ideal if there was a custom Cloudinary capability we could use to restrict who should and shouldn’t have access to that tab (similar to the “upload_files” capability for example). We could then assign it to the default roles as well as our custom ones.
Thanks!