Please put the exact page URL of where you installed your Double the Donation search tool.
Flag: PLUGIN_HTTPS
Message: The plugin URL should begin with https:// or http://.
How to Resolve: Add https:// or http:// to the beginning of the plugin URL, depending on if your website’s URL begins with https:// or http://.
Flag: PLUGIN_IFRAME
Message: The plugin appears to be installed as an iFrame on the page. The iFrame implementation is highly discouraged for 360MatchPro users because it disables email click tracking.
How to Resolve: 360MatchPro clients should use either our full HTML/JavaScript plugin or WordPress Plugin on your dedicated matching gift page. This will enable full tracking and automation within 360MatchPro.
Flag: PLUGIN_KEY
Message: Our automated scanner isn't able to detect the proper public API key for your account. Please make sure the public API key that you added is correct.
How to Resolve: With the support of a technical person on your team (if needed), visit your matching gift page, press F-12, navigate to the console tab, type DDCONF, and then press enter. If your public key is visible, then you are squared away and the automated scanner generated a false negative. If the public key is not visible, add the following line of code somewhere in the HTML of your page: <script> var DDCONF = {API_KEY: "your public api key"}</script>
Reasons why our scanner may be wrong:
Your matching gift page has a blocker (eg. pop-up, reCAPTCHA, etc.) that prevents the scanner from parsing the HTML on your page.
The DDCONF variable that contains your public key is included in another JavaScript file that you created. Our scanner only parses your main page’s HTML code.
Flag: PLUGIN_JS
Message: Our automated scanner is having a tough time finding the Double the Donation plugin on your webpage. If our plugin is appearing and working correctly, please disregard this warning. For additional technical context, our automated scanner is looking at your HTML code in search of the ddplugin.js file but couldn't find it. It's possible that the browser downloaded the ddplugin.js file via JavaScript instead of an HTML <script> tag, and that's OK!
How to resolve: With the support of a technical person on your team (if needed), visit your matching gift page, press F-12, navigate to the console tab, type doublethedonation, and then press enter. If a console error is not generated and you see the plugin on your page, then Double the Donation’s script was installed on your website and you are likely squared away. Our scanner likely produced a false negative. If a console error is generated (i.e. ReferenceError), please go to your current Double the Donation account and re-copy and re-paste the full plugin code.
Reasons why our scanner may be wrong:
The code in our ddplugin.js file was copied to your server, and that file from your server was loaded into your website. Be careful if you do this since copying our code to your server will prevent you from automatically receiving software updates.
You prefer the iFrame installation. Instead of using our standard iFrame implementation, your iFrame is pointing to another site that has our plugin on it. Our scanner does not recursively search iFrames that point to other sites.
Flag: PLUGIN_CONTAINER
Message: Our automated scanner is having a tough time finding the Double the Donation plugin on your webpage. If our plugin is appearing correctly and working correctly, please disregard this warning. For additional technical context, our automated scanner is looking at your HTML code in search of the <div> tag with an id attribute of 'container' but couldn't find it. It's possible that the <div> tag is injected into the HTML asynchronously (after our scanner parses your HTML), and that's OK!
How to resolve: If you see the plugin on your site, then you are likely squared away. Our scanner generated a false negative. If you don’t see our plugin on your site, add the following in your page’s HTML where you would like the plugin to render: <div id=”container”></div>
Reasons why our scanner may be wrong:
The <div id=”container”></div> element was injected into the page via JavaScript. This often occurs when using frameworks such as React and Angular.