[Closed] Split: Unable to create Post type

[Author]

Posts

[tobiasH-7]

I created a Google Map API key, but for some reason it will not display on the live site.

This is the webpage where Toolset is being used - hidden link

[Mateus Getulio]

Hi again,

So, we checked the console menu for the page where the Map is being inserted, and we could find this error log:

Google Maps JavaScript API error: RefererNotAllowedMapError
<em><u>hidden link</u></em>
Your site URL to be authorized: <em><u>hidden link</u></em>

The "RefererNotAllowedMapError" error suggests that "Application restrictions" is enabled in your Google Maps API key settings with "HTTP referrers (web sites)" option: hidden link

Can you please make sure that your website's domain is added in there in a way that allows all sub-domains and paths?

You'll find some useful suggestions on troubleshooting "HTTP referrers" restriction in this thread too:
https://stackoverflow.com/questions/35288250/google-maps-javascript-api-referernotallowedmaperror

I hope this helps. Please let me know if you need any further assistance on this.

Regards,
Mateus.

[tobiasH-7]

I currently have the restriction settings off on the Google API, should I turn it on? What I am seeing is that the error log when I inspect the page is trying to pull a different API key than what I have installed on Toolset.

[Mateus Getulio]

Hello there,

Thanks for your reply.

You can add the domain to the allowed referrers using a wildcard - for instance, as the client did here: https://toolset.com/forums/topic/google-maps-doesnt-show/#post-2508215

Please give it a try and let us know how it goes. Thank you.

[tobiasH-7]

Thank you for sending that information over. I input the domain formatted as shown in the forum, hidden link but there is still no luck getting the map to populate. In the screenshot here I tried to highlight the API key from Google, but also the issue I am seeing when I inspect the page. Is the key shown in the page inspection panel suppose to match the one from Google?

[Mateus Getulio]

Hey there,

Thanks for your reply.

What about hidden link, instead of hidden link (this is, to include the https protocol, and not http)? Please check this explanation of another Google Maps user: https://stackoverflow.com/a/38577184

If you're still stuck on this, I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Our Debugging Procedures

I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.

Privacy and Security Policy

We have strict policies regarding privacy and access to your information. Please see:
https://toolset.com/privacy-policy-and-gdpr-compliance/#data-shared-with-our-support
**IMPORTANT**

- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link

Please, let me know if you need any additional details. Have a nice day.

[Mateus Getulio]

Hi there,

Thanks for providing the credentials.

It seems that the password is not correct. We receive this message when trying to login:

Error: The password you entered for the username toolset is incorrect. Lost your password?

Therefore, may I kindly ask you to review the access data? If you prefer to provide a new login info, or even a backup copy of the website, I'm enabling the private fields again for you.

Please let us know. Thank you.

[Mateus Getulio]

Hey there,

Thank you for correcting the credentials.

Upon further inspection, we have double-checked your previous messages:

What I am seeing is that the error log when I inspect the page is trying to pull a different API key than what I have installed on Toolset.

Also: https://toolset.com/forums/topic/split-unable-to-create-post-type/#post-2610173

But actually, the API key of the screenshot is the same key that was settled in the Toolset -> Settings -> Maps -> Google Map API key section. In the above reply, you asked:

Is the key shown in the page inspection panel suppose to match the one from Google?

Sorry about not answering it before, but yes, they should match, and right now it seems that they're not the same. Please review it and make sure that the key you have in the Toolset configurations is the same as in the Google Maps settings. If needed, just try to recreate the API key and check again.

If still not solved, I'll have to escalate it to our second tier team, but first we need to ensure that the keys are matching.

We're looking forward to your updates, please keep us posted. Thank you.

[tobiasH-7]

I created an entirely new API key and swapped out the information in Toolset and still no luck. Here is a screenshot to confirm. I left this API key unrestricted.

[Mateus Getulio]

Hey there,

Thanks for your cooperation.

I checked this out but so far I couldn't find a fix for it. I asked my colleagues to have a look at this issue in order to see if there's anything I'm missing.

I'll come back to you here as soon as one of my colleagues reply back to me (which it shouldn't take long).

Best,
Mateus.

[Mateus Getulio]

Hello again,

While we wait for the feedback from my colleagues, if you want to try something in the meantime, I can suggest to review the custom codes you created in the child theme, because it seems that it is the responsible for this issue.

We can confirm it because when any other theme is enabled (both default themes and your parent Genesis theme), the Maps in the website work just fine.

You can check the codes that were inserted in the custom child theme, and test to delete some of them, in order to check which one is the culprit.

Regardless, as soon as I receive updates from our second tier team I'll let you know about them, please stay tuned.

Thank you,
Mateus.

[tobiasH-7]

Hello! Some good news on this issue, I moved the Toolset plugin and information to the live website and the map seems to work on the live site. I now have a different issue, which may be easier to resolve. The searchable dropdown menus and the map do not populate with database - it's as if they are disconnected in some way? Here is a link to the live page where you can see the map does not display the listings and the drop down categories do not work - hidden link

[Mateus Getulio]

Hi there,

Thanks for your reply.

Similar to what was happening before, we might be facing an interaction issue with a third-party functionality, in this case:

- Deactivate all the plugins that are not related to Toolset
- Switch for a moment to a WordPress default theme like Twenty Twenty-one
- If the issue is gone, activate one by one to see with which one there is an interaction issue

Could you please tell me the results of this investigation? Just make sure to have a website backup before doing this procedure.

Looking forward to your reply. Thank you.

[tobiasH-7]

I am seeing an error message for Toolset as shown in my screenshot here. I reset everything and created a new site key and updated it but I am still seeing this message. Could this have something to do with my issue?

[Mateus Getulio]

Hi there,

Thanks for your reply.

Actually the issues are very unlikely to be related. Therefore, since the original issue is resolved, may I kindly ask you please to open a new ticket for this question?

This will also help other users with similar problems find solutions when searching the forum as well as we avoid mixing lots of questions in one ticket.

Thank you for your understanding.