Richard

Thank you, that would be great!

I am a premium subscribed, I have been trying to post on the website, but I keep getting this error: https://prnt.sc/ttzkyk

Can you just send the file to [email protected]?

I tried that, I copied and pasted the code from /wp-content/plugins/woocommerce/templates/myaccount/downloads.php to the file /wp-content/plugins/woo-shortcodes-kit/mytemplates/downloads.php, but it didn’t work.

Same error, it stops people from adding coupons on the cart page.

I’m having this issue as well, I’ll let you know if I come across a solution.

Oh thank goodness, @grigaswp’s solution worked for me as well. Thank you!

Noted, thanks.

For anyone else experiencing this issue, I disabled “import external media” and the cURL errors went away. I’m still working on getting my server settings setup to finish importing, it’s still getting stuck at 4%.

Update: I tried excluding users and the blog, now it’s getting stuck exporting orders at 87%.

Is this the problem you are having? I can’t select icons, and have to use the Menu Icons plugin to get them to work. It seems to be a Javascript issue.

https://prntscr.com/qgyeyo

@apprimit While you’re working on it please take a look at Elementor’s checkboxes too. They should be a box instead of a single vertical line: https://prnt.sc/pzva1c

Thanks @whiteshadow I do have the pro version, so I’ll do that.

@apprimit That worked for me, thanks! I think there may be other icons that were not working, keep an eye out for those. I’ll let you know if I come across any myself.

Thanks!

Here is an example of it not working while the checkbox has been ticked (selected): https://prnt.sc/px4roq

I can’t share the URL because it is live, and I am currently using GeneratePress until the icon issue gets resolved.

I don’t remember which site was experiencing this problem, and I’m not sure where to input the code shared above. If it comes up again I can open another ticket if that’s better.

• This reply was modified 5 years, 4 months ago by Richard.

Looks like this was fixed in the most recent update.

I should have checked the FAQ, thank you!