mike8040

Great. How did you do this…

$order->get_number();?!

EDIT: For those looking for an answer like me.
replace $order->get_id() with $order_id = $order->get_order_number()
and if you like {{order_id}} with {{order_number}}
file: niwoopr-email.php

I like people opening threads and closing them without giving an answer to their solution.

• This reply was modified 3 years, 8 months ago by mike8040.
• This reply was modified 3 years, 8 months ago by mike8040.

Was the latest plugin version on that date I posted the issue. I couldn’t fix it and removed the plugin

@rik1234
Hi, sorry for the late reply. I managed to fix this by just adding in the custom CSS for the theme:

.dropdown-menu .sub-menu
{min-width:50px;}

For some reason either the theme or the plugin did set some ridiculous min-width value and the outcome was that the flag wasn’t shown.

This are the menu settings itself
https://ibb.co/Bw46B7Q

Well, thanks for clarifying. But somewhat in my case your solution won’t work or I don’t get it. I already got the latest update and did re-save the plugin settings. The order confirmation emails sent to me and customers gets the post ID sent. There is no way to change the email already sent. So now there are several discrepancies with the order tab and customer invoices. The order IDs are correct in the order tab but the emails sent to customers are sending the post ID. How to fix that?

I posted this on the main “not working” thread that was marked as resolved:

Unfortunately I have to say its not resolved. I tested the latest update on the staging site and it was ok. Updated the live page with the latest plugin version. After an hour I get an order coming in. The email order number is 4407 where the order itself should be and is 4006 in the wordpress back end. SO the customer gets a wrong Order ID and any support with emails goes bonkers. Is there quick fix other than disabling the plugin?

Just to note… Thanks a lot for the quick fix and the free plugin and support even if the issue is not resolved yet. This is something that gets forgotten quite fast when something doesn*t work. Its a free plugin. So thanks for the support!

• This reply was modified 3 years, 8 months ago by mike8040.

Unfortunately I have to say its not resolved. I tested the latest update on the staging site and it was ok. Updated the live page with the latest plugin version. After an hour I get an order coming in. The email order number is 4407 where the order itself should be and is 4006 in the wordpress back end. SO the customer gets a wrong Order ID and any support with emails goes bonkers. Is there quick fix other than disabling the plugin?

Just today I also was looking for exactly the same info about this. There is a bug with the lng switcher. I have it set to just show the flag. The drop box however is completely empty. It should show the flag and its there in the code but not showing up. This is not a caching issue. Do you got the same behavior?

https://www.dropbox.com/s/s660uoh1qnhs27i/lng_switcher_bug.jpg?dl=0

//EDIT: If “show lng names” is activated it shows at least the name but the flag is still missing.

//EDIT-2: Ok it seems the size for the flag icons get defined through html inline code for whatever reason. If I disable the size properties in the dev tools the flag shows up.
https://www.dropbox.com/s/t4s3kt81qkyn78m/lng_switcher_bug-2.jpg?dl=0
After more digging is seems this css line is the culprit:
.lang-item a img {padding: 0 10px;}
Setting this to padding 0 resolves the invisible flag without disabling the inline CSS properties.

@rik1234 For your issue. I think as a workaround you could have the “show lng names” active and set the active lng name to “display:none” with custom CSS. Just a workaround

• This reply was modified 3 years, 8 months ago by mike8040.
• This reply was modified 3 years, 8 months ago by mike8040.
• This reply was modified 3 years, 8 months ago by mike8040.
• This reply was modified 3 years, 8 months ago by mike8040.
• This reply was modified 3 years, 8 months ago by mike8040.

Thanks for your quick and detailed response! Sounds great even though I have to work this out and make me familiar with the setting. Amazing features!

Thanks for your response. With saying that I already checked for double/correct tags I meant I used the Tag Manager by Google to make sure there are the appropriate tags set. Everything is alright according to troubleshooting docs but still it doesn’t work.
I must say that I find GA and Google Ads interface awful and having a hard time to get used to it. Maybe I missed a setting there. E-commerce and Enhanced EC is active. Is there anything else I need to set and missed that? Also I generated a conversion ID in Google Ads for buys with a custom code in the child function for the Thank-you page. (In this try I used a custom thank you page which is actually the ultimate goal I try to achieve. Saying this right now I try the default TY page to work properly first) The GTAG code after a test buy is correct having all the product information and prices but still no tacking of this in GA or GAds.

I must say I’m confused by the general logic with GAds and GA. Both are connected with another and both track the conversion and checkout behavior but with a different setup. Intuitively I would keep all the analytics in GA and not let those two platforms do the same stuff.

• This reply was modified 3 years, 9 months ago by mike8040.

