aitosoftware

As of today, we no longer offer a free plan. The costs for supporting the free service has grown too large to be sustainable.

Existing free accounts continue to work, but setting up PulseMaps on a new site now requires one of our paid plans.

Also, version 1.7 of the plugin should fix the problems with installing it on a new site. Older plugin versions had some issues (with libcurl, as well as with the facebook login) which have been resolved in the new plugin.

katrinazhang, ncc16: This issue may be caused by a missing “curl” PHP extension. Especially on Windows it’s not always installed. Check with your wordpress hosting provider whether the curl extension is installed.

lousywriter: Your problem appears to be caused by having the PulseMaps widget twice on the same page. It’s once in the left column (but hidden with CSS), and again in the right column. The widget won’t work if it’s used several times on the same page.

It seems that the Gravatar hovercards plugin might be causing this problem for some reason. If you remove https://s.gravatar.com/js/gprofiles.js?ver=2013Janaa from the page, the duplicate widgets won’t appear and everything works fine.

Hi roleled, your widgets are now back. One of our servers suffered a failure and some widgets were off-line for a while.

If the PulseMaps widget appears in red, that means that the widget is not added to any sidebar, footer, or other widget area. To activate the widget, drag the widget to a sidebar on the right.

Hi Geoff,

There appears to be an issue with the PulseMaps plugin when doing network activation. We’ll take a look and see what can be done!

Meanwhile, normal (single-site) activation should work fine, but each site will of course be separately tracked.

Hi John,

First of all, sorry for the delay in answering!

To investigate this issue, we’d need the following info:

• WordPress version
• PulseMaps plugin version
• Other plugins and their versions
• The browser and OS you’re using

Also, does the entire screen go blank, or just part of it? Which part? A screenshot would help a lot! If you wish, you can email one at [email protected], and we’ll do whatever we can to figure this out.

We experienced two service outages, almost back to back, due to power failures in the area where the data center hosting our servers resides.

The power outages were relatively long, about 1 hour and 2 hours.

We’re very sorry that this happened and are already looking at alternative providers where outages such as these would be less likely.

Yep, definitely something wrong with that other plugin (getting a PHP syntax error from it). Found no conflicts with mod_pagespeed or JS-minify.

Thanks a lot for investigating the issue further!

We’ll check for conflicts with the other plugin.

Thanks for the info!

So I guess we can say that the problem is not in the PulseMaps plugin, but something else in your setup.

In any case, to be sure, we’ll do some tests with mod_pagespeed and JS-minify, and will report back here about our findings.

I’m sorry to hear our plugin doesn’t work for you. Let’s fix that.

Do you mean Firefox 6 and IE 9 alert you with a Javascript error or something like that? Can you provide more details about the error:

• the exact error message
• the URL you were visiting
• WordPress version
• List of other plugins installed and their versions
• anything else you see or can think of that might be relevant

These would help a lot to diagnose the problem!

Thanks.

Yeah. We didn’t realize that name conflicts could occur also with file names (and still don’t quite understand how exactly it can happen). Pretty much everything else we already have prefixed.

Finally found the problem (at least I think it’s the one you encountered) and it’s fixed in version 1.3.1 of the plugin.

For record, the issue seems to be a bug in WordPress multisite/network; if a plugin contains a file with the name “settings.php” the network admin pages won’t work. We renamed the “settings.php” to something else and now everything seems to work fine.

We found no issues with BuddyPress compatibility.

Hmm, perhaps you mean BuddyPress 1.2.9 and not 1.9?

Anyway, we’ll test compatibility with the latest BuddyPress version and will post a reply with our findings.

Thanks for the report!