Recommended Posts

4 minutes ago, Gary7 said:

All I know is that I was told to clear your cookies, cache, logout restart before you report any problem. People want to argue, go right ahead. Not you LM.

What exactly do you think in cookies and cache controls these functions?

9 minutes ago, Gary7 said:

All I know is that I was told to clear your cookies, cache, logout restart before you report any problem. People want to argue, go right ahead. Not you LM.

 OK -- I ran CCleaner, which clears out Cookies, blew my nose, and Restarted.

 

Quote works now but Like this does not. :/

4 minutes ago, Gary7 said:

Ask Dave Legg it is in his signature/

 

Clear your cache and cookies and try again before posting any bugs!

The equivalent of trying safe mode. It's good for narrowing down basic issues but they bungled the https implementation. It is causing problems and not just here. 

1 minute ago, adrynalyne said:

The equivalent of trying safe mode. It's good for narrowing down basic issues but they bungled the https implementation. It is causing problems and not just here. 

You asked a question, I answered it. You want any more info talk to Dave. I have had it for today.

5 minutes ago, exotoxic said:

It is because the like button link does not use HTTPS.

Thank you. I keep saying this is not a cache or cookies thing.

root_library.js.90c2923….js.gz:2 Mixed Content: The page at 'https://www.neowin.net/forum/topic/1309670-likes-disabled/?page=2' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'https://www.neowin.net/forum/topic/1309670-likes-disabled/?do=repComment&com…=589abbf57eecbef4d4e9676372faadb4&csrfKey=589abbf57eecbef4d4e9676372faadb4'. This request has been blocked; the content must be served over HTTPS.send @ root_library.js.90c2923….js.gz:2

root_library.js.90c2923….js.gz:2 XMLHttpRequest cannot load https://www.neowin.net/forum/topic/1309670-likes-disabled/?do=repComment&com…=589abbf57eecbef4d4e9676372faadb4&csrfKey=589abbf57eecbef4d4e9676372faadb4. Failed to start loading.send @ root_library.js.90c2923….js.gz:2

root_front.js.9f4e731….js.gz:155 Uncaught TypeError: Cannot read property 'error' of undefined

 

43 minutes ago, LimeMaster said:

Not the best browser to test it with. I remember somebody complaining about certain bits of Neowin being broken in Edge.

 

Could be. With very little information, it's hard to tell.

The developer console tells the problem: they have hardcoded links to http and are enforcing https. That does not work.

11 minutes ago, Gary7 said:

You asked a question, I answered it. You want any more info talk to Dave. I have had it for today.

I don't need information. I know what the problem is.

its mixed content problem alright, theres temporary workaround using RegEx plugin to filter/modify the html/js/css text

FIND = "https://www.neowin.net/forum/topic/\0/\?do=repComment"
REPLACE = "https://www.neowin.net/forum/topic/\0/\?do=repComment"

Alternatively if the browser support it, there should be option in its configs to unblock mixed content for https session.

(IE up to ver 8 would actually prompt/warn you about this, if you sets so in the options)

1 hour ago, Torolol said:

its mixed content problem alright, theres temporary workaround using RegEx plugin to filter/modify the html/js/css text


FIND = "https://www.neowin.net/forum/topic/\0/\?do=repComment"
REPLACE = "https://www.neowin.net/forum/topic/\0/\?do=repComment"

 

fascinating /..... but what do I do with that ?

4 hours ago, adrynalyne said:

The equivalent of trying safe mode. It's good for narrowing down basic issues but they bungled the https implementation. It is causing problems and not just here. 

We didn't bungle anything, we implemented that ON THE FRONT PAGE, as we said in the announcement topic. Users have always been able to use https with the forums if they wanted to, but it's not yet officially supported, for exactly this reason, we haven't been through and checked that everything works fully with https yet.

 

For the mean time, just revert back to http for the forums, and everything will run fine.

3 hours ago, Hum said:

I was not able to Dave. If I tried using http it would jump to https, every time.

Ok, I'll sort that when I get a moment later on. For the mean time, things like Likes etc should now be resolved

9 hours ago, TAZMINATOR said:

You didn't call or summon him, though.. 

 

Because you missed something. 

 

Not tell you what it is.

 

 

:rolleyes: 

No I did not.:)

 

 

 

 

7 hours ago, DaveLegg said:

We didn't bungle anything, we implemented that ON THE FRONT PAGE, as we said in the announcement topic. Users have always been able to use https with the forums if they wanted to, but it's not yet officially supported, for exactly this reason, we haven't been through and checked that everything works fully with https yet.

 

For the mean time, just revert back to http for the forums, and everything will run fine.

You enforced it on the entire domain. Did you think forums didn't fall under that? Come on....everyone makes mistakes. No point in denying it. Enforcing it on the entire domain enforced it on the forums too. 

3 minutes ago, adrynalyne said:

You enforced it on the entire domain. Did you think forums didn't fall under that? Come on....everyone makes mistakes. No point in denying it. Enforcing it on the entire domain enforced it on the forums too. 

It is for me.

4 hours ago, DaveLegg said:

Ok, I'll sort that when I get a moment later on. For the mean time, things like Likes etc should now be resolved

OK dAVE !  tHANK YOU !

 

I'm able to Like again -- I really really can Like you ! :D

  • Like 2
This topic is now closed to further replies.