chrisvrichardson

Network activation should now work. There was also an error with using an upper-case wordpress database prefix, which is also corrected. Thanks to DETC and Kristarella for reporting the issue!

Hi, I may have a solution for you. Please contact me here:
https://wphostreviews.com/chris-contact

Hi, that’s the default behavior of Google’s geocoder, but try the latest version – I’ve updated 2.12 to allow directions for lat/lng locations.

I don’t have any trouble with my own feedburner feed. Please try disabling you other plugins to rule out a conflict there, then contact me directly with your URL, your feed URL and details about exactly what’s happening and I’ll try to help you out.

Hi,

Try deactivating your other plugins, there may be a conflict. Also, please contact me using this link and provide your site’s URL so I can take a look.

Hey John,

Glad it’s working. There was a separate conflict with the prototype.js library, which is included by some other plugins. Prototype seems to break the jQuery width(), height() and JSON functions. I updated MapPress to work around the issue (I hope!)

Hi,

I think that error may be because your address must be geocoded. You need to geocode the markers before you call display().

Take a look at the geocode() function and also the save_post() function to see how to handle the goecoding results, along with google’s documentation:
https://code.google.com/apis/maps/documentation/geocoding/

If you just want to display a map from addresses in a custom field – if you’re patient, I’m currently working on adding this into the plugin itself, but it may be a while before I get it done.

Hi,

In mappress.css, I have some comments for the various CSS classes. The one you want is “.mapp-overlay”. You can get black links like this:

1. Create a custom CSS file somewhere on your server
2. Enter the URL to it in the MapPress options screen
3. Put this in your CSS file:

.mapp-overlay a {
color: black;
}

I hope that helps!

Hi Folks,

Thanks for your patience. If you copy the new version files over the old version without activating the plugin you’ll get this AJAX error.

As the helpful folks above discovered, the fix is to deactivate and reactivate the plugin.

I’ve also modified the plugin to warn you if it must be reactivated.

Sorry for the confusion.

Have you had any luck using the current version (2.0.1) or higher?

Hi Thomas,

I’m not sure what you meant about the ‘&’ but the plugin seems to be working. I think the map is greyed out because of CSS settings in your theme conflict with Google maps.

If a map is to be hidden it must be with “visibility: hidden’ rather than ‘display: none’ on the map <div>. Otherwise Google has trouble determining the map size.

I think your tab control (tabber.js?) is probably hiding the map. The comments say:

/* When a tab is to be hidden, instead of setting display=’none’, we
set the class of the div to classTabHide. In your screen
stylesheet you should set classTabHide to display:none. In your
print stylesheet you should set display:block to ensure that all
the information is printed.
*/

You could try setting your classTabHide to “visibility: hidden” instead, or try a different tab control.

Found & fixed the error – thanks for reporting it. Should be OK in 2.0.1.

2.0.1 also adds:
– street view
– enable/disable keyboard shortcuts

Hi,

Please deactivate and reactivate the plugin. If you stil have the error, please contact me using the page below (I don’t usually read the WP forums):

Contact Page

Hi,

This feature is included in the latest beta along with lots of other neat stuff.

It’s located here if you’d like to help test it:
https://wphostreviews.com/mappress/mappress-beta

Hi,

This was a tricky issue, but I think it’s resolved.

The original problem was a bug in the wordpress 2.9 json_encode function (ticket 11537 above). I released MapPress 1.5.8.9 to fix this.

However, there was a second issue: there are other plugins that include versions of JSON.php that don’t contain the encodeUnsafe function. If you were using one of these plugins, it would crash MapPress.

I released MapPress 1.5.8.10 a few days ago. It should fix both issues. I’m now including the standard JSON.php class in my own namespace with my own json_encode function module.

When WordPress 2.9.1 is released I’ll remove the extra code.