-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Loading maps, discover, visualize and dashboards logs backend.js:6 TypeError: (0 , _url.modifyUrl) is not a function in console #50173
Comments
Pinging @elastic/kibana-gis (Team:Geo) |
Pinging @elastic/kibana-app (Team:KibanaApp) |
@bhavyarm Could you share your saved objects? I tried with the sample data on a development server as well as the BC directly and I don't get the message. |
@flash1293 lets talk tomorrow. I can reproduce this easily. Thanks! |
So can't reproduce this on 7.5.0 BC4. Will try again on BC5 and then close the bug if I can't. Thanks @flash1293 |
I can reproduce this problem on master. It mostly happens when adding filters while the mentioned apps. |
I have tracked down this error and figured out the cause. Follow these steps to reproduce:
There is a bug in angular_config method $setupUrlOverflowHandling at https://github.com/elastic/kibana/blob/master/src/legacy/ui/public/legacy_compat/angular_config.tsx#L356. |
@flash1293 Opened #50747 to resolve this issue. |
@nreese Thanks for looking into this, it was on my list for today, but I probably would not have figured it out so fast. Can I also assign this issue to you? |
Kibana version: 7.5.0 BC4
Elasticsearch version: 7.5.0 BC4
Server OS version: darwin_x86_64
Browser version: chrome latest
Browser OS version: OS X
Original install method (e.g. download page, yum, from source, etc.): from staging
Describe the bug: If you navigate to maps, discover, visualize and dashboards Kibana logs
TypeError: (0 , _url.modifyUrl) is not a function in the console.
Steps to reproduce:
Screenshots (if relevant):
Errors in browser console (if relevant):
The text was updated successfully, but these errors were encountered: