We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Problem Loading Verge directly on my Website with Version 4.2.0

Home Forums Bug Reports and Feature Requests Problem Loading Verge directly on my Website with Version 4.2.0

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #60001
    Armin Bastl
    Customer

    Hello There,

    i am trying to include a Verge app into a webpage directly by including the JS and CSS Files:

    <script src="/somefolder/3d/test_app/v3d.js"></script>
    <script src="/somefolder/3d/test_app/test_app.js"></script>
    <link rel="stylesheet" type="text/css" href="/somefolder/3d/test_app/test_app.css">
    <div id="v3d-container">
    <div id="fullscreen_button" class="fullscreen-button fullscreen-open" title="Toggle fullscreen mode">
    </div>
    </div>

    This had worked flawlessly with Verge Version 4.0.0 and 4.0.1, but since Updating to 4.2.0 the import of visual_logic.js inside v3d.js tries to get the file by the current url rather than the directory where the v3d.js is located.

    ERROR:
    GET https://someurl.net/someslug/somepage/visual_logic.js net::ERR_ABORTED 404

    Expected behaviour: The import of visual_logic should also work if v3d.js is not loaded from the verge app’s root folder.

    #60003
    kdv
    Participant

    all you need is just to copy directly the app’s folder somewhere into your server folder. nothing else. why do you change paths to js/css files? they are relative and lead to the app’s folder provided test_app.html is located in the same folder. Did you move test_app.html? In your case test_app.js can’t find visual_logic.js in the root of the app’s folder. Looks like you moved it somewhere else…

    Puzzles and JS coding. Fast and expensive.

    If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.