-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating the third party #120
Comments
Hi @Misagh90, Thanks for bringing that up, we've been working internally to decide whether to continue to use the store locator plugin or break away from it and explore something like reactJS to run the mapping. Unfortunately the early version of the locator module uses a hacked store locator script, so updating to the latest plugin version will take some time but we have started that work in a local branch. Thanks for the feedback and we'll ping this ticket once we determine how we're going to move forward. |
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
closes dynamic#129 closes dynamic#120
Hi,
I check the third party folder, and understand that the jQuery Store Locator is changed and the latest version of jQuery Store Locator is 2.7.1
because of this changing the Silverstripe locator needs to update to the new one.
Thanks,
The text was updated successfully, but these errors were encountered: