I’ve gone through all the options and you can see the closest I’ve come to in the link.

Can anyone please help me? Do I need to look for some other plugin?

Any help will be greatly appreciated!

I try this (the second) but it doesn’t recognize the activation and removes caps anyway.

My function:

function add_theme_caps()
{
	global $pagenow;
	$role = get_role('administrator');
	
	if ('themes.php' == $pagenow && isset($_GET['activated'])) { // Test if theme is active
		$caps = array(
			'activate_plugins',
		);
		foreach ($caps as $cap) {
			$role->add_cap($cap);
		}
	} else {
		$caps = array(
			'activate_plugins',
		);
		foreach ($caps as $cap) {
			$role->remove_cap($cap);
		}
	}
}
add_action('load-themes.php', 'add_theme_caps');

Can you help me?
Thanks.

PS: my original issue is about adding cpt custom caps

I am currently using Caldera Forms to build a RSVP page for a wedding. I want the answer form to be only accessible to people invited to the wedding hence I’ve added a condition to the “next page” button which shows only if first/last names are matching and in my list.

However some invitees have names with accents and if I put for example “Aurélien” instead of “Aurelien” the “next page” button will not activated.

Same issue with capital letters, however I’ve switched the condition from “is” to “contains” and now it works.

Do you have any idea on how to solve it? My database is case and accents insensitive.

I’m trying to let the editor user role to have access to all CRM entries.
I have managed to show the plugin page, but not the entries.

Here is what i have for now.

function crm_entries_add_access_to_editor() {

     $role = get_role( 'editor' );
     $role->add_cap( 'vx_crmperks_view_plugins', true );

}
add_action('init','crm_entries_add_access_to_editor', 11);

Thank you!

How can I resolve this?

Thanks!

They try to turn off the caps lock, thinking it’s happening on their end, but can’t because it’s the form itself doing it. So I’m getting submissions with jacked up lower case/upper case craziness and they are complaining about it.

Can you please tell me how to correct this, or better yet, can the plugin developers just issue an update that takes care of it? I see that I’m not the only one here who has this problem.

Thanks