Gabor Lippert

@redzonedesigns

You’re mixing things.

• SCF is (or started) as a fork – you can deny it, that’s OK, some folks deny climate catastrophe, some other deny the existence of forks and/or the legality of forking open-source software.
• “Automattic forcibly took over the existing slug, user base, and review history of a successful and actively maintained plugin and replaced it so the original one doesn’t exist in the plugin directory at all” => not forcibly, they have the right to do so; it’s their repo, these are their servers. As for how this affect the user base, I also have some concerns here, but practically, all it means is that users intending to keep the WPEngine-owned product will need to download updates manually from the ACF site. This increases their upload time from 1 min to about 2. Could be worse, my opinion is. ??

As for successful and actively maintained – well, we’ll see how the community-developed SCF can keep up with the company-developed ACF. I’m pretty sure Automattic will have aspecial focus and team for SCF – if ACF evolves too fast compared to SCF, users will simply ignore this latter and keep (or go back to) the WPEngine product.

As for the review history – there’s no stealing here either. The product users install/update is an update of the last version af the free ACF code base. What changed is the plugin name, and as a result, the ownership.

Personally I welcome this change because I’m a hater of WPEngine’s strategy of purchasing successful WP plugins and make them more and more into their platform of advartisement in the wp-admin. And with this step, Matt elegantly prevented the scenario where WPEngine would turn the plugin into a client-only product, something that, I’m pretty sure, already is on their roadmap.

The original ACF was not a WPE product, this latter purchased it a few years ago. They lie when they claim it’s their plugin since 2011. It’s not.

And the code base, at least that of the free version, is now owned again by the community.

Everything in its right place.

This looks like a troll post paid by WPEngine. ??

It actually is. The original plugin has been forked, which is totally cool, since we’re talking about open-source software here.

The rremoval of ACF from the repo is also totally cool, nothing illegitimate or illegal here – and obviously a consequence of the legal war between WP and WPEngine.

There’s no problem with your opinion either, of course. But giving a one-star review to the fork of one of the awesomest WP plugins ever made, simply because you don’t like the change of ownership – now this is definitely unethical behavior.

Noone destroyed anything. And actually, this is a stellar day for the WP community. Not so much for trolls paid by WPEngine.

The original plugin has been forked. It’s open-source, everyone has the right to fork it. This is not stealing.

And the removal of ACF from the repo was also a legitimate step.

Your “NOT THE REAL ACF ANYMORE!” claim is very partially true – and your review score is definitely biased, and your personal problem with the changes of ownership doesn’t have anything to do with the quality of this plugin.

SCF is the good old ACF, it’s simply that it’s not a WPE-owned product anymore, and it is and will be more secure compared to its predecessor.

What REALLY happened is that the free version has been FORKED, meaning the code is the same (if the new dev team hasn’t been updated it since the forking), and, additionally, the WPEngine-owned Advanced Field Plugin has been removed from the repo.

That’s all that happened. And you can be sure, this is the beginning of a beautiful friendship:

• WordPress does need a custom fields solution
• SCF (formerly known as ACF), obviously, needs WordPress
• Now that the free version is not in the hands of an unethical hosting company, the WP developer community, contributors, hobbyists, we all can work to integrate features that currently are available with the premium ACF plugin only.

The only downside of this change is that WP users intending to keep using the free ACF version instead of the also-free SCF plugin will need to manually download updates from the ACF site – this increases their update process from about 1 minute to 2.

Hi @devmich ,

Thanks for your follow-up – please find below the list of plugins currently active on the site:

Advanced Google reCAPTCHA
All in One SEO
Code Snippets
Coming Soon Page, Maintenance Mode, Landing Pages & WordPress Website Builder by SeedProd
Contact Form 7
Contact Form 7 Google Analytics Integration
Contact Form 7 Style
Cookie Notice & Compliance for GDPR / CCPA
Disable WooCommerce Reviews
Download Plugins and Themes from Dashboard
Easy Booking for WooCommerce
Easy Booking PRO
Email Log
Email Verification for WooCommerce
Email Verification for WooCommerce Pro
Flexible Checkout Fields
GP Premium
Image Hover Effects - WPBakery Addon Free Version
Kanzu Little Longtails
Minimum Order Amount for Woocommerce
MonsterInsights - Ads Addon
MonsterInsights - EU Compliance
MonsterInsights Pro
PDF Invoices & Packing Slips for WooCommerce
Pixel Manager for WooCommerce
PixelYourSite
ReCaptcha v2 for Contact Form 7
Simple History
SSL Insecure Content Fixer
Store Toolkit for WooCommerce
String Locator
WooCommerce
WooCommerce First Atlantic Commerce Payment Gateway
WooCommerce Legacy REST API
WooCommerce SSL Seal - WP Fix It
Wordfence Security
WP File Manager
WP Mail Logging
WP Mail SMTP Pro
WP Menu Cart
WPBakery Page Builder
WPFactory Helper
WPForms Lite
YITH WooCommerce Terms & Conditions Popup
Yoast SEO

Not sure if this helps – based on the browser console, the issue comes directly from MonsterInsights plugin files.

Hey, @arnaudbroes,

Thanks for the swift follow-up – do you know when will the updated release be avilable?

Thanks ??

Hi James,

Thanks for your swift reply, and for the detailed explanation.

I’ll use that last url to report the issue.

Hey Georgian,

?? Huge thanks for the update.

And I can confirm Konrad’s report: the Settings > Email Customizer tab is completely empty now (both the User Emails and the Administrator Emails tabs). ??

Hi Konrad,

Thanks for taking a look into this, and for the info regarding what’s causing the issue. Not to mention the safe-guard logic – great idea and a very nice addition!!

I also opened a topic in the Profile Builder plugin support forum as well (with a reference to this very topic included), because bugs are to be fixed.
Hopefully, they’ll update the code accordingly on their end.

Cheers ??

• This reply was modified 1 year ago by Gabor Lippert.
• This reply was modified 1 year ago by Gabor Lippert.
• This reply was modified 1 year ago by Yui.

Hi Alexandru,

Thanks for your swift reply – ?? sounds perfect, I look forward to the next version release.

??

Placing the following snippet:

if( !isset($post) ){
    return;
}

… into acf-extended\includes\module-post.php (above the $module = acfe_get_module_by_item($post->ID); line, originally at line 43) seems fixing the issue, but it would be nice to have an official patch.

@bcworkz Oh thanks for your feedback on this.

The workaround you recommend is completely OK/workable – I guess I just needed this feedback about that the described behaviour is indeed something reproducable, by anyone, and with mulitple themes.

I’m marking this as resolved – ?? thanks again for taking a look into this.

Thanks for your swift reply, Sébastien – that’s all I needed to know.

• This reply was modified 1 year, 9 months ago by Gabor Lippert.

@bobsled , @diondesigns , @cuppa500

The following code (to be added to functions.php) fixes the totally-annoying and totally-counterintuitive auto-suggestion:

add_filter( 'site_status_should_suggest_persistent_object_cache', '__return_false' );

@here https://developer.www.ads-software.com/reference/hooks/site_status_should_suggest_persistent_object_cache/#comment-6173

This supposed to be a temporary fix, but I’m afraid we all need to be prepared this snippet will need to be manually added to all client sites for eternity… ˉ\_(ツ)_/ˉ

—

Thanks to @bandonrandon for the swift commenting…