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

Fix old wavesblockexplorer. #35

Closed

Conversation

username1565
Copy link

@username1565 username1565 commented Nov 2, 2019

Add files to successfully build and run this old wavesblockexplorer.
See this issue: #29

Also, I want some waves here: 3PHwTZasBNSnDJNP68v7Awcs3paRLTHnoao

Add files to successfuly build and run this old wavesblockexplorer.
Copy link
Contributor

@beregovoy68 beregovoy68 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, I can't accept this PR. I appreciate your interest to this project, however, we're not going to support old version of Block Explorer.

src/js/bundle-1.1.8.js Show resolved Hide resolved
src/js/config-1.1.8.js Show resolved Hide resolved
src/js/templates-1.1.8.js Show resolved Hide resolved
BUILD_yarn-install.bat Show resolved Hide resolved
Copy link
Author

@username1565 username1565 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, I can't accept this PR. I appreciate your interest to this project, however,
we're not going to support old version of Block Explorer.

Ok. You can cancel and close this pull-request then. But this waves blockexplorer working better than new wavesblockexplorer, because that new blockexplorer want to enable CORS somewhere, and cann't loading blockchain data from localhost.

This blockexplorer working good on localhost and loading data from waves full node without any problems.

Best regards.

@username1565
Copy link
Author

You can try to build and run this old wavesblockexplorer from your repositary and from my.
I don't see any autogenerated files, when I try to build old explorer from the old-explorer branch in your official repositary.

Fix the URL for the node on the opened host,
to open old wavesblockexplorer from external IP or domain name.
Copy link
Author

@username1565 username1565 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see the code to generate "autogenerated files", while compilation processing.
So I just copy this js and css files, from old https://wavesblockexplorer.com/
and include this in index.html. Now, there is new working blockexplorer, not old.
But files are saved, and here you can find it, and see the source code.

package.json Show resolved Hide resolved
server.js Show resolved Hide resolved
server.js Show resolved Hide resolved
server.js Show resolved Hide resolved
src/js/config-1.1.8.js Show resolved Hide resolved
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

Successfully merging this pull request may close these issues.

3 participants