Discourse forums no longer allowing me to log in Topic is solved

[frostknight]

Currently using an unbranded palemoon browser:


Cannot log in, or see the screen correctly https://community.mnt.re

Thus, its probably wise to mention, that some websites using discourse are still problems.

I would very much like to block that "browsehappy.com" bs

Because the creators of discourse wouldn't needed to make that service even for their own reasons, if they would have just deleted the javascript idea.

Aka, javascript is non-essential as an idea, except by huge corporations.

Meh... what can you do tho.

Feel free to see what I mean there.

[back2themoon]

It works normally here, with the fixes already described in this thread.

Currently using an unbranded palemoon browser:

That could be causing your problem.

(is all that Amiga-related?)

[mmouse]

Hello everyone

Just wanted to add that today I found a forum beginning by discuss., added discuss. in the universal (!) workaround, it did not work, and looking at the code noticed that this particular site used a cdn, so I needed to add also discuss-cdn, like this:

|^discuss\\.|^discuss-cdn\\.

and this forum worked.
So the apparent name of the forum may not always be enough to add a proper fix, looking at the network tab can be useful too to see what are the real URIs.

[frostknight]

It works normally here, with the fixes already described in this thread.

Currently using an unbranded palemoon browser:

That could be causing your problem.

(is all that Amiga-related?)

That depends, does using the latest palemoon web browser but without branding for the usual 64 bit linux, count?

If so, then yes, otherwise no.



Ironically, though, this one does in fact work:

https://support.nitrokey.com/t/attempts ... eable/4954

Do I need to use gecko compatibility or firefox compatibility or native? That might be part of the issue. Not sure though

[andyprough]

That depends, does using the latest palemoon web browser but without branding for the usual 64 bit linux, count?

To be fair, you are using a GNU/Linux distro that's missing a few of the typical features, so you and I have had to disable a few things in your Pale Moon build, including dbus, pulseaudio, alsa, and gconf. The reason we made the browser unbranded was to distinguish it as not being a normal Pale Moon build. Some or all of those missing items on both your GNU/Linux distro and your browser could possibly lead to trouble with the website you are trying to log into.

So it's not the branding or unbranding in your case that is likely causing difficulty with that site, but much more likely it's due to the stuff we had to disable when you and I built that version of Pale Moon for you. If you wanted to switch to using a typical distro like Trisquel, then you could use the official Linux version of Pale Moon and you would probably get a better browsing experience. But as long as you are using Hyperbola, you will have to put up with some sites that probably don't work because of what Hyperbola is missing.

[frostknight]

The reason we made the browser unbranded was to distinguish it as not being a normal Pale Moon build. Some or all of those missing items on both your GNU/Linux distro and your browser could possibly lead to trouble with the website you are trying to log into.

So it's not the branding or unbranding in your case that is likely causing difficulty with that site, but much more likely it's due to the stuff we had to disable when you and I built that version of Pale Moon for you.

I didn't think this was a possibility, good to know. So I assume then, no one else has discourse issues anymore? I am surprised

[andyprough]

I
didn't think this was a possibility, good to know. So I assume then, no one else has discourse issues anymore? I am surprised

I don't know, I've never used discourse forums, could just be a badly built discourse forum. I was just pointing out that if it's failing because of your Pale Moon build it would be because of stuff we disabled so that it could build and run on Hyperbola GNU/Linux, not due to branding files. I don't know of anything in the branding files that would affect performance, and we didn't touch those files, we just disabled the official branding option when we built it.

[purpleleaf]

Today the discourse istance at https://community.e.foundation has stopped working.
the string reported here https://forum.palemoon.org/viewtopic.php?f=70&t=29327&start=60#p237629 worked for me

[purpleleaf]

the string reported here https://forum.palemoon.org/viewtopic.php?f=70&t=29327&start=60#p237629 worked for me

Update: community.e.foundation doesn' work again. Other sites likes Manjaro's forum are still working.

[adoxa]

Code: Select all

[["/discourse|^discuss|^community\\.|^forum\\.|resource\\.dopus\\.com/",["/browser-detect-/",["/.*/g",""]],["/vendor-/",["/(t\\.discourse\\.hoisted|t\\[e\\]|r)(\\?\\?|\\|\\|)=(\\{\\}|\\[\\])/g","$1$2($1=$3)","n??=[]","n||(n=[])"]],["/discourse-/",["e.draft||=t.draft","e.draft||(e.draft=t.draft)","/(t\\.__registry__\\._typeInjections\\.service|[ne]|[fm]\\[e\\])(\\?\\?|\\|\\|)=(\\[\\]|\\{\\})/g","$1$2($1=$3)","(s||=","!s&&(s=","this._details??=","this._details=this._details??","this._similarTopicsMessage||=","this._similarTopicsMessage=this._similarTopicsMessage||","this._applicationElement??=","this._applicationElement=this._applicationElement??"]]]]

[purpleleaf]

@adoxa
many many thanks, it works like a charme

[Daikun]

Can we get an updated script for PM 32.1.1?
EDIT: Never mind.

[Moonchild]

Can we get an updated script for PM 32.1.1?

Would that be necessary? and if so, why?

[Daikun]

Can we get an updated script for PM 32.1.1?

Would that be necessary? and if so, why?

So I can use the Discourse forums with the HTTP Response filter?
EDIT: Never mind. I just used the script that was posted a few days ago.

[moonbat]

So I can use the Discourse forums with the HTTP Response filter?

That depends on the Modify HTTP response extension, not the browser. At any rate, PM is a far more stable platform than Chromezilla browsers where extensions are concerned so unless the extension itself is broken with the new version of the browser (unlikely) there should be no problem.

[back2themoon]

Minor issue in resource.dopus.com. It should be possible to paste images from the clipboard into a reply, but the image never appears. To be honest, I don't know if this ever worked before in PM, in this or other Discourse fora forums.

Don't know if it's relevant, but noticed the URL varies between .com/* .com/t/* .com/c/* depending on the section visited.

[purpleleaf]

community.e.foundation and forum.manjaro.org don't work again
checked some other instances and them don't work also.

[UCyborg]

Web browser must support aspect-ratio CSS property to pass Discourse's supported web browser check.

browser-detect.js

[Moonchild]

Web browser must support aspect-ratio CSS property to pass Discourse's supported web browser check.

browser-detect.js

Already known.
See earlier in this topic

[Tharthan]

The Discourse forums that I am trying to access are still working just fine for me, and the ones that purpleleaf mentions seem to be coming up normally on my end.

So the workaround still seems to be working just fine, at least for me.