izaakbeer

Thanks team Webtoffee. The filters work as expected. For the less-experienced people here, use the plugin called ‘Code Snippets’ (or leverage another method) to apply the hooks.

The code snippet is as follows, feel free to copy-paste it:

<?php
// Function in which you set the translation or updated text
function mf_replacebogotext($mf_bogogiftedtext){
  // define your text
  $mf_bogogiftedtext = 'This is where you enter your customized bogo or giveaway message.';

  // return your newly defined text
  return $mf_bogogiftedtext;
}

// Filter for cart page
add_filter('wt_sc_alter_giveaway_cart_lineitem_text', 'mf_replacebogotext');
// Filter for product page
add_filter('wt_sc_alter_free_product_added_message', 'mf_replacebogotext');


// Note: Right now, the text will be the same for cart and product because the function is re-used in both filters. If you want the texts to be different, define a seperate hook (copy paste) and update the add_filter
// izaakbeer.nl
?>

• This reply was modified 1 year, 5 months ago by izaakbeer. Reason: Code example updated

Dear Webtoffee,

I have send you the report as requested.
I’ll keep the others up-to-date of any progress here.

Thanks!

Update:

A lot more functionalities seem to have broken with the recent WP, Woo and WT Smart Coupon update. For example, e-mail restrictions are completely ignored.

If I restrict a coupon to a specific e-mail (lets say [email protected]), ALL other users can still APPLY and REDEEM the coupon during checkout. It’s as if the condition does not exist. Even if i order as a guest in an incognito window, I can apply any coupons I wish…

Very, very frustrating to say the least. Especially as I have no clue where this is coming from.

Note: I am not even sure if WT Smart Coupons is causing this bug. It might be an incompatibility, of course (although it was working fine before the update, and I do not have plugins that address the same functionality of WooCommerce).

This felt like the best place to share the report.

You’re welcome.

Do you have an instruction for how I can provide you the correct logs? I’d be happy to send them over.

Regards,

Beer

@rogierlankhorst Thank you for the swift reply (or bedankt!).

This definitely helps. I agree with ioiodesign though, it’s quite the wrong (or at least, doubtful) move to change styles so significantly between updates. Absolutely understand where you are coming from with changing requirements, incorporating more features, etcetera. But (yeah, there it is, haha) the style is not even in the slightest bit similar to what it was. To me, it honestly looks like the styles aren’t working/it’s broken.

Anyway, looks like I have some custom CSS work to do here.

Thanks a lot for the clarification and keep it up with the amazing plugin!

Cheers, Beer

• This reply was modified 2 years, 10 months ago by izaakbeer. Reason: rephrased first sentence

I now see my site doesn’t allow hotlinking, hence the screenshots don’t show.

Here (click here) is an imgur album that shows the images, where:
1. What the banner looked like before updating
2. Error example 1
3. Error example 2

Thank you ??

I’m such a noob…

RESOLVED
Brave browser shields block various end points of Google Tag Manager. Basically, you can’t track whoever uses Brave (including me). Its working just fine!

— CLOSED

Hmm… After resubmitting the changes (reclicking save), the script appears to show up (both in head and footer) – albeit without the <!– Google Tag Manager –> comments

However, when trying the “Preview” in Google Tag Manager (to test the connection and if events fire), GTag does not connect to the site. Not sure why it doesn’t connect? (I am not logged in and all cookies have been accepted)

• This reply was modified 3 years, 2 months ago by izaakbeer.

@yoast @semrush any new updates on this?

I am quite positive this is not a false negative but actually a real error. Google Search Console is now giving me the exact same error (A value for the item.name or name field is required for a nested ListItem.) –> “Either “name” or “item.name” should be specified”.

Yoast address this ASAP please. Keep us updated. Thanks!