Hey there,
this a never ending story for me. Since 4 weeks I try to get the conversion to work. I tried several different approaches with no success. Even with default Woo thank you page. Right now I use Woo GA integration for general analytics which work. Actually I gave up on this but today I tried this custom Thank you plugin and found the you solution.
The thank you page does have the conversion code in the source code. So everything is set up as described but I still get not conversion data. Any idea what could be wrong? I’m stunned that this is so buggy. This is how the TY source code looks like in the head tag:

<!– WooCommerce Google Analytics Integration –>
<script type=’text/javascript’>
var gaProperty = ‘UA-19XXXXXXX-1’;
var disableStr = ‘ga-disable-‘ + gaProperty;
if ( document.cookie.indexOf( disableStr + ‘=true’ ) > -1 ) {
window[disableStr] = true;
}
function gaOptout() {
document.cookie = disableStr + ‘=true; expires=Thu, 31 Dec 2099 23:59:59 UTC; path=/’;
window[disableStr] = true;
}
</script>
<script type=’text/javascript’>(function(i,s,o,g,r,a,m){i[‘GoogleAnalyticsObject’]=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,’script’, ‘//www.google-analytics.com/analytics.js’,’ga’);ga( ‘create’, ‘UA-196XXXXX-1’, ‘auto’ );(window.gaDevIds=window.gaDevIds||[]).push(‘dOGY3NW’);ga( ‘require’, ‘displayfeatures’ );ga( ‘require’, ‘linkid’ );ga( ‘set’, ‘anonymizeIp’, true );
ga( ‘set’, ‘dimension1’, ‘no’ );
ga( ‘require’, ‘ec’ );</script>
<script type=’text/javascript’>
var ga_orders = [];
try {
ga_orders = localStorage.getItem( ‘ga_orders’ );
ga_orders = ga_orders ? JSON.parse( ga_orders ) : [];
} catch {}
if ( -1 === ga_orders.indexOf( ‘3104’ ) ) {
ga( ‘set’, ‘&cu’, ‘EUR’ );ga( ‘ec:addProduct’, {‘id’: ‘002340’,’name’: ‘Product’,’category’: ‘Shoes’,’price’: ’10’,’quantity’: ‘1’});ga( ‘ec:setAction’, ‘purchase’, {
‘id’: ‘3104’,
‘affiliation’: ‘Brand’,
‘revenue’: ‘14.50’,
‘tax’: ‘0’,
‘shipping’: ‘4.5’
} );
try {
ga_orders.push( ‘3104’ );
localStorage.setItem( ‘ga_orders’, JSON.stringify( ga_orders ) );
} catch {}
}</script>
<!– /WooCommerce Google Analytics Integration –>

• This reply was modified 3 years, 9 months ago by mike8040.
• This reply was modified 3 years, 9 months ago by mike8040.

Unfortunately nothing changed and the issues persist. I deactivated this plugin as it lets shop appear completely dilettante. Awful and too bad as I would like to try its features.

This are random issues with no consistence which makes it hard to fix. Also it appears for BACS payments now which is totally stupid as I can’t see any way how an order already made with an offline payment could be abandonment afterwards
Paypal:
https://www.dropbox.com/s/i1rzj5g42jrt4yk/random_issue_1.JPG?dl=0
Bacs:
https://www.dropbox.com/s/nauimdag1vfjk0x/random_issue_2.JPG?dl=0
Translated: “Transfer awaiting Order status changed from pending payment to pending.”

Maybe the Woo shop logic is not intuitive to me. To manage shipment and packaging that takes place at that day for those orders I set them from “on-hold” to “processing” to have better overview in the order list. It may be the issue for the plugin. BUT I have excluded emails for “processing” so… Emails were active for “pending” and “failed” still those issues and lots of confused customers.

• This reply was modified 3 years, 9 months ago by mike8040.
• This reply was modified 3 years, 9 months ago by mike8040.

Thanks for your response. To bad that one can’t add customers manually since the BACS users sometimes don’t par or forget to pay. With excluding “on hold” those BACS users won’t get added to the list. It would be great to have a definition for those manual payment gateways.” After x days send the customer an email if he is using XY gateway”

I already set the exclude order status and there was still emails sent. But since yesterday it seems to be ok. Didn’t get any complains and the test account is also free from mails. Maybe a random bug

Sorry couldn’t edit it anymore. But I think this is relevant. I tested the issue on the staging site with Authorize enabled, with a PP sandbox account and followed the same steps. There was no issue and the cart abandonment plugin wasn’t triggered.
https://www.dropbox.com/s/lihd3jvz7jhv6sl/paypal_issue2.JPG?dl=0

Still not sure where to go from here.

• This reply was modified 3 years, 9 months ago by mike8040.

Any help? I’m worried that payments don’t work if I change the settings to sale.

Well it was the white screen of death and fatal error was the description for the error that was pushed to the user. I test it on the staging site when I find time. And yes the latest wordpress release.