The SCF plugin itself changed to ACF

  • Resolved AniaFrania

    (@aniafrania)


    1 year, 4 months ago

    I’m working on a new website on localhost. I had the SCF plugin installed on this new website. Today I go to this website and the plugin has changed to ACF version 6.3.11?! How did the plug change itself? What is this about? Could someone explain this to me? Just 2 days ago I was working on SCF and today I have ACF?

Viewing 3 replies - 1 through 3 (of 3 total)
  • alx359

    (@alx359)

    1 year, 4 months ago

    Probably you had the other “SCF Lite” plugin installed that lately was returned back to the ACF devs, and it got rebranded back to ACF in their last update, when they took back control.

    https://ww.wp.xz.cn/plugins/advanced-custom-fields/

    This SCF plugin here is a fork of “ACF Pro”.

    It was confusing for some time, as both plugins were named “SCF”. That one here is the only SCF plugin now.

    Thread Starter AniaFrania

    (@aniafrania)

    1 year, 4 months ago

    Thank you for your reply. Is SCF no longer in existence and I am working on ACF? Is this stable and will not affect my site? I wouldn’t want to work hard and then have something break down.

    alx359

    (@alx359)

    1 year, 4 months ago

    The “SCF Lite” plugin doesn’t exist as such anymore, as it was rebranded back to ACF (Free), their original developers. It’s still the same codebase and functionality, so you shouldn’t have any issues whatsoever with the ACF plugin, as it has 2+ million deployments and a long story in the WP ecosystem.

    The remaining SCF plugin (a forked version of ACF Pro) is still in beta, and not recommended for live sites.

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

The topic ‘The SCF plugin itself changed to ACF’ is closed to new replies.

Tags