squarecandy
Forum Replies Created
-
Forum: Plugins
In reply to: [Advanced Custom Fields: Font Awesome Field] Results could not be loadedYes – it’s weird – I’m also seeing it working on my staging server right now with the same PHP version, but not on my local machine…
Forum: Plugins
In reply to: [Advanced Custom Fields: Font Awesome Field] Results could not be loadedHi – I am also experiencing this issue and I dove a little deeper into the root cause. It looks like it is only a problem for the 4.x version. 5.x version populates fine.
Short term solution – for other users who find this before it is solved:
Copy and paste the value ofACFFA_icon_datain the wp_options table from a backup or other site that has valid data for 4.x – here is mine in case it is useful:
https://gist.github.com/petertwise/e2ef15bea3bfa044e8b8ae528a3b31bfLong term – for the developer:
/assets/inc/class-ACFFA-Loader-4.php– the regex on line 206 does not seem to work with PHP 7.4. I took a bit of time to try and fix it but I could not come up with a solution. Anyways – this is definitely where the problem is coming from – that regex just returns empty arrays instead of parsing out the slugs from the css file.Suggested easy fix:
since the 4.x branch of fontawesome is EOL maybe thefind_iconsfunction could just return a hard coded list of the 4.7.0 icons?- This reply was modified 5 years, 6 months ago by squarecandy.
Forum: Plugins
In reply to: [XML Sitemap Generator for Google] WordPress 5.5 sitemap featureIt may not result in negative consequences for “discoverability” but it could have negative consequences for people who have spent time crafting how the output of their sitemap works. Examples:
- You have hidden specific pages like form thank you pages or a page with a survey intended to only be accessed via a direct link. The default wp-sitemap.xml could cause these pages to become indexed.
- You want an entire custom post type not to be indexed.
- You have carefully set the priority levels of different posts and post types according to your needs
Forum: Plugins
In reply to: [XML Sitemap Generator for Google] WordPress 5.5 sitemap featureI would advocate for adding
add_filter( 'wp_sitemaps_enabled', '__return_false' );to this plugin so we can be sure if we turn on Google XML Sitemaps that there’s no conflict with the core feature.+1 for this
Yes, thanks @ande1352 !!!
Forum: Plugins
In reply to: [Disable Blog] Disabling Writing Settings Panel is a problemAwesome – thank you. Happy to help test it before you push the new version if you would like… My contact info is at https://squarecandy.net
Forum: Plugins
In reply to: [Simple Taxonomy Ordering] Conflict with ACF ProOr if you want to disable the ACF javascript on ALL taxonomy pages:
function squarecandy_yikes_acf_taxonomy_sort_hotfix($post_id) { $screen = get_current_screen(); if ( 'edit-tags' == $screen->base ) { wp_deregister_script('acf-input'); } } add_action('current_screen', 'squarecandy_yikes_acf_taxonomy_sort_hotfix', 99);Forum: Plugins
In reply to: [Simple Taxonomy Ordering] Conflict with ACF ProHere is my heavy-handed temporary solution to match the heavy-handedness of ACF’s colspan=100. This is fine to apply to any taxonomy for which you don’t have any ACF usage on the taxonomy edit screen. My custom taxonomy is called
series. You should replace your taxonomy ID as needed below.function squarecandy_yikes_acf_taxonomy_sort_hotfix($post_id) { $screen = get_current_screen(); if ( 'edit-series' == $screen->id && 'series' == $screen->taxonomy ) { wp_deregister_script('acf-input'); } } add_action('current_screen', 'squarecandy_yikes_acf_taxonomy_sort_hotfix', 99);This is still not really a good final resolution, but will allow you to use the YIKES reordering plugin and ACF successfully at the same time for now.
Forum: Reviews
In reply to: [CAPTCHA 4WP - Antispam CAPTCHA solution for WordPress] Yo dah Man Shamim !!+100!!!
This is saving me from having to transition dozens of sites to a completely different plugin.
Leave a 3 star review and then ask for help… not the best way to do it, my friend.
Forum: Plugins
In reply to: [Contact Form 7] reCATCHA V3@dukeo – don’t worry, you don’t need to update your own privacy policy to notify users. Google has placed a convenient and beautiful badge in the corner of all of your web pages now with a link to their terms!
Forum: Plugins
In reply to: [Contact Form 7] reCATCHA V3@locascioa – Your article that you linked to is really comprehensive and awesome!
Thanks for the tip that we can just use
https://ww.wp.xz.cn/plugins/advanced-nocaptcha-recaptcha/
and disable the CAPTCHA feature provided by CF7 if we want to keep v2.I know you’re now advocating for people to switch to v3 with 5.1.1, but it’s good to have options.
Forum: Plugins
In reply to: [Contact Form 7] reCATCHA V3But new v3 keys must be created on https://www.google.com/recaptcha/admin for every domain and then installed in the plugin settings, right? That’s a ton of work. Discontinuing support existing v2 keys instantly on upgrade to the version that uses v3 seems like a bad approach. A separate setting for v3 and support for both would be so much better, allowing users to keep the plugin updated but make the switch to v3 when they have time and inclination to do so.
“We agree that the badge is obstrusive, but that can be removed by adding some additional styling.”
It’s against Google’s TOS to hide the badge with CSS. You can do it, but it’s technically illegal. The badge that’s inline with the form is not the prettiest, but at least it is a relatively positioned element that only shows on the form pages.
“We can even trigger a SPAM block by using autofill on all the form fields.”
Lots of real users use autofill for their contact info.
Forum: Plugins
In reply to: [Contact Form 7] Add reCaptcha v2 support@claitonlord – obviously always backup first, because you never know… but, no you shouldn’t loose any forms, but you’ll need to re-enter the v2 keys if you switched to v3 keys.
I used https://ww.wp.xz.cn/plugins/wp-rollback/ to roll back the version, which worked great.