Network Error Obnoxious on Chrome

63 views
Skip to first unread message

Kevin Kleinfelter

unread,
May 3, 2020, 4:42:15 PM5/3/20
to TiddlyWiki
When network connectivity is down, the node.js edition of TW works nicely and as expected with Firefox.  With Chrome, the minute I open a tiddler, it goes nuts with the gold Network Error message.  If I close the message, it comes right back.  This makes the node.js TW unusable offline with Chrome.

How can I get TW to show the Network Error zero or one times when using Chrome.

Using 5.1.22.
TIA


Arlen Beiler

unread,
May 3, 2020, 5:18:42 PM5/3/20
to TiddlyWiki
This is quite possibly related to your other post. Please try creating a new empty datafolder and only copy the tiddlywiki.info file from your current data folder to get a clean one. Then try testing everything again. 

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ec4f91c3-bcc8-4548-90df-1cb0b1cf71ea%40googlegroups.com.

Kevin Kleinfelter

unread,
May 3, 2020, 6:54:46 PM5/3/20
to TiddlyWiki
That's a good suggestion, but no joy.

I removed and re-installed tiddlywiki with npm.  I created a new wiki, so I've got a clean tiddlywiki.info, no content and no plugins.  If I open or close a tiddler from an already-open wiki while wifi is down, the status icon turns red and start spinning its arrows, and Network Error opens (or counts upward) at the rate of about 1 per 5 seconds.  I've tested with all extensions disabled too.  Chrome version is 81.0.4044.129.

Happens with Safari and Firefox.  (I was mistaken when I said it did not happen with Firefox in my earlier post.)

Pretty much makes node.js TW unusable in offline mode for me. More importantly, it gets me in trouble with my wife!  ;-)

Arlen Beiler

unread,
May 3, 2020, 7:50:15 PM5/3/20
to TiddlyWiki
What is the version number in the control panel. If you click the gear icon it will open the control panel, and the main tab should list the version. 

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.

Kevin Kleinfelter

unread,
May 3, 2020, 7:50:51 PM5/3/20
to TiddlyWiki
As a quick hack, I edited tiddlywiki/core/modules/syncer.js and made Syncer.prototype.displayError look like this:

Syncer.prototype.displayError = function(msg,err) {
    if(err === ($tw.language.getString("Error/XMLHttpRequest") + ": 0")) {
        //this.loggerConnection.alert($tw.language.getString("Error/NetworkErrorAlert"));
        this.logger.log(msg + ":",err);
    } else {
        this.logger.alert(msg + ":",err);
    }
};


Kevin Kleinfelter

unread,
May 3, 2020, 7:59:15 PM5/3/20
to tiddl...@googlegroups.com
I'm running with 5.1.22 now.  As I mentioned earlier, I deleted 5.1.21 and simply installed 5.1.22, so it is a pure 5.1.22.  (I backed up the 5.1.21, to be able to pursue my other question about the failed upgrade.)

You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/0zoa06k0OTw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSoY27yh%2BQ44313AtHr7Z48ivD5yD5b9xg57xSpGqOZLg%40mail.gmail.com.

Arlen Beiler

unread,
May 3, 2020, 8:15:59 PM5/3/20
to TiddlyWiki
Ok, sounds good.

In thinking this over, I think the best idea would be for you to open an issue on GitHub for this. If you don't have a GitHub account and don't feel like creating one I could open it as well, but feel free to do so.


Arlen

Kevin Kleinfelter

unread,
May 4, 2020, 9:33:36 AM5/4/20
to TiddlyWiki
submitted via github
Reply all
Reply to author
Forward
0 new messages