Shop Categories

X

API Key in my Website – conflict with another api key from my Plugin

Home Forums Agama Pro API Key in my Website – conflict with another api key from my Plugin

Topic Resolution: Resolved

Tagged: 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #26640
    Bernd Tomasini
    Participant

    Hi!

    I have a big problem on my website. I have installed a plugin on my website that requires an API key. Unfortunately, for whatever reason, another API Key was generated on the website. But this on the complete website, independent of the tab. This one blocks my other one, so the plugin does not work properly.

    Since I have not installed another plugin that requires an API key, I think the key comes from the template of Theme Vision. Are there any possibilities to find out, for which the API key is that I do not know?

    This is my active API Key of my plugin, which I have activated on Google:

    AIzaSyB8U…NtkrJA

    This is the API key I can’t assign:

    AIzaSyAo_…EU2-5I

    Can you help me?

    Thanks!

    #26645
    Zex
    Moderator

    Hello, Bernd!

    It’s possible that you have a conflict with the map widget

    Here are the guidelines on how you can temporarily resolve the API conflict:

    1. Open the theme Editor (Dashboard->Appearance->Editor)

    2. Chose to edit an Agama Pro theme in the top-right corner.

    3. On the right side, find the widgets.php file, located on the framework/widgets/ folder.

    4. click on a widgets.php file to edit it.

    5. In the main window, comment the line #12 (add a // sign in front of the line of the code).

    6. Click on the “Update file” button to save the changes.

    7. Refresh the page.

    https://prnt.sc/ppndt9

    Please let me know if that resolved the Api conflict.

    Regards

    #26647
    Bernd Tomasini
    Participant

    Ok, thanks!

    I’ll try it.

    Can you tell my why there is a API key included?

    Thanks!

    #26648
    Bernd Tomasini
    Participant

    The API Key seems to be removed.

    We’ll see.

    Thanks for that!

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.