DeoThemes

I’ve sent you email regarding this issue.
Cheers.

Looks like this support is useless. This error with empty object is breaking Elementor edit mode as well. Maybe you try to check if the object is exist before trying to access property from it.
Any update on this?

For your reference, it’s coming from your plugin CSS – https://c2n.me/489xh4O
The issue happens when I add the interest groups for the first time with all values unchecked. I’ve noticed that once I’ve checked at least one checkbox, they all wrapped in label tag and look different.

• This reply was modified 4 years, 9 months ago by DeoThemes.
• This reply was modified 4 years, 9 months ago by DeoThemes.

I’m using latest version. I’ve just added new form to test my interest groups, and that’s how it looked.
Cheers.

Hi,
I’m really sorry for the late reply. I didn’t receive any notification on my email.
Yes, you can change the default footer and customize copyright info, widgets, colors etc.

Regards.

That’s a website of our client and looks like she’s using CDN. I can send you admin credentials if needed. I don’t know how to fix this issue. Is this hosting related?

Thanks.

Hi,

I have similar issue, the fonts are trying to load from different address.
Check this screenshot:
https://c2n.me/47DIOcD

I’ve tried to delete the fonts folder and clear transients but it’s not helping.
Website URL – https://hippiegenes.com/

How to solve this issue?
Thanks.

• This reply was modified 4 years, 10 months ago by DeoThemes.

I actually have a bit different issue. My client is using CDN, so the address is:
https://secureservercdn.net/104.238.71.109/p7s.013.myftpupload.com/wp-content/fonts

But Kirki trying to load it from the main domain, which is https://hippiegenes.com/

So I got this error in console – Access to font at ‘https://secureservercdn.net/104.238.71.109/p7s.013.myftpupload.com/wp-content/fonts/raleway/1Ptrg8zYS_SKggPNwPIsWqZPBtqczVs.woff’ from origin ‘https://hippiegenes.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

How to solve it?

So I’m not alone then. I also got the same error today.

Yes, our client’s website is on a cheap sharing hosting. I just googled that Instagram is limited to 200 calls per hour. So that could probably be the issue.

I couldn’t find where exactly should I place nginx.conf file.
But I’ve tested it on my new hosting (Bluehost) and it seems working now.
Thanks and Happy Holidays.