Felipe Santos

Hi @basler,

Yes, you’re correct! SCF is a new plugin, created as a fork (new version) of the ACF free plugin.

Most of the code is still the same. The main things removed were ads with new security fixes were also added.

If you are using ACF Pro that would be a different situation as their Pro features don’t have an equivalent (at least for now) for SCF — in this case, I would recommend you to keep track of the changelog for new updates.

Hi @nikulv,

Repeater and Gallery are not options yet in SCF. My recommendation is to follow the changelog to have new updates.

Considering that Secure Custom Fields is a new plugin and that the initial code was based on the free ACF plugin, it will surely keep improving with time in terms of feature parity.

Hi there,

No, ACF functions names haven’t changed to ensure maximum compatibility with the new SCF plugin.

Maybe these will change in the future, but in a way that offer as much compatibility as possible.

Hi there,

Do you have any bugs that you could report?

It all seems to be working as expected from my end.

Hi there,

I understand that it is especially challenging to determine the next steps for the ACF Pro version compared to SCF right now, with so many things happening.

Secure Custom Fields is a new plugin. I’m confident that new features and improvements will be added soon.

I personally recommend waiting for new announcements as the version here is the free version, and I know you currently depend on ACF Pro features and don’t have many options.

I believe new options and alternatives will be available in the following weeks as we have more users focusing on this.

Hi there,

Could you please provide as much details as possible of the issue you faced?

I would love to investigate this, so it won’t apply to other users.

Hi there,

I understand that your client had issues during the update. Could you please provide more details of what happened? I would love to investigate so other users don’t face the same problems.

While the plugin was not hijacked, it was necessary to start building SCF as a new plugin as a security measure.

Hi there,

Thank you for sharing your feedback. I’m sure this was not a good experience for you!

I would really appreciate if you could provide more details on what exactly broke and how you fixed it, so we can improve this for all 2M+ sites using Secure Custom Fields.

Can you share logs, screenshots, or really anything that might help?

Hi @wilcoboode,

It really shouldn’t impact these options, as that part of the code is basically the same for now.

Could you please try downloading version 6.3.6.1 (which was available before the move to SCF) and check if that fixes the issue?

I would appreciate in case you could share a before/after screenshot, so we can investigate the issue — you can do that on https://snipboard.io/.

Hi there,

The team kept the class name and most of the structure exactly to keep as much compatibility for former ACF users, so should be all good.

You can always use a staging/testing site to confirm before any changes, but I’m confident it would work as expected.

@markob17 all those things weren’t supposed to happen.

Can you please create a topic whenever this happens to you again? This way, the team can take a look at this for you. ??

Hi there,

Thank you so much for your feedback — and I agree that being simple is more of a feature, not a problem.

I would also highly recommend checking Twenty Twenty-Four in case you like it: https://www.ads-software.com/themes/twentytwentyfour/

Hi there,

Can you please reach out to Woo support to check this further for you?

https://www.ads-software.com/support/plugin/woocommerce/

That’s really odd. Have you flushed your object cache (usually an option on your hosting)?

WYSIWYG should be a must.

Deeply agree. It generally shows as expected from my end, so I’m thinking it might be something related to the environment.

Fantastic, @madtownlems!

I added to my to-do list here to just have some additional tests and I’ll share here as soon as I publish it.