[Chris]

Hi Kathy,

I really can’t say – I don’t know how your site and data are set up. If you’d like to provide a login and a specific example I’ll be happy to take a look.

In general, it’s best to set up each location you want mapped as a separate post. In your case it sounds like you might want one post per event. You could then assign events to a location using a taxonomy, and use a mashup by category/tag to show all events or just events for a location.

[Chris]

Hi,

I can’t say without a URL to illustrate the problem, but did you publish the post? Perhaps when you preview you’re just seeing the page before the marker has been saved completely.

If that’s not it, in general a good place to start is to disable all other plugins and the theme for a moment, to see if there’s a conflict.

Also, in the FAQ there’s a description of a “rocket” server add-on used by some hosts, that can interfere with rendering markers. It’s relatively rare so I’m not sure if applies to you.

[Chris]

Hi,

What version of the plugin are you using?

The default setting only affects *new* maps – any existing maps would have been saved with their original dimensions.

[Chris]

Hi Mike,

Feel free to send a link if you like.

SetCenter takes TWO arguments, a lat and a lng – not a structure. You can try hardcoding it to see:

mapp0.setCenter(-32,22);

[Chris]

Hi,

I don’t think you want to wrap your function calls in jQuery(). Try:
mapp0.setCenter(response);

Instead of:
jQuery(mapp0.setCenter(response));

[Chris]

When you enter a map in the map editor, it geocodes using the javascript API. That API uses the IP address of the client (your PC).

When a map is being generated on the server, it geocodes using the IP address of the server – which in this case is over the limit.

[Chris]

Sorry, I misspoke: the API key is only for map views, not for geocoding requests.

Geocoding is limited to about 2,500, by IP address. The only exception is there’s a higher limit (to 100,000, I think) for Google Maps for Business accounts – but it’s very expensive.

You can also configure MapPress to use the nominatim geocoder, but in my experience the resulting geocoding quality is poor.

[Chris]

Hi,

The message indicates that you or someone else has exceeded the maximum number of geocoding requests per day for the server’s IP address.

There’s some info in the documentation. In general you can wait until tomorrow or get an API key so Google can track your usage (if you think it’s someone else on a shared server).

[Chris]

You passed the result of the resize function to slideToggle, not the function itself. It should be:

`$(“#mapp”).hide();
$(“#maptoggle”).click(function(){
$(“#mapp”).slideToggle(“fast”, mapp0.resize);
});

[Chris]

Strange, I see the toggle taking 2 seconds and the map sizing correctly.

But then the ‘simple toggle’ code fires and closes the toggle control again immediately:

{$(document).ready(function(){$(“h3.symple-toggle-trigger”).click(function(){$(this).toggleClass(“active”).next().slideToggle(“fast”);return false;});

You should try this without using a plugin, and just call the jQuery slidToggle directly.

[Chris]

I guess the duration is in milliseconds. So try 2000.

[Chris]

Try this, “2” is for 2-second opening:

$(“#page-slider h3.symple-toggle-trigger”).click(function(){
$(this).toggleClass(“active”).next().slideToggle(2, mapp0.resize);
});

[Chris]

Hi,

Your site is still showing the original code. How about updating it with the code I gave you, so I can take a look?

[Chris]

Hi,

The workaround built into the plugin is for tabs. For the slider/toggle there’s no event for the plugin to watch for, so you’re doing it the right way.

For the issue with calling toggle twice, it may help to use the ‘complete’ argument for toggle(), to set the map resize *after* the animation finishes:

$(“#page-slider h3.symple-toggle-trigger”).click(function(){
  $(this).toggleClass(“active”).next().slideToggle(0, 1, mapp0.resize);
});

[Chris]

Hi,

That code would be very helpful if you want to restrict the result set by querying using lat/lng. As far as reading the result maps or poi details, it’s fastest to read them as a serialized object (the way they’re stored in the custom tables).

[Author]

Posts