Basilisk 2023.11.05 Released!

[Basilisk-Dev]

Basilisk 2023.11.05 has been released!

This release uses the same UXP platform version as Pale Moon 32.5.0.

The autoupdate service does not currently support FreeBSD, aarch64 Linux, and macOS builds so a manual update is required on these operating systems.

See the release notes for more information.

See the downloads page to download the update.

[TTraveler]

.

Thank you..........¡Es profundamente apreciado!

..

[nord1]

Much thanks, an impressive release.

[uwethomas]

Hi there, and please pardon me bothering.

Still using 2022.01.27 as I am simply too silly to manually transfer all my files and settings (incl. the last session) profile into the new version.

Is there any intention from your side to integrate a tool in a new version which automatically adapts my older profile into the new one?

It would be so helpful and welcome ^^

Thank you and best wishes


Uwe

[Raava]

@Basilisk-Dev

I successfully updated to 2023.11.05 aka

Code: Select all

rava@rava1:~$ basilisk --version
Basilisk-Dev Basilisk 52.9.2023.11.05

but I made a huge mistake: I logged into one web email and pressed "save password" (or whatever the exact phrasing is) by mistake.
For now I reverted that error in the running system by about:preferences#security and going to sub-section Saved Logins and removed that login/that password.

But I use a Slackware based live system and created a settings module for basilisk that still stores the erroneously saved login, so I want to know which files exactly I have to alter to have all logins and passwords removed from ~/.basilisk-dev/basilisk/RANDOM.default
I want to keep older versions of my settings modules in case some mishap happens and my settings got messed up: better start at a point where my add-ons and my dark mode is already enabled and only the most recent change or add-on must be re-done than start at zero; therefore my question about which files to only alter to have the saved logins removed.

Also, could I set the "do not save any logins" via its settings, and if so, how?


Update
Just realized: I started basilisk from a non-root terminal to see any possible errors displayed and I get this message repeatedly:

Code: Select all

addons.update-checker	WARN	HTTP Request failed for an unknown reason

[Raava]

One thing is quite annoying.

I can log into https://forum.palemoon.org just fine.When I want to log into another phpbb based forum - https://forum.porteus.org - no login is happening, I also get no error message whatsoever.

This is what it looks life after I gave my username and correct password at forum.palemoon.org

basilisk-palemoon.png

and this is after I gave my username and correct password at forum.porteus.org

basilisk-porteus.png

I looked into Developer / Web Console / Network and found one initial status 302 and a lot of 200, but no errors.

I looked into Developer / Debugger and found some js listed, and this one:
https://forum.porteus.org/assets/javasc ... ersion=332

basilisk-porteus2.png

Is this the reason the login fails?

Update
After I stopped blacklisting that JS the login works. But why was that script blacklisted to begin with?