Still shows as ACF, even if SCF

Hi there,

That’s a good point.

but the administration still shows ACF.

This changed and should show SCF now! It is still improving to remove any reference of ACF.

at least the slug should be changed too

For the slug specifically, there are some current technical limitations that wouldn’t allow the plugin to be updated (even with the security fixes) if we changed the slug.

Maybe this will be possible in the future, but not an option right now.

@foosantos Thanks for your feedback… On a fresh installation, there are still a lot of ACF references, esp. in help texts.

But also the link to the documentation links to the original documentation… very confusing…

I don’t like how everything has worked out, still see this as a chance too.

But WP.org can’t make such a rushed move with all this “talk” and promises and then deliver such a mess. I’m a professional and can handle this, but average users …

at least the slug should be changed too

For the slug specifically, there are some current technical limitations that wouldn’t allow the plugin to be updated (even with the security fixes) if we changed the slug.

What you actually mean is that by changing the slug (which is default for forking software) you could not hi-jack the existing users of the original free ACF plugin and would have started with a user-base of 0, like all real forks do.

• This reply was modified 1 month ago by Pieter Bos.

I’m generally fine with not changing the slug and getting downloads and reviews… But the only reason should be an official – from both sides – planned handover (and not takeover).

But in this special case, there are other reasons too:

• Avoid confusion!
• The chance: as good as ACF is, there are quite some technical debts in it too and a “new” plugin can be a chance to clean this up. (this still can happen)

As much as I like ACF, and we are using it in every project (mostly the pro version)… if there is a core plugin with a similar feature set, we will just switch.

—

And there were other cases in the past, where a very good single-feature plugin got bought and transformed to some bloatware… We also have some free plugins, tried Freemium in the past. For me, there are reasons for this happening.
First and foremost: no direct git support (or better Github) support for the repo. They always speak of “community”, but thanks to missing git it makes very hard to contribute at all. And then, as a developer… you don’t get anything using the wp.org repo… never ever someone donated for my plugins… To be honest: Automattic is earning money, riding the GPL-train as hell, but don’t give plugin developers a way to at least cover costs…

Uninstall ACF, then reinstall SCF from WP Plugins. When you activate SCF, you should see the changes in the menu.

I’m not sure about the code, but the visual references to ACF should be removed.