Marc Fritz

Thank you for your prompt reply! I changed the WP Setting and it works! Thank you!

The Limit squared distance area is set to 40 miles. My problem is that I search for listing within 5 miles “near me” and the results show listings 6 – 40 miles away.

Thank you Kor!! I really appreciate your help!!

Ok, I understand.

Could you at least please help me to fix the bubble, so that it displays correctly?

The picture doesn’t display correctly and I can’t scroll down enough to see the bottom of the text in the description box. Please see the screenshot below. That’s as far as I can scroll down, but there’s more text below it.
I appreciate your help!
Thank you in advance!

Best regards,

Marc

Hi Kor,

Thank you for your help, I really appreciate it!! It looks much better already!!
Is there any way to make the bubble a bigger? It would be great if the description box was larger. It’s kind of hard for the customer to scroll, esp. on the mobile device. It would also be great, if one could see the whole image and if the corners of the bubble would be round (15px radius).

Thank you!

Best regards,

Marc

Hi,

Go the “directions” to work. Thanks!
I would also like to move the “Partner Offer” section before the “Description” section on the detailed listing page and change the color of the font awesome icons to #c19e47. I tried using the “CCS class” tab in the “Place Settings,” but it didn’t change it.

It would be amazing if you could help me with that as well!

Thank you in advance!

Best regards,

Marc

Would also work if customer can just click on address to get redirected

Hi Stiofan,

Thank you for your reply! Based on Alex’s reply I thought that your developers were checking into the issue.
I passed on your comments and the above provided link to the Avada support team.
Here’s their reply:

“I believe it is quite a difficult task for us to change our FA setup immediately.

There are a few points that we would like to mention here

1) The KB item shared by plugin support has the following mentioned -> http://prntscr.com/lnxstf. If they check source after disabling the plugin and its add-ons, we are using standard approach. Here is a screenshot for reference -> http://prntscr.com/lnxu3k, but the source is still being modified here.

2) Plugin author also provides another plugin to fix this issue -> https://github.com/AyeCode/fix-font-awesome. So maybe they can help you implement this

3) Additionally, I see they themselves claim compatibility with Avada -> http://prntscr.com/lnxuxr. So it should not be hard for them to add a check for Avada in their code.

4) On top of that, we enqueue our file with “font-awesome” handle -> http://prntscr.com/lnxx5e. While they do with “fontawesome-css” handle. This is with respect to the response here, https://prnt.sc/lny38n.”

I would greatly appreciate any help to resolve the issue!

Thanks,

Marc