Felipe Santos

Hi @jimbyrnescotland,

If you can’t see this version somehow, my recommendation would be for you to follow this path:

1. Download the 6.3.6.3 version of Secure Custom Fields
2. Go to your site WP Admin > Plugins > Add New
3. Upload the zip folks there

This should give you the option to update SCF manually.

Hi there,

For now, all contributors are focused on setting up the basic structure for the new SCF plugin.

The team is already working on adding the plugin to a GitHub repository to allow the whole community to get involved.

If you would like to help, you can join the?channel secure-custom-fields on Slack?and get involved from there.

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.

Hi there,

I’m not sure what the near-future goal for Secure Custom Fields will be, as the initial focus of this newly created plugin was to fix the security issues available on ACF while offering a superior experience for WordPress users.

I believe a natural next step is to bring feature parity with their ACF Pro version to give more freedom to users, so my recommendation would be to wait a bit and keep following the changelog, but that is something you need to consider based on your current context and possibilities.

Hi there,

Can you please share the full error message?

Also, do you remember if you had other changes right before updating SCF?

It is unlikely that your issue is related to SCF as it is a new plugin/fork, and (for now) most of the code is still the same, so I would appreciate as much context as possible.

Hi there,

Doing something like that right now would likely bring several compatibility issues, and I’m not sure what exactly it would achieve.

As SCF is a new plugin, I believe the long-term goal is to have it as scf or secure-custom-fields as the text domain, but not something that will be done until it is possible technically without bringing issues.

Hi there,

Secure Custom Fields (SCF) is a tool to create the fields without using custom code, but you still need use the plugin functions to show the field data on these posts.

For instance, you can use the_field('publication_release_date'); on a loop with all the posts for this CPT, and it will show this data.

Alternatively, you can also use a shortcode on your content such as [acf field=”{$publication_release_date}”] to show this dynamically.

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?