World: r3wp
[!CureCode] web-based bugtracking tool
older | first |
Dockimbel 22-Aug-2011 [1272x2] | (make a backup before) |
I have test it locally, it should fix your upgrading issue. | |
Henrik 22-Aug-2011 [1274x3] | ok, that works now. |
now when logging in, I get a "redirection trapped" error, but I can then proceed to the correct URL via a link below the message. | |
hmm.. that was either caused by debug/on or my lastpass plugin | |
Dockimbel 22-Aug-2011 [1277] | Redirection trapped is a debug feature, not an error. If debug mode is activated, it produces a intermediary page for HTTP redirection, you have a chance to examine request and session before the redirection is done. |
Henrik 22-Aug-2011 [1278] | ah, ok. good. |
Dockimbel 22-Aug-2011 [1279] | I have upgraded the install script in v0.9.12 archive to handle the mysql-protocol.r installation. |
Henrik 22-Aug-2011 [1280] | my curecode seems to be running OK now. |
Dockimbel 22-Aug-2011 [1281] | Glad to hear that. :-) |
Ladislav 10-Sep-2011 [1282] | Does the CureCode currently work for you? |
Henrik 10-Sep-2011 [1283] | works for me |
Ladislav 10-Sep-2011 [1284x2] | Strange, I am getting "page unavailable" |
Aha, now it finally worked | |
Ladislav 9-Oct-2011 [1286] | This is annoying. I do not know why, but in Chrome, I am de facto unable to log in to CC. Do you have any idea, what may be the culprit? |
GrahamC 9-Oct-2011 [1287] | Works for me using Chrome |
Ladislav 9-Oct-2011 [1288] | I usually have to wait, until Chrome tells the page is currently unavailable |
GrahamC 9-Oct-2011 [1289] | and a different browser is okay? |
Ladislav 9-Oct-2011 [1290] | In IE it seems to work in a snappy way |
Henrik 9-Oct-2011 [1291] | I don't have issues in Chrome. |
Dockimbel 9-Oct-2011 [1292] | It works from here with Chrome too. It might be an internal Chrome prefetching or DNS caching issue. |
Ladislav 9-Oct-2011 [1293] | internal Chrome prefetching - looks more like postfetching taking into account how sluggish it is |
james_nak 22-Oct-2011 [1294] | Way back when I reported that I was getting an error with the head.rsp file. Well, after being on a fix it binge, I decided to take a look at what was going on. It turns out that there were multiple instances of Cheyenne running. I am not referring to the multiple instances on normally sees but from another build altogether. I still don't know where that is getting launched from (I checked the startup and all the services etc in msconfig) but by kludging it and renaming the build I didn't want, it fixed the issue. |
Dockimbel 11-Nov-2011 [1295] | The domain issue.cc has expired since yesterday and is no more reachable. It seems I've missed something when transferring it to another registrar, so it might be unavailable for one or two more days. |
Dockimbel 14-Nov-2011 [1296] | Domain issue.cc is up again. |
Ladislav 14-Nov-2011 [1297] | Perfect, doc. |
Dockimbel 22-Dec-2011 [1298:last] | Domain issue.cc is down again, it seems that the configuration wasn't completed after the transfert. I've fixed the config options so it should be back online in 24 hours max. |
older | first |