Uploaded the updated real ACF 6.3.9 instead

Replies: 0

I watched the original WPE and WP debacle develop for some days and then got more personally impacted by this ACF SCF development with the “proposed” switch to SCF.

I never auto-update anything, as I prefer to wait some days to see if anything else happens, as in corrections for new issues, and do backups first. So, I had the option to decide which way to go here.

What happened here clearly falls in the “this is not something you do and is thus not acceptable” category.

There is no need for justifications of “point 18, point 17”, “what constitutes a fork”, etc. That is artificial precision that misses the entire bigger picture.

What is happening here is stupid, unnecessary, risky, and legally costly.

Accordingly, there is no positive “stewardship” in the equation, which I thought was always a core goal.

Stability, trust, and predictability are priority #1 unless you want to destroy a thriving ecosystem.

So, I hope the adults in the room can grab the steering wheel soon, roll back this SCF takeover, and solve whatever issue there may be with WPE.

In the meantime, I decided to stick with the ACF (free plugin) route and updated to 6.3.9 from their site instead.

این خبر را در ایران وب سازان مرجع وب و فناوری دنبال کنید

مشاهده پاسخ های این مطلب
———————————————
این مطلب از سایت انجمن وردپرس گردآوری شده است و کلیه حقوق مطلق به انجمن وردپرس می باشد در صورت مغایرت و یا بروز مشکل اطلاع دهید تا حذف گردد

منبع: انجمن وردپرس