Skip to content
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

interactivity problem with hided layers in published maps #5858

Closed
oriolbx opened this issue Oct 5, 2015 · 7 comments
Closed

interactivity problem with hided layers in published maps #5858

oriolbx opened this issue Oct 5, 2015 · 7 comments

Comments

@oriolbx
Copy link
Contributor

oriolbx commented Oct 5, 2015

In the CartoDB editor, when you add two layers and one of them is hidden. When the user publish the map the visible layer loose its interactivity or it confuse the infowindow property with the tooltip property.
Steps:
1- Add layer 1 to a map
2 - Add layer 2 to a map
3 - only enable infowindow in layer2
4 - hide layer 1
5 - Publish map
6- Layer 2 doesn't have the infowindow, but it has a tooltip. Also, in some cases it doesn't show any interactivity.

Image step 4:

infowindow_layer_no_hover

Image step 6:

screen shot 2015-10-05 at 14 20 45

@saleiva
Copy link
Contributor

saleiva commented Oct 5, 2015

@alonsogarciapablo worked on this I think...

@xavijam
Copy link
Contributor

xavijam commented Oct 5, 2015

I followed those steps and the map generated is working. Any clue with you have the map failing and not me?

@alonsogarciapablo
Copy link
Contributor

It works for me too, even after applying the bubble wizard to the visible layer...

@oriolbx
Copy link
Contributor Author

oriolbx commented Oct 5, 2015

Ok...it is working now for me too...

@javisantana
Copy link
Contributor

did you check:

  • errors in the console (both client and server side)
  • cache problems looking to the viz.json headers and adding some cache buster to the url

In theses cases is not always as trivial at it looks but we need to dig deeper to find the real problem

@acanimal
Copy link
Contributor

@oriolbx @xavijam Could you try if you are able to reproduce the error again?
I'm working on a similar problem (see CartoDB/carto.js#122) without success to reproduce the error.

@alonsogarciapablo
Copy link
Contributor

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants