Designer Portal reloading endlessly
See original GitHub issueBug description
After building the designer portal and hosting it, it will reload endlessly.
Reproduction steps
- RUN
npm install
- RUN
npm run build-designer
- Host dist/designer folder somewhere ( i.e. iisexpress:
iisexpress /path:PATHTODESIGNERFOLDER /port:8081
- GoTo localhost:8081
=> page is reloading endlessly
Expected behavior
I expect it to not reload all the time.
Is your portal managed or self-hosted?
Self-hosted
Release tag or commit SHA (if using self-hosted version)
most recent master
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Can't load eDesignSuite power supply design - ST Community
Attempting to load the Power Supply Designer results in an endless loading spinner. This is reproducible for me across multiple browsers ...
Read more >Designer Portal
Pillar-mounted slewing jib cranes in low-headroom design, with I-Beam jib arms and endless slewing range (n x 360°) and wall-mounted slewing jib cranes....
Read more >JavaScript hard refresh of current page - Stack Overflow
You answer has refresh() being called on script load. That's why it's doing an endless loop. You coded it to refresh on load....
Read more >Unable To Open Label - BarTender Support Portal
As I double click the label, it seems to load but then ends up not loading, and the screen BarTender loading banner remains...
Read more >Why Does Ansible Tower Reload Indefinitely after an Upgrade ...
Issue. After upgrading to 3.6.2, Ansible Tower's front page continues to reload or redirects to an unexpected page.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thx @ErikMogensen , you pointed me into the right direction. The
config.json
produced bynpm run build-designer
is theconfig.runtime.json
not theconfig.design.json
. I fixed it by adding{ from: "./src/config.design.json", to: "config.json" }
to theCopyWebpackPlugin
in thewebpack.designer.js
. But somehow it is strange, why am I the only one having that problem. This should be an issue for everybody.Thanks @cirellamhcs, yes that’s the right workaround.
It, of course, should not behave like this, something got broken along the way, so we’ll fix this. Also, just in case, this workaround cannot be used for production because you expose the token. Depending on the specific production setup, it can be handled differently. We’ll provide some recipes soon.