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

TypeError: vis.Timeline is not a constructor #33

Closed
shosaco opened this issue Jul 4, 2017 · 6 comments
Closed

TypeError: vis.Timeline is not a constructor #33

shosaco opened this issue Jul 4, 2017 · 6 comments

Comments

@shosaco
Copy link

shosaco commented Jul 4, 2017

When running a simple example, I get the error in the javascript console "TypeError: vis.Timeline is not a constructor[Learn More]" and the output doesn't show up.

The example is a module in a bigger app. This happens only on my Linux machine, not on my windows.

library(timevis)
ui <- function(id){
  ns <- NS(id)
  fluidPage(h3("Timeline:"),
            timevisOutput(ns("timeline")))
}

server <- function(input, output, session) {
    output$timeline <- renderTimevis(
      timevis()
    )
}

shinyApp(ui, server)

R version 3.3.2 (2016-10-31)
Platform: x86_64-redhat-linux-gnu (64-bit)
Running under: CentOS Linux 7 (Core)

@shosaco shosaco changed the title TypeError: vis.Timeline is not a constructor[Learn More] TypeError: vis.Timeline is not a constructor Jul 4, 2017
@daattali
Copy link
Owner

daattali commented Jul 4, 2017 via email

@shosaco
Copy link
Author

shosaco commented Jul 4, 2017

The CentOS machine is my host for the shiny app, a remote machine used for my webserver, so I basically cannot "navigate" to visjs.org to try it. If there is anything that I can try to find the root cause of this problem, please let me know. And thanks for the great package!

@daattali
Copy link
Owner

daattali commented Jul 4, 2017 via email

@daattali
Copy link
Owner

daattali commented Jul 4, 2017 via email

@shosaco
Copy link
Author

shosaco commented Jul 5, 2017

I just fixed it, this issue was related to issue #11 and #12, I had visNetwork V1.0.1 running, whereas the bug was fixed there with V1.0.2. Upgraded now and timevis is working fine.

Thank you very much! If your travels lead you to Munich, let me know!

@shosaco shosaco closed this as completed Jul 5, 2017
@daattali
Copy link
Owner

daattali commented Jul 5, 2017 via email

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

2 participants