This thread may help. Emoji display issues
v30 bugs Topic is solved
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
- somdcomputerguy
- Lunatic
- Posts: 384
- Joined: 2014-02-23, 17:25
- Location: Greenbrier County, West Virginia
- Contact:
Re: v30 bugs
-bruce /* somdcomputerguy.com */
'If you change the way you look at things, the things you look at change.'
'If you change the way you look at things, the things you look at change.'
Re: v30 bugs
These are not emojis, but tiny cashed pictures.
I've just realized the same bad behavior occur at v29.4.5 too!
v29.4.4 was working fine.
I've just realized the same bad behavior occur at v29.4.5 too!
v29.4.4 was working fine.
- back2themoon
- Moon Magic practitioner
- Posts: 2409
- Joined: 2012-08-19, 20:32
Re: v30 bugs
Is that with a clean profile, or did you directly downgrade from v30?
Safe Mode / clean profile info: Help/Restart in Safe Mode
Information to include when asking for support - How to apply user agent overrides
How to auto-fill passwords
Windows 10 Pro x64
Information to include when asking for support - How to apply user agent overrides
How to auto-fill passwords
Windows 10 Pro x64
Re: v30 bugs
Yes, You are right, downgraded.downgrade from v30?
I assumed a 29.4.5 installer would auto-recognised it was downgraded and would clean the problematic values.
I was too optimistic.
Re: v30 bugs
I'd still test it against 29.4.4 to be sure. Just get the portable version and copy your profile to it. If the profile is the problem, you'll still have the issue with the old version. Also try a clean profile with 29.4.5 to confirm.
Re: v30 bugs
@SzakiLaci
Downgrading a browser (no matter which one) is always a bad idea, especially in case of milestone releases like in this case (29 <-> 30).
If you have an old profile of 29.4.* you can upgrade without any problem to 29.4.5 otherwise best thing is to start with a fresh profile.
Downgrading a browser (no matter which one) is always a bad idea, especially in case of milestone releases like in this case (29 <-> 30).
If you have an old profile of 29.4.* you can upgrade without any problem to 29.4.5 otherwise best thing is to start with a fresh profile.
Re: v30 bugs
The trouble is, especially if one is using a build with the updater in it, but the same principle applies when one is using a (Linux) distribution package, that it is easy for an upgrade to be installed in your system without fully being aware of it. It is very easy to click on the "Update now" button when the former identifies that there is a new version available.
Is it feasible for the PM start-up process to recognise that it is updating a profile used with a previous version and to ask the user whether they wish to backup their profile before the main executable makes any changes to it - obviously once it has gotten a go ahead to go ahead either after allowing or even doing a backup, then it can mark the profile with it's version which could give a heads up to any older version (that is aware of this suggested feature) that one is using a downgraded profile and all bets on stability and functionality are now off the table?
If I do not downgrade the profiles on those installations where I am using a 30.x PM to avoid tainting the profiles, will those update correctly to 31.x when it is eventually released - or am I stuffed?
Is it feasible for the PM start-up process to recognise that it is updating a profile used with a previous version and to ask the user whether they wish to backup their profile before the main executable makes any changes to it - obviously once it has gotten a go ahead to go ahead either after allowing or even doing a backup, then it can mark the profile with it's version which could give a heads up to any older version (that is aware of this suggested feature) that one is using a downgraded profile and all bets on stability and functionality are now off the table?
If I do not downgrade the profiles on those installations where I am using a 30.x PM to avoid tainting the profiles, will those update correctly to 31.x when it is eventually released - or am I stuffed?
Re: v30 bugs
Please see my announcement update about profile compatibility.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: v30 bugs
I confirm the cache issues and possibility for flawless transition from 30.0.1 to 29.4.6 keeping at least bookmarks (manual backup/restore), layout (xulstore.json), google search (searchplugins\google.xml), saved passwords (key4.db + logins.json), last session (sessionstore.js), 29.* compatible extensions (extension-data\ + extensions\ + extensions.ini + extensions.json) and extension / site JS saved data (webappstore.sqlite). Had to reinstall Foxyproxy though (keeping foxyproxy.xml was not enough).
Did a fresh install and replaced all those files. Did not try to transfer cookies (cookies.sqlite), history/active bookmarks (places.sqlite) and about:config (prefs.js). I guess it is unsafe to transfer prefs anyways.
Did a fresh install and replaced all those files. Did not try to transfer cookies (cookies.sqlite), history/active bookmarks (places.sqlite) and about:config (prefs.js). I guess it is unsafe to transfer prefs anyways.
Re: v30 bugs
I just wanted to report back:
Since v31 everything is smooth
Thank you for the fix!
Since v31 everything is smooth
Thank you for the fix!