API Token Issues

Those are all of the possible token validation messages being seen at once. The correct one is supposed to be displayed using javascript. The fact that you are seeing them all at once would mean that one of a couple things are happening.

1. The JS assets for this plugin are not loading successfully for some reason
2. There is a JS error on the page preventing further script execution

If you are familiar with your browsers developer tools/console you may be able to help diagnose which of the two issues is happening. Are there any errors in the console? Either JS errors, or perhaps a 404 when it tries to load the JS asset?

• This reply was modified 1 year, 7 months ago by Matt Keys.

Checked in Chrome and Firefox

No errors, no 404s in console.

Disabled all plugins except for ACF and ACF FA. Used default theme. Same issue.

Tested on local. Fresh install. Only installed ACF Pro and ACF FA. Before doing anything besides activating the plugins, I get that same message:

Token Validation: Please add your API token above. Save settings to validate token. Token successfully validated. Could not validate token. Please verify the token has been correctly entered.

Thanks for those tests. Can you tell me if these two plugins are installed normally through the WordPress plugin manager, or are they bundled with a theme?

FYI i’ve been able to reproduce your issue, I’m looking into it.,

Awesome, thank you for working on the issue!

NP. It looks like in ACF the admin menu is now called “ACF” instead of “Custom Fields” seems innocent enough but that slug is used in this plugin when determining if we are on the correct admin page to enqueue our scripts:

$acf_menu_slug = sanitize_title( __( 'Custom Fields', 'acf' ) );
if ( $acf_menu_slug . '_page_fontawesome-settings' != $hook ) {
	return;
}

I’ll probably need to check for the old and the new page slugs for a while to cover people who haven’t updated.

• This reply was modified 1 year, 7 months ago by Matt Keys.

@starrymom can you check out v4.0.5 of this plugin just released and see if it resolves the issue you were seeing?

Yes, that fixed it. Thank you, I appreciate it!

Wonderful, thanks for reporting the issue.