Secure Custom Fields plugin

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Javier Casares

    (@javiercasares)

    1 year, 5 months ago

    You need to download and install the official maintained ACF plugin from their website.

    To fix it, if you were using Advanced Custom Fields, it’s better to have the official version from their website and upload manually. Thereafter, the message will disappear.

    Thread Starter eyed11

    (@eyed11)

    1 year, 5 months ago

    Thank you for your answer.

    If I want to use Secure Custom Fields instead of Advanced Custom Fields, will I still be warned?

    Plugin Author Javier Casares

    (@javiercasares)

    1 year, 5 months ago

    Yes.

    Plugin Author Javier Casares

    (@javiercasares)

    1 year, 5 months ago

    As extra information for futures references.

    There is no official way (WordPress function) to list the plugins / themes, but to detect the slug and know if it’s the local repository or an external one. Using the same slug for SCF (from ACF) creates an incompatibility.

    Usually, when that happens, we (in general, the security community) decided to use the WordPress Plugins / Themes repository as the main one, but, when there are external plugins / themes with the same slug and more relevant, we go that way.

    In this case, we (WPVulnerability) are going to maintain the versions for the Advanced Custom Fields, as is the maintained version of the plugin.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Secure Custom Fields plugin’ is closed to new replies.