Problems in publishing location

Welcome to Portals United! / Forums / Troubleshooting / Problems in publishing location

  • Author
    Posts
  • June 3, 2025 at 10:04 am #1653

    I’m encountering errors that I’m unsure how to resolve when trying to publish my project. For the moment, the errors occur in two of the three locations. By selecting F12 I also do not get which is the error, since it is not always the same. I am worried my project is too large. I would like to attach the file with the errors but right now it looks I can only attach images or links.

    In case of multiple locations, how to do a single application? Simply by selecting all three during the export procedure?

    June 4, 2025 at 9:39 am #1654

    Actually, it’s not going to work in the shop. Do you have access to a server where you can store some files for public read access? If so, you can use the Nodes for switching between locations as expected. But in the shop, you would have to know the download URL of the corresponding vrml file locations within the shop. However, these names are hidden and it gets too complex to unravel those hidden references. Uploading the project to the shop would present the user with one link for each vrml file. So you could theoretically jump to any one of those locations directly by clicking on one of those vrml file links.

    Instead, upload your project files to some other location and upload only the vrml file which points to the first location into the shop. Of course, in that vrml file you have a link which points to the data on your own (or hosted) server.

    June 4, 2025 at 2:08 pm #1656

    We’re encountering a similar issue in our project, which involves 5 different locations that the user navigates through sequentially.

    So, if I understand correctly,  we have to publish the <span style=”text-decoration: underline;”>first VRML in the shop</span>, and using node “change location-external location”  OR  node “open link” inside the first vrml will then open the rest 4 VRML files (stored in  a server  for public read access)  using the method you described earlier.

    Any additional guidance or suggestions on this approach would be greatly appreciated.

     

     

     

    June 4, 2025 at 3:58 pm #1657

    Use Change Location. Open Link will attempt to start the Hopper, because the file ends in VRML and Open Link will automatically start the matching app. .txt runs the text editor and .ppt launches the PowerPoint app. But the Hopper is already running, so Open Link will fail.

    Let’s assume that you have a server/domain named MyDomain.com and on that server a public folder named xr4ed. Place the other 3 vrml files there. Let’s say they are named vrml2.vrml, vrml3.vrml, and vrml4.vrml.

    The nodes which call those links would then call the external link http://MyDomain.com/xr4ed/vrml2.vrml for the second vrml etc.

    You could even place a duplicate of vrml1.vrml there so you can create a “round trip” going back to the first location after the third location.

    If you did that, you could also publish the link even in this forum (or in a pdf or ppt etc…) as an entry point to the hopper. Just add hopper: to the link. The address of the entry point vrml (first location) would then be published as hopper:http://MyDomain.com/xr4ed/vrml1.vrml – share with your friends (who have a hopper installed)!

     

    You can test it here

    June 5, 2025 at 8:35 am #1663

    Should all the vrmls be published in the shop?

    Or only the first one ?

     

    June 5, 2025 at 9:58 am #1664

    Only the first one to avoid confusion which VRML link should be clicked on. But you must do this manually. If you use the XR4ED plugin to publish, then the links will be all wrong. You use the custom publishing with the root domain you are using. Then upload only the first VRML file and a picture and descriptions.

  • You must be logged in to reply to this topic.