Hello, I responded to your other post. Can you provide me with your website URL as I believe these two issues to be related.
Hi FSP,
I have the same issue. I have seen it listed here a few times but not with the solution. I have sent you a support ticket, but it looks like a common issue that should be resolved here I would suggest. This would save you time in the long run!
Regards!
I have installed firestorm pro real eastate plugin for my real estate site
eshopperchoice.com. It was working for listing with google map showing properly. After I resolved the listing search issue by removing 4 lines in define.php. The search problem was resolved but new problem of not showing goole Lat & Lon or Pin on the specific location appeared. I could not figure out what caused the problem. Can anyone help me? Ta
Peter hwuang
I have the same problem like billways
Can anyone help us?
Regards
Mikal
Hi Mikal,
I tried hard on the firestorm pro plugin. Before all the problem fixes out on the Forum I had to use normal posts with Featured Images plus Mappress Google Map Plugin. This seems to be working better and easier with the generic Search using keywords we enter at the time of placing the listings. It seems to be trouble free for me. However, the difference we may have using this method for listing is losing the intended features designed within RE plugins for the real estate property listing. If you like try this before we have any answer to see if you like my idea.
Cheers
Billways
I pass this on for info as I am not sure if this is the cause of the problem in the original post.
Over the last few weeks I have been trying this plugin out.
When I started the lat/long stuff worked fine, but then it stopped. I had a similar problem on an completely unrelated site I know that as of March 8 Google discontinued their V2 version of the map api. Although I now read it has been continued till September.
This plugin uses the V2 map api to geocode the address into a lat and long. For me when I modified the plugin geocode function to work as per the V3 api the geocoding bits now work again.
It is too early to say if everything else works, but I pass this on in case it helps.
Regards
DREW