robertzollner
Forum Replies Created
-
Same thing happens to me also, the notice does not go away.
A github bugreport was created here: https://github.com/woocommerce/woocommerce/issues/62123
Forum: Reviews
In reply to: [Advanced Custom Fields (ACF®)] (In)Secure Custom FieldsThe link to the GPLv2 repo were it was forked from is this: https://plugins.trac.ww.wp.xz.cn/browser/advanced-custom-fields/tags/6.3.6
The company that has bought ACF 2 years ago was filled suit against WP last month and they don’t have access to free services offered by WP anymore, including the plugins repo infra. In the mean time ACF has deployed their own repo and users can download ACF directly from them. It’s an ugly situation for everyone and until the legal conflict is not resolved between them probably nothing will gonna change.
Forum: Reviews
In reply to: [Advanced Custom Fields (ACF®)] Disappointed with unauthorized changes@joshgreenuk while I totally agree that the whole ACF move was awful and they should have released a different forked plugin and leave this one as is, your comments about the technical parts don’t make sense, you can’t seriously say you don’t trust the core developers of the whole wordpress codebase and woocommerce to develop this plugin to the highest standard and not push broken code, managing custom meta should have always been done by the core devs as they are the best qualified to make the right decisions and i have no doubt they will BUT as already said in the beginning this is not a technical discussion about code or skills, this take-over of the acf profile in the wp repo should have never happened, it is wrong on so many levels and it did so much damage to WP image and trust without binging any benefit to anyone involved at all.
@adrianlambertz I’m not defending anyone and I’m not affiliated with any of them, I ended up here after receiving update notifications from my clients websites and entered panic mode right away after reading the fake titles that the plugin was hijacked bcz that means something completely different eg hackers taking over websites after updating the plugin.
So after reading thar WP has taken the maintenance of the ACF plugin as SCF I was relieved in the context of “hijacking”, but that not imply that I defend or support this move from them as this shouldn’t have happened.
WP has the right to fork the code but does not have the right to use acf branding and their reputation built from years of reviews, they should have started clean and nobody is saying otherwise.
Forum: Reviews
In reply to: [Advanced Custom Fields (ACF®)] PatheticCan you post some details on what broke? and how you fixed it
Forum: Reviews
In reply to: [Advanced Custom Fields (ACF®)] Please Stop this Mess WordPressWP is cutting their ties with WPEngine, so it’s impossible for wpengine to continue to have access to the WP ecosystem, I’m sure all wpengine plugins to end up forked eventally, so that they can be maintained going forward, it’s ugly but it is what is is.
Forum: Reviews
In reply to: [Advanced Custom Fields (ACF®)] Very concerned!Looks like they announced it in the changelog section, that’s the first place to check when a update is available, second is the reviews tab :))
Did you had auto-updates enabled for ACF?
Can you tell us more about what incident the update caused?
ACF/SCF is part of wordpress core now, nothing was hijacked.
What incident has the update caused? Where you by any chance using the $_REQUEST global variable in metabox callback configured from [Edit Post Type] / Advanced Settings / Visibility / Custom Meta Box Callback? If so then that is no longer possible as it is a security issue, read more about the CVE on Wordfence
Forum: Reviews
In reply to: [Advanced Custom Fields (ACF®)] Yeah OkSo stop using WP and WooCommerce, and go use WPEnginePress or whatever inovative and trusted CMS they have created.
If you didn’t know WP and WPEngine are in conflict atm, and plugin repos have split, so this move from WP to cut ties with all code controlled by WPEngine on WP repos was inevitable, and I would bet the same will happen with all other plugins controlled by WPEngine in the coming weeks if the conflict between them is not resolved
I have tested and it is working perfect, well done!
Themes Customization:
“Header and Navigation” -> “Header” -> “Header Layout” has to be set to “Logo / Navigation / Cart” from the dropdownThe demo with the search modal using the “dialog” html tag can be seen here: https://shoptimizerdemo.commercegurus.com/?header=header-4&headercontainer=full-width-header
Their demo is using the built-in search but it can be changed from the Appearance / Customization to AWS. And the AWS shortcode will be added inside “dialog.shoptimizer-modal .shoptimizer-modal–content .site-search”