Adam Walter

Thank you!

This plugin is for ACF color picker fields and nothing else. Are you not seeing your colors in your ACF color pickers? Are your HEX colors formatted correctly following the examples in the plugin’s settings page?

Simple! Make a subfield in the ACF group for the background color. Use that field’s value (it will be a HEX color) in your template code and drop it into a style attribute in your div.

Great idea! I’ve added a admin_notice_enable hook. There’s an example of use on the plugin’s main page.

This is a different error than the topic of this post. Make sure you have colors saved in the plugin’s settings page and then see if the error persists. If it does, please start a new topic. Thank you!

This isn’t related to the topic of this post, but I can say that would require rebuilding how this plugin’s custom colors are defined and stored. They are currently a simple comma-separated list of HEX values so there are no names or slugs. The theme palette colors are merely added to the HEX list.

If you want the full array of theme color data, I would just use WordPress’s native function for that for the time being.

get_theme_support('editor-color-palette');

Just pushed a fix for this. Sorry for the delay!

This was a good idea so I have added a acfrcpo_get_color_options function in the latest version. Thank you!

• This reply was modified 3 years, 11 months ago by Adam Walter.

Great idea! I just pushed a new version with the option to include the current theme’s colors if it uses the editor-color-palette support feature.

Thanks for pointing this out. Just pushed a fix!

Since the developer has no incentive to fix this and the plugin hasn’t been touched for 6 months, I have added the following to my theme’s functions.php to hide the nag:

/**
 * Hides incessant review nag from Members plugin.
 */
add_action('admin_head', function() {
    echo '<style>#members_review_notice { display: none; }</style>';
});

+1 on this. No matter what option I click, it returns eventually. Our sites have multiple environments (dev, stage, etc) so this problem is multiplied even more.

Thanks for working on this! I just tested version 4.1 on a basic install with the Twenty Nineteen theme and minimal plugins, but I’m still getting a 404 on the child post. The slug is removed, but only the parent posts return successfully. Permalink cache flushed and everything. Any ideas?

Excellent! Love your plugin. Thanks for all the hard work.

My original report was on MAMP running PHP 7.1.6. I moved that same WordPress site to our production server running 7.0.22 and everything appears to work fine. It may not be an issue after all, but I’m not setup anymore locally to test again on 7.1.6.