Alexander

Hi @fesupportteam,

Thanks for your reply. The difference of course being that custom post type slugs can be prefixed in a way that is completely hidden to the visitors of a website, and usually don’t need to be maintained by contributors (but only by an admin/developer). With this situation, neither is the case: these slugs are very much public, and can arbitrarily collide with posts created by contributors. The solution “just use different name” feels shaky at best.

My 2 cents.

Kind regards,

Alexander

Alright. I relayed the issue via email. Hope to hear from you soon!

Ah, @fesupportteam. In that case, the first snippet I mentioned actually does do the trick. I feel a bit silly now. Thanks for your help!

Hi @fesupportteam, thank you for your quick reply. I tried that, but to no avail. I must be missing something, because even if I just do this, nothing happens:

add_filter('wpc_filter_post_meta_term_name', 'wpc_acf_labels_instead_of_values', 10, 2);
function wpc_acf_labels_instead_of_values($term_name, $meta_key)
{
    return 'test';
}

Note that my filter is placed in a template through a shortcode. Maybe that’s relevant somehow?

The official WordPress page (now) also says Reason: Guideline Violation.

I would advice against purchasing this plugin.

We are now running 0.8.1, and the problem persists.

Hi, any news on this issue? We run into exactly the same errors on the production environment of a website (the plugin works fine in a Docker container that we use for development).