Title: [6.0.26] Polyline bug found
Last modified: August 22, 2016

---

# [6.0.26] Polyline bug found

 *  Resolved [JCLG](https://wordpress.org/support/users/jclg/)
 * (@jclg)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/6026-polyline-bug-found/)
 * Long story short, if you save a polyline without actually drawing it, it breaks
   the map rendering in admin, and breaks markers on frontend.
 * It would be nice if there was some kind of failsafe or fallback for not saving
   a polyline correctly.
 * [https://wordpress.org/plugins/wp-google-maps/](https://wordpress.org/plugins/wp-google-maps/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [WPGMaps](https://wordpress.org/support/users/wpgmaps/)
 * (@wpgmaps)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/6026-polyline-bug-found/#post-5235291)
 * I apologize for the delay in response. I’ve had to deal with a personal emergency
   recently (my mother went to hospital) but all seems to have calmed down now. 
   Sorry about that.
 * We are aware of this and will be addressing this in the next version (hopefully
   early next week)
 * Thank you for informing us

Viewing 1 replies (of 1 total)

The topic ‘[6.0.26] Polyline bug found’ is closed to new replies.

 * ![](https://ps.w.org/wp-google-maps/assets/icon-256x256.png?rev=3058363)
 * [WP Go Maps (formerly WP Google Maps)](https://wordpress.org/plugins/wp-google-maps/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-google-maps/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-google-maps/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-google-maps/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-google-maps/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-google-maps/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [WPGMaps](https://wordpress.org/support/users/wpgmaps/)
 * Last activity: [11 years, 8 months ago](https://wordpress.org/support/topic/6026-polyline-bug-found/#post-5235291)
 * Status: resolved