Resolved RMS Category maps missing

[Nik]

So wrote to Bob about this but he hasn't got to me yet.

Thought I'd put it out there in case anyone can help.

I was running old RMS + XF 2.2, upgraded to release versions of XF 2.3.4 + latest RMS (2.3.1). Got my categories + item types configured. Mostly works well.

I cannot for the life of my get category and full index maps to show at the moment. It's not a G Maps issue, using same keys+APIs for showcase + cas and they all work well. No front end / back end errors to speak of.

I feel I'm missing something obvious in the config or maybe something went wrong during my upgrade path.

Maps per item (store, business etc) works fine, but category map is missing as is full map which says "No businesses have been added yet."

I'll dump my config shortly but wanted to open this up to any users to spoon feed me the 'did you check this option' faceslap I'd like to endure

I'm at the point of doing a full uninstall/reinstall, it's not the end of the world but prefer to avoid it.

 

[Bob]

Apparently I am the only person on planet earth that is able to HELP people.

Ya, it HAS to be a setting. I mean, Things don't work from some people and not other people lol I still would appreciate it if you could verify that the location_data field in the item table has data or if its empty.

Run through the RMS options again and make sure that any of the spin boxes (number boxes) are not set to 0. I had someone a few months ago that enabled the option, but didn't set the number box to tell the system how many items with location data to fetch lol With as many options as there are, its EASY to miss some.

It's not a G Maps issue,

Please do not say this. You don't know for sure. You are basing this on another addon with a similar feature that is working. That doesn't mean JACK SHIT. Google could very well be blocking the Geocoding API key for RMS HTTP requests. Tell me how you tested that? HINT, you personally can't as you'd have to write programming code within RMS so that its an RMS HTTP request. That is stuff that I do while troubleshooting sites that are having issues with Google Maps Geocoding API.

or maybe something went wrong during my upgrade path.

I highly doubt that. There are no upgrade steps involving SQL for any map related features.

I'm at the point of doing a full uninstall/reinstall, it's not the end of the world but prefer to avoid it.

There is no need to uninstall and reinstall an addon (unless you want to, but you lose all data).

If there were missing tables and or fields, you'd know it as there would be errors thrown all over the place. You can validate the schema by looking at the /src/addons/XenAddons\CAS\Install\Data\MySQL.php file which lists all tables, which all fields. Just compare to your CAS DB Schema.

 

[Nik]

Apparently I am the only person on planet earth that is able to HELP people.

You are the one man army

Ya, it HAS to be a setting. I mean, Things don't work from some people and not other people lol I still would appreciate it if you could verify that the location_data field in the item table has data or if its empty.

On to something.... Looking at what I hope it the correct table/fields I see location_data is missing.... Location addresses are there. So what populates those?

Run through the RMS options again and make sure that any of the spin boxes (number boxes) are not set to 0. I had someone a few months ago that enabled the option, but didn't set the number box to tell the system how many items with location data to fetch lol With as many options as there are, its EASY to miss some.

Doing it as we speak, permissions are all set. Attaching general options screenshots below. I've had to reduce quality as I was hitting your upload limit here.

Please do not say this. You don't know for sure. You are basing this on another addon with a similar feature that is working. That doesn't mean JACK SHIT. Google could very well be blocking the Geocoding API key for RMS HTTP requests. Tell me how you tested that? HINT, you personally can't as you'd have to write programming code within RMS so that its an RMS HTTP request. That is stuff that I do while troubleshooting sites that are having issues with Google Maps Geocoding API.

I retract the statement

I highly doubt that. There are no upgrade steps involving SQL for any map related features.


There is no need to uninstall and reinstall an addon (unless you want to, but you lose all data).

If there were missing tables and or fields, you'd know it as there would be errors thrown all over the place. You can validate the schema by looking at the /src/addons/XenAddons\CAS\Install\Data\MySQL.php file which lists all tables, which all fields. Just compare to your CAS DB Schema.

Agreed, long shot, I'd have seen lots of errors along the way.

General options page for RMS (I've blanked out my GMaps keys):

 

[Nik]

Unrelated but possibly related - playing around with CAS I'm seeing a somewhat similar but not quite same issue...

This is inconsistent in my opinion, check video clip:
https://www.awesomescreenshot.com/video/35770047?key=6b26bc1c93b09ab69bdf4883909a35ae

Category maps work but... clicking full map on the category map that shows entries should not be telling me there are no entries?!?

 

[Mouth]

I see location_data is missing.... Location addresses are there. So what populates those?

/admin.php?options/groups/xaRms/ and ensure your Geocoding API key is correct and working. Embed and Javascript use the same key, but Geocoding is different. I cannot remember why, but I had issues using the same key for all 3. Maybe a search here will find the discussion/reason?

/admin.php?tools/rebuild and action the 'RMS: Rebuild item location data' function. Then check the DB table/column again for populated data?

 

[Mouth]

Apparently I am the only person on planet earth that is able to HELP people.

Too quick for me

 

[Nik]

/admin.php?options/groups/xaRms/ and ensure your Geocoding API key is correct and working. Embed and Javascript use the same key, but Geocoding is different. I cannot remember why, but I had issues using the same key for all 3. Maybe a search here will find the discussion/reason?

/admin.php?tools/rebuild and action the 'RMS: Rebuild item location data' function. Then check the DB table/column again for populated data?

Good suggestions @Mouth. Geocoding I suspect is the problem.

EDIT: You are 100% correct. For no apparent documented reason I have to use a different API key for Geocoding.... No API restrictions on both keys. I don't understand Not in the manual. I tried it manually and it works with both.

 

[Mouth]

Great, you've resolved.

Just taking a look, appears Google API restrictions was the reason I had to seperate them?

 

[Bob]

Good suggestions @Mouth. Geocoding I suspect is the problem.

EDIT: You are 100% correct. For no apparent documented reason I have to use a different API key for Geocoding.... No API restrictions on both keys. I don't understand Not in the manual. I tried it manually and it works with both.

This is literally the first thing that I mentioned lol It the first thing I mention to anyone that has issues with the Multi-Marker Maps features in AMS, CAS, EMS, IMS, LD, RMS, SC and Sportsbook (and dozens of client addons).

It is mentioned for every addon of mine that uses the Geocoding API. You need a separate key without restrictions placed on it (which is fine, because its not exposed publicly and only used by php behind the scenes). There is a known issue with the Geocoding API (and a couple others) that rejects API requests from certain HTTP requests. Its on their end, nothing wrong on your end.

The other two api keys (Embed API and JavaScript API) should be restricted, as those API keys are exposed publicly.

 

[Nik]

This is literally the first thing that I mentioned lol It the first thing I mention to anyone that has issues with the Multi-Marker Maps features in AMS, CAS, EMS, IMS, LD, RMS, SC and Sportsbook (and dozens of client addons).

It is mentioned for every addon of mine that uses the Geocoding API. You need a separate key without restrictions placed on it (which is fine, because its not exposed publicly and only used by php behind the scenes). There is a known issue with the Geocoding API (and a couple others) that rejects API requests from certain HTTP requests. Its on their end, nothing wrong on your end.

The other two api keys (Embed API and JavaScript API) should be restricted, as those API keys are exposed publicly.

Thanks Bob, apologies if I missed the obvious mention. Appreciate your help with RMS along the way. Weirdly CAS was working just fine with this key (perhaps I may have switched it previously and it pulled data at that point) but it's definitely some funk and doing a separate key fixed it.