w4yp01nt

@mediaticus Thanks for having a look!

The other thing you mentioned, is a problem I have taken a stab at solving as well, since I need to do this when accounts are created, as you pointed out. Due to timing issues (Related to when the children meta is actually written), the only solution I could hack together was this one.

Please let me know if you see a better way to do this as well ??

I came up with this, would it be a stable approach to simply check these fields?

@dazzerr Hey,

Did you ever find a solution to this? I have the exact same issue, in that I need to update user meta after account creation, but before the purchase is completed.

@vilerozes

Glad I could help!

Hey @vilerozes,

Unfortunately, the issue here becomes, that the markup is actually generated by core WooCommerce JS files.

It dawned on me, that I was having an issue with this, because the notifications that I was talking about in my OP, are only the ones that are generated after AJAX requests – and these are generated via JS (of course).

If I wanted to alter the markup of these, I would then have to change core files, which is something we should avoid.

I have now ended up implementing a workaround, where I hide all default notifications with CSS, and instead hook into the jQuery AJAX update event, so that I can copy the content of these notifications, and display them in my own.

Not an ideal solution – but a workable one for the time being.

The problem appears to be this pattern, in frontend/cart.js, where a new message is prepended to the main wrapper. I guess WooCommerce hasn’t really been designed with the alteration of these in mind.

• This reply was modified 3 years, 10 months ago by w4yp01nt.

Hello @gabrielfuentes,

Thank you – I managed to make progress with this – someone on Slack helped me dive into it!

Awesome!

Thank you, Frank – you enjoy your Sunday too!

Oh wow, found it! Amazing ??