Quote from: Mercedes.li on May 22, 2021, 03:00:00 AM

hi.dev. I tried to configure eIquidus on windows 10 OS.

Just a note that while it may possibly work under Windows 10, the project has been tested and configured to run under ubuntu/debian linux and no efforts have been made yet to make the source compatible with other operating systems, so you may have troubles getting everything working because of this.

Quote from: Mercedes.li on May 22, 2021, 08:18:04 AM

After patient modification, my explorer can work. Now, I still receive the following error, but my web page is displayed well. Is it related to the fact that I haven't fully synchronized the blockchain?

Code:

_http_outgoing.js:561
throw new ERR_HTTP_HEADERS_SENT('set');
^

Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
at ServerResponse.setHeader (_http_outgoing.js:561:11)
at ServerResponse.header (H:\eiquidus-1.99.0\node_modules\express\lib\response.js:771:10)
at ServerResponse.json (H:\eiquidus-1.99.0\node_modules\express\lib\response.js:264:10)
at ServerResponse.send (H:\eiquidus-1.99.0\node_modules\express\lib\response.js:158:21)
at H:\eiquidus-1.99.0\app.js:430:23
at H:\eiquidus-1.99.0\lib\explorer.js:287:20
at H:\eiquidus-1.99.0\lib\explorer.js:26:14
at ClientRequest.<anonymous> (H:\eiquidus-1.99.0\lib\node.js:29:5)
at ClientRequest.emit (events.js:388:22)
at Socket.socketErrorListener (_http_client.js:475:9)
at Socket.emit (events.js:376:20)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
code: 'ERR_HTTP_HEADERS_SENT'
}
Cluster restarting...

The ERR_HTTP_HEADERS_SENT error typically means your wallet daemon is not running or else you have not properly configured your wallet connection in the settings.json file.

Quote from: Mercedes.li on May 22, 2021, 08:18:04 AM

This is my package.json ：

Code:

{
"name": "explorer",
"version": "1.99.0",
"private": true,
"scripts": {
"start": "npm run sass:compile && node --stack-size=100 ./bin/cluster",
"stop": "kill -2 $(cat tmp/cluster.pid)",
"test": "node ./node_modules/jasmine/bin/jasmine.js test/*Spec.js",
"sass:compile": "sh './scripts/sass_theme_reader.sh' './node_modules/.bin/sass --no-source-map --style=compressed' './public/css/style.scss' './public/css/style.min.css'"
},
"dependencies": {
"express": ">=4.17.1",
"async": "^3.1.0",
"intl": "^1.2.5",
"serve-favicon": "^2.5.0",
"morgan": ">=1.9.1",
"cookie-parser": "~1.4.4",
"body-parser": "~1.19.0",
"debug": ">=4.1.1",
"pug": "~3.0.0",
"postman-request": "2.88.1-postman.27",
"jsonminify": "0.4.1",
"jstransformer-markdown-it": "^2.1.0",
"mongodb": "3.6.3",
"mongoose": "5.11.4",
"qr-image": "~3.2.0",
"sass": "1.30.0",
"json": "10.0.0",
"strip-json-comments-cli": "1.0.1",
"bad-words": "3.0.4"
},
"devDependencies": {
"jasmine": "~3.6.3"
}
}

Have you made custom changes to the package.json file? Typically no changes are necessary in this file. It also seems that either you removed a lot of the newer scripts or else you are running an older version of the explorer. Are you sure that you cloned the newest changes from https://github.com/team-exor/eiquidus? It seems you are a few months behind in regards to updates. Maybe try a git pull and double-check that you are cloning/forking from the official repo: https://github.com/team-exor/eiquidus

Quote from: Mercedes.li on May 23, 2021, 12:15:08 PM

hi.sir. I followed the tutorial to complete the browser configuration, this is a good project! Now, I encountered the following difficulties:
1 My page zoom is different from "https://explorer.exor.io/", my upper left LOGO is very close to the left side of the window;
2 My search box is different from "https://explorer.exor.io/", it is very short, and the search button is below it instead of on the right.
3 On the TOP100 page, the percentage color is not displayed under the "Wealth Distribution" item, but the color is displayed in the pie chart below, but the ranking of the entire TOP100 is displayed correctly.

Any answers are appreciated.

1) Can you post a screenshot to demonstrate the zoom issue you are referring to? Or else can you provide a link to a test explorer where you are encountering this issue? It's difficult to say what could be wrong without being able to see it
2) There are two different search position options that you can find in the settings.json file. Lookup the page_header.panels.search setting and change the position option to show the search box inside the page header or below it.
3) Once again, can you post a screenshot or provide a link to your explorer that is having this color issue so I can see what it looks like?