Map zoom on scrolling mouse

[jameswemyss]

When the user scrolls down a page using the scroll wheel (which I am guessing is typical) and the cursor/selector comes to the map, the action then zooms the map in and out, leaving the user to then move to the scroll bar in the browser. How do I stop the map “zoom on scroll” function?

I found the article here , however the file referred to no longer exists and the thread has been closed.

[Barry]

Hi James,

Right now you’d need to modify a core plugin file (the-events-calendar/resources/embedded-map.js) to make this change.

Typically we wouldn’t recommend that approach – primarily because it will be overwritten when next you update – but it’s certainly possible if you want to give it a go.

A more robust and future proof approach, though it’s not for everyone, would be to dequeue that same script and replace it with your own (which could be based on the original).

I hope that gives you a few ideas you can explore 🙂

[jameswemyss]

Thanks for coming back to me Barry.
To be honest I found the responses to all my questions somewhat disappointing. I firstly sent an email to ask for prices for all these bits, to which I got an email back from Leah suggesting that the help I needed could be found by posting in the forums.
Whilst “support” is always keen to say “what a great idea” or “good point” it always seems to result in “you need to engage someone else to help you”, which seeing that we have paid for two plugins as it came with support feels less like support and more like batting the problem away or adding it to a wish list that you may/may not implement.

Leah did also say in the email “1. This is on our list as things to do a tutorial for. In the meantime, you might try the solution given in this thread.” which takes you to the link I provided in this thread. You have previously recognised this as a problem and supported it, you also recognise this as something that needs a tutorial. But because something has changed you now don’t seem to recognise it as a problem and have suggested something that “Typically we wouldn’t recommend that approach” or bat it away for us to find someone else to support your plugin.
Regards
James

[Barry]

Hi James,

I’m sorry to hear that you are disappointed in our level of service.

We want to help to the extent we can – but it isn’t practical for us to offer unbounded assistance for every problem and at this point I would like to draw a clear distinction between support on one hand and customization work on the other.

In delivering support our primary goal is to help you understand how the plugin works and point you in the right direction if something is unclear.

Collecting bug reports and – where it’s reasonable for us to do so – helping you workaround any bugs until they can be resolved in a future release is similarly a high priority task in terms of our support service.

However, when it comes to customizations – changing how the plugin functions and behaves – service is naturally more limited.

We simply cannot afford to act as an on-tap design/development service – that just isn’t our role and if our product page, terms and conditions or anything else led you to believe it was then we’re more than receptive to your feedback so that we can make things clearer for other current and future users.

Even so, we fully recognize that for our users to get the most from our plugins they will frequently need to customize them. To that end we develop and maintain a rich set of learning resources in addition to providing more-specific assistance on a topic-by-topic basis where it makes sense for us to do so.

But because something has changed you now don’t seem to recognise it as a problem and have suggested something that “Typically we wouldn’t recommend that approach” or bat it away for us to find someone else to support your plugin.

Typically we would not recommend it – nor did we recommend it in the other topic you referenced (the proposed solution there came from a customer).

That’s not to say you can’t or shouldn’t apply it – and hopefully with the direction I gave you in my first reply you can use it on a current version of our plugin if you choose to do so: that decision is something for you to make (and if you don’t feel comfortable, don’t do it – hire someone with suitable skills or explore a different strategy such as I outlined).

Lastly, I would take issue with your statement that we are “batting things away”. From Leah pointing you to a possible existing solution on the forums to my helping you apply it to the current release we’ve done our best to get you on track.

To close:

• What do you still need help with to drive this forward? We can’t build the final solution for you, but perhaps we can point you to some further resources if you have additional questions
• I will talk to Leah and highlight your concerns, with a view to possibly re-prioritizing any tutorial work on this subject

I hope that clarifies our position and definitely let me know if you’ve got further thoughts/questions here.

[Barry]

Hi!

It’s been a while so I’m going to go ahead and close this topic.

• Need help with anything else? Go right ahead and post a new topic, one of the team will be only too happy to help
• Still need help with this issue and need to re-open it? Again, please simply create a new topic and link to this one to provide the team with some context

Thanks!

[Author]

Posts