Closed sstruemph closed 8 years ago
@sstruemph just to make sure - are you using the latest version?
@DevinWalker Does this look right?
It looks like you're on the latest version of pro - Just make sure that the core has the latest version too in the vendor/wordimpress/
subdirectory of the plugin
With the latest version of core, this seems to be a free and pro issue on the front-end only. I wonder if some of the new window code that I was working on got accidentally committed when it was generated. I’m digging into it.
I just put together a fix in core that I believe addresses this.
@DevinWalker, I noticed something in the code as I addressed this problem. It seems like sometimes a global gmb.info_window
object is used to deal with the info window, and sometimes a function parameter is used. I switched to the former in this case, and it solved the problem—the function parameter hadn’t been defined, up the tree. Is this a byproduct of how the plugin JS used to be architected? Is the gmb.info_window
global the right way to handle this, now? Just want to make sure I’m sticking with the right convention/method for the project.
@lchski you're correct here https://github.com/WordImpress/maps-builder-core/pull/43/files
Since our refactor we're using the object to interact with the info window throughout the plugin
Steps to replicate:
(tested with free and pro)
Errors: