grex22

@cybecom – Just as a heads-up, there appears to be an upgrade-safe solution for this problem described in this thread here:
https://www.ads-software.com/support/topic/salesforce-new-endpoint-with-the-summer-17-release/

It requires adding in some code to your theme’s functions.php file, but nothing too crazy. Hopefully this helps.

@arrowplugins Maybe related, but I’m seeing similar behavior — I’ll refresh the page (it’s on a local machine, if that matters) and the feed doesn’t appear. Sometimes, however, if I wait a good 3 or 4 minutes with the tab open, it finally appears. Very odd. Any ideas if this is related?

Bump?

Update — After diving into my particular issue a bit more, I’ve found that my problem was caused by my theme loading a Google map API call *before* A1EC’s call. THis causes the map to break and not display properly. If I switch to a different theme, the map loads fine. It may be worth checking for the other folks in this thread that the issue actually does lie in A1EC and not a plugin / theme conflict.

In my case, it seems like my theme with Visual Composer installed is causing the issue. VC loads in Google Mapping APIs even if you use them on the page or not, it seems.

Following this thread, as I also have the same issue. I’ve entered my API key in the settings panel, and in fact the API key is never passed as a parameter in the Maps script tag when viewing the page source. There’s just some simple bug that’s preventing the pasted API key from even being included in the map call.

Since there hasn’t been much response here from the devs, I may just jump in and fix it on my local install (rather than waiting on a new version). If I do, I’ll post my fix here for the thread.

It looks like you’ve got the wrong API types enabled for the key you’re using. I *believe* you have to enable the Google Maps Embed API for the particular key you’re trying to use.

Same behavior here as well — API key added, still getting MissingKeyMapError JS error in console. Caches have been flushed, plugins disabled, still same behavior.

Darn! I was taking a shot in the dark, but either way it sounds like you’ll be taken care of soon with a patch in the next week. Best of luck!

Samantha, I’m guessing you’re using Avada theme — I just went through this exact process myself the last couple of days, with the same error message. Avada has a fix specifically for this issue here:

https://theme-fusion.com/knowledgebase/avada-3-9-3-fix-wordpress-4-5-compatibility/

Just download that ZIP and overwrite the JS files it contains in your theme’s folder, and things should start working. Alternatively you could upgrade Avada to its latest version, but I understand that may not be possible if you’ve made previous modifications.

You were 100% correct, Tijmen — Wow, this is such a great plugin and you support the heck out of it. Major kudos.

It was the old version causing this issue, mixed with some VERY VERY STUBBORN caching from GoDaddy’s managed WordPress service. (Seriously, their cache takes like a full 12 hours to clear sometimes, even when using the flush cache feature.. )

Last night I ran a diff on the plugin vs the repo version (actually using Wordfence’s scan to find differences) and reincorporated them into the newly updated version of your plugin. After finally getting the cache to clear, all seems to be working wonderfully.

I wish the original developers of the site I’m working on realized that you’d added the ability to externalize templates into the theme. That would’ve been much easier to maintain than overwriting WPSL’s code..

Tijmen,
There is in fact caching, but repeated flushes haven’t affected the issue (nor has turning off the caching entirely).

However, I did some more digging and found that the version currently installed is 2.1.1 (the previous developer must’ve made changes to the WPSL code, because a “Block Plugin Updates” function is blocking any new updates to WPSL.. Sigh…

Is it possible that version 2.1.1 has that underscore library or old JS that you were talking about above? That would at least let me know if that’s a place to start looking to solve this.

THANK YOU FOR YOUR HELP. It’s very much appreciated

Can confirm that Avada theme previous to version 3.8.3 and earlier will cause this issue. It has nothing to do with WP Store Locator, but this was also how I came across this issue.

As a generally happy paying customer of Wordfence, this seems like a pretty big opportunity to snag threats that aren’t currently being scanned for. I’d say 90% of the infections I find in sites also deposit nasty non-core files into wp-includes/, and currently WF doesn’t seem to pick those up.

Like the OP, I only found them because of another security plugin I tried running.

It sounds like your review here is for the actual slider itself, and not this plugin that is designed to patch the slider’s vulnerabilities. You should remove this review and apply it instead to Revolution Slider

The plugin creator you gave 1 star to is actually trying to *fix* the issues you pointed out for Revolution Slider.

This is really strange to me.. There’s no way to figure out the “permalink” of a download to send to a friend, post in an email, etc, without creating the widget and copying the link that it creates.