mrmartinimo

Hi @alex-caravaca-ponce

I completely understand your thoughts, but I think you are wrong.

It is common practice for WordPress plugins to hide certain functions behind a paywall. This is also the case with plugins such as WooCommerce from Automattic aka WordPress.com. You can find this good or bad.

The ‘essential tools’ you mentioned that ACF offers for developers are already implemented in WordPress-Core itself. ACF only offers a nice and standardised interface for clicking together the custom fields. I don’t know how often you work with ACF, but the free version already offers everything you need to create complex custom fields. The Pro features are rarely relevant.

I am also a fan of open source, but in my view WordPress.com’s behaviour is damaging the open source community. As for the legality of taking over the plugin by www.ads-software.com, you may be right. But not everything that is legal is also right. www.ads-software.com took over ACF’s repository without any agreement and thus also the user base. This is completely unusual and I wouldn’t call it a fork. To me, the whole thing seemed more like a heist that was controlled by WordPress.com. I would have no objections to a classic fork by creating a separate repository or implementing the ACF features in WP-Core.

It’s no secret that WordPress.com and WPEng*nes are fierce competitors. WordPress.com has taken advantage of www.ads-software.com’s power to hurt WPEng*nes. I can’t understand who is turning a blind eye to this. All this under the guise of open source. It’s disgraceful.

• This reply was modified 1 month ago by mrmartinimo. Reason: Detail added

What restrictive practices on the part of WP Engine with ACF are we talking about here? What advantage does SCF have over ACF in the current version?

I find it questionable how ACF is becoming a pawn between Atomattic and WP Engines. This harms the WordPress and open-source community.

Thank you!

That’s not true, take a look at the changelog.

The same problem has also occurred with me.

The problem occurs in the file ‘./wp-content/plugins/ninja-forms/ninja-forms.php’ in line 354:

require_once Ninja_Forms()::$dir . 'blocks/ninja-forms-blocks.php';

has to be:

require_once Ninja_Forms::$dir . 'blocks/ninja-forms-blocks.php';

wpbodymovin.animations[index_of_animation].instance.playSegments([30,0],true)