Devin Howard
Devin Howard
Yes. You should point metamaps to the machine that has the working realtime server. Have you gotten a .env file setup? If so you can point metamaps to the working...
If its running on your local machine, try using localhost:5000 or 127.0.0.1:5000 On Tue, Jul 25, 2017, 8:28 AM Hariharan Gopalan, wrote: > I tried using both the internal IP...
@haribole did this fix work for you? It looks like Connor made the change above in 785e16eeae941e563ca1027a19ab70f7fabcf2b0
yeah, which is a good point. i've been trying to limit my enthusiasm for new js features so that we continue to support legacyish browsers. I do think it's worth...
I got it to update the query string when you zoom/pan the map in this PR!
That's great! This is a big "public api" decision, so i think it's prudent to really think it through before pushing to metamaps.cc. once we enable it it'll be hard...
Interestingly enough, I can't replicate this on my local dev machine. I'll try again on heroku maybe.
I'm guessing this doesn't happen locally because the connection is so fast. But it is pretty weird. I'm not prioritizing this at the moment because no one is complaining. Please...
@Bortseb I can't replicate your error where it says "Please enter topic title" when you hit enter. can you give more details?
ok i believe all bugs are fixed in the latest (deployed to heroku) except for the problem where you roll over and then move away