I understand that CookieMonster will do this (as will most other Cookie manager add-ons), and I fully appreciate and thank you for posting about the CookieMonster add-on and have previously said that in my opinion it “is a very good add-on”.
I was only pointing out that in the case of the FF browser this same function is already available to the user, along with a lot of other webpage info as well. And of course with this in mind I only meant to say that Cookie manager add-ons can be an absolute necessity for many browsers but on the other hand it is in fact not really that necessary in the case of the FF browser for this very reason.
Just to say that I can also not login to the forum with Palemoon - all I get is a blank page with an exclamation mark in an orange triangle and my addressbar is showing https://id.avast.com/?target=https%3A%2F%2Fforum.avast.com#login
I am posting this in Opera 12. You are not alone.
Thanks for your post Dave, it is up to Avast to want to make the effort to support the Pale Moon browser addressed here in this Avast topic: Cannot sign in here with the Pale Moon Browser
All Pale Moon users are getting this same page attempting to login to Avast.
For some users (including myself) it has been discovered that Avast cookies were causing a problem using any browser to login to Avast, by clearing the Avast cookies this solved the problem for all browsers with the exception of Pale Moon of which an issue remains that consists of more than an Avast cookie related problem in this case.
This problem for Pale Moon users logging into Avast started getting reported as of Aug 09, 2015 as evidenced by a Pale Moon forum topic on this issue.
In reference to my post above this problem with Pale Moon users not being able to login to Avast was first reported in the Pale Moon forum around the same time that appears to coincided with the date of this comment referencing a change Avast made as we see here in this Avast forum post: my.avast.com and forum.avast.com are the same now . I would add that Pale Moon has reportedly done everything possible regarding this Avast login incompatibility issue with Pale Moon.
So I’d have to conclude that this issue all comes down to just the procedure used by Avast to login to Avast, users can still read the forum without logging in. Of course this login issue includes logging into the “myavast” account as well since as pointed out above these logins have merged and as I pointed out above you might note as of the same date that users started reporting this login issue for Pale Moon users.
Clearly this issue is on Avast to fix if they really wanted to make the effort… I can disable Windows User Account Control (UAC) and will then get a hang sometimes instead of the typical results that has been posted but of course the login is simply failing in another way and of course it makes no sense to remove recommended security in the first place just because Avast fails to remain compatible with Pale Moon.
It is sad to see this so often pervasive corporate attitude that emerges as a result of organizations in general becoming so expansive that they see no need to make the effort to accommodate as contrast to what is typically the case with smaller organizations.
We should all be able to agree here in this Avast forum that it is not at all that much to ask Avast to have the comity to simply make the effort to support Pale Moon browser users. ???
"it is not at all that much to ask Avast to have the comity to simply make the effort to support Pale Moon browser users. "
Eventually. Right now I’m sure they are concentrating on Avast 2016. (Short and sweet.)
It all depends upon what “eventually” is… I’d like to think you’re correct, but I’m frankly not holding my breath ;)… I’ll check back w/u in another 90 days to discuss once again (Short and sweet)
Thanks for your helpful reply. I appreciate that Avast are working on their new products but it would be nice to have some acknowledgement that they are aware of this issue and a timetable as to when it will be fixed. Forum login issues affect us whatever version of the software we are using.
Thanks davews for doing this… That said, I’m personally not very hopeful. If you take a look at the Pale Moon thread on this topic (the link you previously posted) you’ll see why.
It is surmised that the new combined login that Avast has released is likely coded using Asynchronous Programming with the abstraction called “promises” (or sometimes deferreds) which is not really a good idea for a login interface actually (refer to link for details on this approach) and I would add that in so doing may very well be neglecting to check for their existence in browsers. It is pointed out in the Pale Moon topic that Avast may have actually taken the easy approach and used quote “… a cookie-cutter library” for their new “single sign-on” login procedure and because of this will most likely have “no way to troubleshoot or fix it as a result”. It is advised that Avast should be using “… any of the server-side shims available” which would go a long way toward helping improve browser compatibility.
I’m simply not convinced that Avast is going to really care enough to make the effort to do it right in order to fix the issue. I’m inclined to think that this problem ticket will simply not reach the level of priority at which point Avast would address this issue to be perfectly honest. I’d like to think otherwise, but I’m afraid this is perhaps just the way Avast does things.
But we’ll see, I told bob3160 that I would touch bases with him in another 90 days and see where we stand at that point. I’d certainly like to be wrong and instead be pleasantly surprised to find out bob3160 is correct in the end, but I’m afraid I’ll instead be asking bob3160 to come up with another excuse and another dead-line date.
Let’s get something straight, asking Avast, might get you help on this. (You’ve already done that.) I only offered you a logical explanation.
I’m an Avast user just like you so I don’t make your, my, or any one else’s wishes a reality.
Please, no more novels.
Well 6 days after I submitted my ticket I had a reply - he suggested I cleared my cookies and browser history. I have replied back saying we know that is not the problem and politely suggested they download a copy of Palemoon and replicate the problem. I am not hopeful I will get anywhere…
Palemoon project is an optimized compile of Firefox code from the get-go, and as such uses SSE2. Its not an OS dependency as far as I know, and at one time it was common to run XP on newer hardware to keep legacy applications alive or even downgrade from Vista If your XP box was still an old CPU, Palemoon simply wasn’t the right fit of browser for your needs.
To compare, Google Crome browser dropped support for non-SSE2 CPUs back in release 35 but still supports XP for the current version.
So as time marches on, Palemoon performance gains might not be as significant as they used to be over other browsers, but those of us using it for so long are reluctant to change just for one website, so fixing this Avast login issue would be great.
Opera 12.16 works fine here (virtually identical to 12.17), but I stay permanently logged in so will try and not log out… As said, Opera 12 is the last of the old Presto series before they moved to a Chrome lookalike. I eventually moved to Palemoon which is now my default browser, a branch of Firefox which will never have the Australis look.
Fingers crossed that they will come up with a solution.
(Short and sweet)