Error Encountered: URIError: URI malformed

Hi @apollosk,

Can you share domain so we can take a look at your site? I haven’t seen this before, so not sure what could cause it. Maybe there’s something non-standard in the domain or something like that?

@rogierlankhorst the domain is ssnm (dot) org (dot) mk

@rogierlankhorst did you have the change to take a look? Any update?

@apollosk sorry for the late response! I did some digging in the code, and while I can’t reproduce the issue, it’s probably something to do with the language encoding/decoding.

I’ve created a version which does some better error handling, and logs the error if it encounters any:
https://github.com/Burst-Statistics/burst/tree/decodeURI-try-catch

Can you try the following:

– deactivate your current plugin
– download this version as a zip using the green button
– Go to plugins, add new, upload, and upload and install this zip file, and activate it.

Then, try the dashboard again. If you see any errors in the console, please post them here.

Hi! I did everything as you requested. Here is the error I see when I go Dashboard > Statistics:

ReferenceError: url is not defined
Stack trace:
at https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:91:30
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at J (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:137:23)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at Kt (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:51888)
at https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:6136
at div
at div
at div
at u (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.8c0c46eab51ef5c68fdd.js?ver=8c0c46eab51ef5c68fdd:1:163)
at l (https://example.com/wp-content/plugins/burst-statistics/settings/build/204.1096da6f01bf28d1ba1a.js:1:4497)
at X (https://example.com/wp-content/plugins/burst-statistics/settings/build/204.1096da6f01bf28d1ba1a.js:1:24960)
at div
at te (https://example.com/wp-content/plugins/burst-statistics/settings/build/204.1096da6f01bf28d1ba1a.js:1:30746)
at u (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.8c0c46eab51ef5c68fdd.js?ver=8c0c46eab51ef5c68fdd:1:163)
at l (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.8c0c46eab51ef5c68fdd.js?ver=8c0c46eab51ef5c68fdd:1:55604)
at div
at u (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.8c0c46eab51ef5c68fdd.js?ver=8c0c46eab51ef5c68fdd:1:24001)

@apollosk I’m sorry, I’ve made a stupid typo… Instead of the variable ‘uri’, I put ‘url’ in the log. So the error you see is actually one of my own making.

I’ve fixed this now, can you try again?

I have used the same download URL and after installation I still get the same error:

ReferenceError: url is not defined
Stack trace:
at https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:91:30
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at J (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:137:23)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at div
at x (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:53844)
at Kt (https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:51888)
at https://example.com/wp-content/plugins/burst-statistics/settings/build/856.a24ce392b7ce9424a145.js:383:6136
at div
at div
at div
at u (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.f83d1a25b74d93dc0090.js?ver=f83d1a25b74d93dc0090:1:163)
at l (https://example.com/wp-content/plugins/burst-statistics/settings/build/204.1096da6f01bf28d1ba1a.js:1:4497)
at X (https://example.com/wp-content/plugins/burst-statistics/settings/build/204.1096da6f01bf28d1ba1a.js:1:24960)
at div
at te (https://example.com/wp-content/plugins/burst-statistics/settings/build/204.1096da6f01bf28d1ba1a.js:1:30746)
at u (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.f83d1a25b74d93dc0090.js?ver=f83d1a25b74d93dc0090:1:163)
at l (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.f83d1a25b74d93dc0090.js?ver=f83d1a25b74d93dc0090:1:55602)
at div
at u (https://example.com/wp-content/plugins/burst-statistics/settings/build/index.f83d1a25b74d93dc0090.js?ver=f83d1a25b74d93dc0090:1:23999)

@apollosk I made another adjustment, can you try again?

Sorry for the slow progress, it’s a bit like debugging blindfolded, as I don’t have the issue locally. Hope this one gives us a bit more insight!
https://github.com/Burst-Statistics/burst/tree/decodeURI-try-catch

Hi @rogierlankhorst Thank you for the update.

I can confirm that your latest adjustment resolved the issue. Now, the Pages section of the Statistics page is displayed properly and there is no error. See printscreen: https://postimg.cc/dkVTdVRM

Thank you for your time and effort. Cheers!

Great! We’ll merge this fix in one of the coming updates, please check the changelog before updating!