-
Notifications
You must be signed in to change notification settings - Fork 3
Page hangs on load after being logged in. #2
Comments
As i am not using Codiad anymore i need to install it and need to understand, what they changed in their application. I'll give it a try on the weekend, maybe it's just a little change in initialization. |
Yes, I got one error: |
Sorry, hadn't much time the last days. Can you provide further information (browser, operating system, conflicting plugins). |
Even if everything else is disabled, it does not work and the error appeared. Tryed with Windows 10, Debian 8, Kubuntu with the google chrome 48.0.2564.109 (64-bit) |
That is bad.
|
Ok seems Content isn't an empty string. |
Ok, when I close all Files, install the Plugin and reopen the files the error no longer appears. But when I refresh the Page, the same error appears. It looks like that if content at startup is not empty, the error occurs |
What do you mean with "refresh the Page"? |
I mean, that I reopen the Page in a new Browser-Session.
Yes
Google Chrome 48.0.2564.109 (64-bit)
Yes it may rests against the web server (software)? |
Hm. So it works when you reload the page using CTRL+F5? |
No, I could better explain it that way. It does not work on any way. |
Ok, can you ensure you have the latest codiad version installed (v2.7.2)? |
Yes |
Ok, as seen here, the getContent method returns nothing if there is no "active" editor: This means my further code fails. |
…sts, recompiled with coffeescript 1.10.0
Ok, tried to fix it, but i can still not reproduce your error. |
@oxi: does it work? |
Sorry for the delay. But a new error at the console:
|
I am wondering, why you havn't an active editor item. |
Do you use multiple editor panes? |
@oxi |
Ok, I will test this tomorrow. |
Ok, I don't use multiple editor panes. But the first Error is now ok. But The Error "init.coffee:61 Uncaught TypeError: Cannot read property 'getSession' of null" is still here. |
New version 0.1.3 is released, i really hope i got all potential issues. Please give me some feedback if it works or not, so i can hopefully close this ticket this time. :-) |
Ok, now it is fixed! Thank you very much! |
Best news today. :-) |
Codiad/Codiad#897
The text was updated successfully, but these errors were encountered: