user9876789

Hello, it’s still saying all my products don’t have a description. I couldn’t see a way to change the sync in bulk but I did a few products and didn’t work either. The code I’ve used is

function custom_gla_product_description($description, $product) {

$custom_text = get_field(‘text’, $product->get_id());

return !empty($custom_text) ? $custom_text : $description;

}

add_filter(‘woocommerce_gla_product_attribute_value_description’, ‘custom_gla_product_description’, 10, 2);

Is there any other advice you can offer?

Hello, I’ve added a code snippet now to change what field the description uses. I tested this locally and it was returning the correct data. I have put the changes live, but it still lists out each of my products as having a missing description field. How can I resync this so it can pick up the new values? In my Issue to resolve section each of my products show with the issue as ‘This value should not be blank [description]’

Hello, we are developers. Do you have any documentation on what actions / filters you have that we can hook into?

Thanks for this – looks like that plugin may do the job. Can I ask if I were to purchase and install this – would the existing order of taxonomy terms I had set in the free plugin carry over into this? We have a taxonomy (product_cat) with 5000 terms that have been reordered and I don’t want to have to redo that reordering.

Do you have any further ideas on what I can try here to get the 2FA working?

Thanks for your reply – in regards to Are there any additional plugins like membership plugins or custom login forms/pages/modals that could be changing the login flow from the ones supported on your other sites?

The staging and live site have the same plugins and functionality and they’re on the same hosting. The sites did have Really Simple Security installed but I removed that as it wasn’t needed. If the staging site didn’t work I’d be inclined to think it was a plugin, theme or hosting issue but like I say they’re the same.

I also tried making a new login (mainly because I was using the admin one and once I’d added the 2fa I couldn’t get back in without the client logging in to deactivate the 2FA) with the user role of Contributor and this does the same.

Live and dev sites both match time wise and say
Server Time: 2024-11-15 08:58:04 UTC (2024-11-15 08:58:04 Europe/London)
Browser Time:?Fri, 15 Nov 2024 08:58:04 GMT (Fri Nov 15 2024 08:58:04 GMT+0000 (Greenwich Mean Time))
Corrected Time (NTP): 2024-11-15 08:58:04 UTC (2024-11-15 08:58:04 Europe/London)

We use 1Password to store our logins – and use the in built feature in there to scan QR code which hooks up the 2FA. We don’t use Authenticator for these logins as we use one company login for several developers to share.

Great thank you, please do let me know when this is available as we will buy the pro version once that’s in place

Please could someone come back to me on this one?

Great thank you!

This change has happened as a direct result of moving off of Legacy Stripe, prior to that it had Stripe in the title. We were able to change it on the legacy version – it’s frustrating to be told to move off a system that was working fine to a system that has more restrictions and less customisation.

I am a developer myself so I am comfortable with code changes, but the more we try move off of legacy stripe the more and more issues like this we seem to be encountering. I shouldn’t need to make a code change for something that before was just changeable in the admin

Also, I am using woocommerce shortcodes, not blocks.

The client has come back to say they are getting errors signing up again. I was able to replicate this time. I have added recaptcha v3. However I now have two new issues.

I ticked the box to say don’t show the badge. However, the badge is showing on all pages. Also, the cookies for Recaptcha are loading on all pages not just single product so when I run Lighthouse my Best Practices score is reduced to 78 due to 2 cookies now in use _GRECAPTCHA and NID

Great thank you!

Great thanks, that works!

Thanks I have changed the option to the REST API one. I have informed the client and will wait to hear from them, their customers are pretty good at letting them know they’re getting errors so should know if its worked within a few days / a week