Jason Ryan

@rzepsen –

Thanks, I got it sorted out, was something on my end.

Hello @rzepsen –

The issue seems to be with the fact that we are not using the default WooCommerce template for the My Account page. We are using the Impreza theme, however, it still outputs all of the other default WooCommerce account details so something in the way you are hooking into it is not translating to the theme.

Is there a Shortcode that could be placed to output the Refund Request form? Otherwise I will have to share your plugin with the theme developers to see if something else could be done.

Thanks

• This reply was modified 9 months, 3 weeks ago by Jason Ryan.

Issue resolved in 1.9.13.2

Thank you.

@wpserveur

Hopefully that isn’t the recommended fix for this? We host and maintain over 200 websites for clients that use this plugin. Simply can’t spend the time going through each one’s database to add these transients.

Neither of those transients exist for me, even after dismissing the nag message and refreshing and checking the DB.

Clearing cache after dismissing the nag message, then reloading the page, the message comes back every single time.

Yeah, can confirm. The message comes back after a couple of page reloads. The same message as @nicolas-leclerc.

Experiencing the same issue here, cannot get rid of the nag message.

@kylephillips –

Can confirm, Wordfence scan came back clean. Thank you very much for taking care of this, much appreciated!

@kylephillips –

Hey, there he is! Glad to hear that you are well!

Not sure if this helps, got this via Wordfence’s website:

https://www.cve.org/CVERecord?id=CVE-2023-49195

@gillesgagnon

I have posted the issue on Github which he should see.

https://github.com/kylephillips/wp-nested-pages/issues/351

Unfortunately, his plugins are not his full time gig, he may be busy with that or there is a lot of illness going around, could be laid up with that? Who knows. Dude is super talented and builds great stuff, if there was some type of “pro” version I would certainly support the cause, especially with this plugin – which should be part of core anyway.

@claudiaiw

Thanks for the recommendation but that is nothing like this plugin whereas Nested Pages replaced the clunky default WordPress page and post list entirely and makes it more manageable. Plus your recommendation doesn’t work with custom post types.

Thanks, but I’ll hold out for an update here.

Experiencing the same issue (Premium). On a couple sites.

We wound up writing a custom plugin that modifies the “stock_quantity” field’s data type to “number” in the WooCommerce REST API schema and got it working again.

Should seriously consider making this part of core.

Thanks

Hello –

I just updated to the latest version and it looks like this didn’t make it into version 1.1.0. Thought you were including this?

Thanks