[BradSiegfried]

Hi Chris,

I’ll tinker with it.  If I find anything useful I’ll post back.

Thanks.

Brad

[BradSiegfried]

Hi Chris,

I tested that code and it works great. (I put it into my generic site utilities plugin instead of functions.php; no worries about theme updates that way.)

Thanks once again for the outstanding support.

Brad

[BradSiegfried]

Don’t forget to tick the box for that post type in MapPress Basic Settings.

[BradSiegfried]

Hi Chris,

Thanks, that was just the ticket.  I used this shortcode syntax that worked fine:

[mashup query="post_type=crimes,units" width="98%" height="600" marker_link="true"]

(I also made a new custom post type “crimes” rather than leaving those as generic “posts.”)

The info at http://thereforei.am/2011/10/28/advanced-taxonomy-queries-with-pretty-urls/ was also very helpful.

Brad

[BradSiegfried]

Hi Chris,

Between my content changes and your latest code changes, I’m not having an issue with unwanted automatic maps any longer.  If it crops up again I’ll try using the filter as you suggested.

Please consider this issue resolved.

Brad

[BradSiegfried]

Hi Chris,

Thank you for digging into this issue and resolving it.  Types & Views is working just great with MapPress mashups now.

Brad

 

[BradSiegfried]

Hi Chris,

I’m running the 2.38.6 version that you emailed to me on 7/25/12 for
testing.

See my email to you of 8/3/12 for details.

I’ve been testing to try to see where the conflict between MapPress and Types & Views is happening.  When I do the mashup before the view, the view produces a “No posts found” error.  When I do the view before the mashup, both work fine.  However, I wanted the mashup at the top of the page, not the bottom.

I don’t have the technical chops to see where the conflict is happening.  I hope you will be able to work with the Types & Views folks to shed some light on this.  I have been corresponding with Caridad at Types & Views, and encouraged her to contact you.  Perhaps you can exchange full versions of your respective plugins in order to improve compatibility and support for your common customers.

Thanks for your help.

Brad

[BradSiegfried]

In mappress.php the function the_content provides several methods to determine whether to add a shortcut that will create an automatic map or not.  Would it be possible to set an appropriate variable prior to or within the View Template so as to match one of the existing methods, thereby not creating an automatic map?

For example, would it be possible to set the value of $autodisplay or a similar variable at runtime? I’m not clear on how the loop works in terms of when things happen relative to each other.  I’d be happy if I could embed a shortcode to turn auto mapping off and on, for example:

[maps_off] generate desired output with a View Template [maps_on]

Or, can you suggest any code additions to the mappress function the_content so that it can determine whether the View Template is asking for the entire post body (automatic map desired) or just a particular field (no automatic map desired)?

Thanks.

Brad

[BradSiegfried]

Hi Chris,

I put in a support request with Types & Views regarding this issue (#10096) of filtering the automatic map and  also the issue (#10097) regarding the effect of  mashups on subsequent queries.

See http://wp-types.com/forums/topic/using-types-and-views-with-mappress-plugin/.

I’ll let you know what I hear back.

Brad

[BradSiegfried]

Hi Chris,

Thanks for the quick reply.

I did upgrade to Mappress Pro version 2.38.5.

1. I tried setting the address field value as indicated below (with straight quotes):

correctedaddress=”513 W 7th St, Wilmington, DE 19805″ title=”513 W 7th St” iconid=”red-dot” point_lat=”39.744481″ point_lng=”-75.554222″

I also set the value for lat and lng fields.

The result was tooltip text still showed lat/lng rather than the desired title when displaying that individual post. It would be nice to be able to set the title (and other values) when using lat/lng rather than geocoding.  Maybe in 2.38.6?

This only affects the individual post with the POI.  On mashup maps that include this post, the tooltip and POI list show the origin post’s title, not the lat/lng.  So, the mashups look fine.  See http://wilmington.crimeboard.org/index.php/wilmington/4th-district/.

2. I set [mappress zoom="15"] on the individual post.  That worked well and still resulted in only one map, the automatic map, being generated.

3. I will build a dummy post to ensure that the meta field for errors persists even if all my posts geocode perfectly, or not at all.  It might be more efficient to keep using a dummy post than taking a couple bytes for “OK” on every post.  But I guess worrying about a couple bytes here and there is a bit old school.

Thanks for a great plugin.

[Author]

Posts