X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

My browser history doesn't show yesterday's, last week's history etc. HELP PLEASE!!

Kuphostiwe

I LOVE portable firefox and it's the only browser I ever use. Today, something happened and I am desperate to get help on this. Normally when the browser crashes, I reopen and hit "restore previous session" and I also open another window that may have had 5-6 tabs (it's normal for me to have 5-6 tabs in two diff windows). Today, I opened an older firedox version by mistake and now I can't get back to the 15 or so tabs I had originally! Worse yet, when I look at browser history, I see only two options: Today's browser history (which contains the single home page tab!) and "older than 6 months option" which is not what I want. I really need to see my browser history from the last couple of weeks! What went wrong when firefox never let me down before. I am freaking out here, help please!!

I am on a Windows 7 machine. My question is relevant to firefox portable version 37.01

I LOVE portable firefox and it's the only browser I ever use. Today, something happened and I am desperate to get help on this. Normally when the browser crashes, I reopen and hit "restore previous session" and I also open another window that may have had 5-6 tabs (it's normal for me to have 5-6 tabs in two diff windows). Today, I opened an older firedox version by mistake and now I can't get back to the 15 or so tabs I had originally! Worse yet, when I look at browser history, I see only two options: Today's browser history (which contains the single home page tab!) and "older than 6 months option" which is not what I want. I really need to see my browser history from the last couple of weeks! What went wrong when firefox never let me down before. I am freaking out here, help please!! I am on a Windows 7 machine. My question is relevant to firefox portable version 37.01

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Adobe PDF Plug-In For Firefox and Netscape 11.0.07
  • Google Update
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • The plug-in allows you to open and edit files using Microsoft Office applications
  • Office Authorization plug-in for NPAPI browsers
  • Shockwave Flash 16.0 r0
  • Adobe Shockwave for Director Netscape plug-in, version 12.1
  • 5.1.31010.0

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0

Eminye Imininingwane

jscher2000
  • Top 10 Contributor
8837 izisombululo 72222 izimpendulo
Kuphostiwe

Unless you changed the configuration, each copy of Portable Firefox has its own settings folder. You need to exit out of any other Firefox and open the one you used before.

Unless you changed the configuration, each copy of Portable Firefox has its own settings folder. You need to exit out of any other Firefox and open the one you used before.
cor-el
  • Top 10 Contributor
  • Moderator
17673 izisombululo 159870 izimpendulo
Kuphostiwe

The portable Firefox version comes with its own Firefox profile folder that is located in its installation folder.

  • X:\PortableApps\FirefoxPortable\Data\profile

So if you switch to a different portable installation then you get the profile folder from that version. This is different then the normal release that uses the profiles.ini file.

You would have to locate the Firefox profile folder of that other version if you didn't uninstall it and copy the relevant files to the portable version that you currently use.

You can use this button to go to the currently used Firefox profile folder (I assume that this work in the portable version as well):

The portable Firefox version comes with its own Firefox profile folder that is located in its installation folder. *X:\PortableApps\FirefoxPortable\Data\profile So if you switch to a different portable installation then you get the profile folder from that version. This is different then the normal release that uses the profiles.ini file. You would have to locate the Firefox profile folder of that other version if you didn't uninstall it and copy the relevant files to the portable version that you currently use. *https://support.mozilla.org/kb/Recovering+important+data+from+an+old+profile *http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox You can use this button to go to the currently used Firefox profile folder (I assume that this work in the portable version as well): *Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder) *http://kb.mozillazine.org/Profile_folder_-_Firefox

Umnikazi wombuzo

jscher2000 said

Unless you changed the configuration, each copy of Portable Firefox has its own settings folder. You need to exit out of any other Firefox and open the one you used before.

The tricky part is I had kept an older version of firefox on my desktop from which I launched firefox. Whenever FF asked me to upgrade, I would hit yes and it would somehow end up in the same folder on the desktop. Not sure how it knew but it did. However, it's nested deeper in the folder structure and when I launched this time, I hit the older version without going deeper to find the newest version. So it brought up the old tabs and not the important 12+ tabs! When I close and open the new version (from the same folder), then hit "restore" session, it didn't bring back my new tabs. I figured I would manually search in the history and do it but my history tab shows only today's (which contains just google search page!) and tabs "older than 6 months"!

''jscher2000 [[#answer-717587|said]]'' <blockquote> Unless you changed the configuration, each copy of Portable Firefox has its own settings folder. You need to exit out of any other Firefox and open the one you used before. </blockquote> The tricky part is I had kept an older version of firefox on my desktop from which I launched firefox. Whenever FF asked me to upgrade, I would hit yes and it would somehow end up in the same folder on the desktop. Not sure how it knew but it did. However, it's nested deeper in the folder structure and when I launched this time, I hit the older version without going deeper to find the newest version. So it brought up the old tabs and not the important 12+ tabs! When I close and open the new version (from the same folder), then hit "restore" session, it didn't bring back my new tabs. I figured I would manually search in the history and do it but my history tab shows only today's (which contains just google search page!) and tabs "older than 6 months"!

Umnikazi wombuzo

  • X:\PortableApps\FirefoxPortable\Data\profile

So if you switch to a different portable installation then you get the profile folder from that version. This is different then the normal release that uses the profiles.ini file."

I located the profiles folder (xmkjha1y.default) and in it, there is session-store backups folder with "previous.js" file. This file has the time stamp of exactly when I manually crashed FF. Where can I copy this file to restore that session before I crashed please? Thanks for your help!

*X:\PortableApps\FirefoxPortable\Data\profile So if you switch to a different portable installation then you get the profile folder from that version. This is different then the normal release that uses the profiles.ini file." I located the profiles folder (xmkjha1y.default) and in it, there is session-store backups folder with "previous.js" file. This file has the time stamp of exactly when I manually crashed FF. Where can I copy this file to restore that session before I crashed please? Thanks for your help!

Okulungisiwe ngu rkramadh

cor-el
  • Top 10 Contributor
  • Moderator
17673 izisombululo 159870 izimpendulo
Kuphostiwe

You need to copy this previous.js to sessionstore.js in the current profile folder to have access to that session.

You need to copy this previous.js to sessionstore.js in the current profile folder to have access to that session.

Umnikazi wombuzo

cor-el said

You need to copy this previous.js to sessionstore.js in the current profile folder to have access to that session.

I understand exactly what you are saying. However, I don't have a profile folder for the new version (as odd as that sounds). This is the reason I think: I had a FFportable folder on my desktop for the old version. When I downloaded a newer version, it put that under the same folder like this...FFPortable\app\firefox and that's where the NEW executable is. However, no profile folder. So I put previous.js into ffportable\Data\profile and that didn't work. So I removed it and put it under ffportable\ app\defaultdata\profile and that didn't bring up my session from 4/13 either (used restore previous session option).

I understand at least now how this stuff works. In the future, when I am in the middle of 12 tabls and it asks me to upgrade and I do, how can I prevent it from putting/mixing up new version with the old folder structure? Thanks for all your help, much appreciated!

''cor-el [[#answer-717647|said]]'' <blockquote> You need to copy this previous.js to sessionstore.js in the current profile folder to have access to that session. </blockquote> I understand exactly what you are saying. However, I don't have a profile folder for the new version (as odd as that sounds). This is the reason I think: I had a FFportable folder on my desktop for the old version. When I downloaded a newer version, it put that under the same folder like this...FFPortable\app\firefox and that's where the NEW executable is. However, no profile folder. So I put previous.js into ffportable\Data\profile and that didn't work. So I removed it and put it under ffportable\ app\defaultdata\profile and that didn't bring up my session from 4/13 either (used restore previous session option). I understand at least now how this stuff works. In the future, when I am in the middle of 12 tabls and it asks me to upgrade and I do, how can I prevent it from putting/mixing up new version with the old folder structure? Thanks for all your help, much appreciated!

Umnikazi wombuzo

Additionally, I found this. When I click the old ff executable (from 2/28) and when I click the new executable (from 4/8), and check the version #, they both show 37.0.1. Isn't that odd? Also, executing the old executable (old defined by the date 2/28), and use restore previous session option, I get at least a few of the tabs from a previous session (not quite the 4/13 session that I crashed and lost 12+ tabs). Just sharing all this in case it makes more sense to you :)

Additionally, I found this. When I click the old ff executable (from 2/28) and when I click the new executable (from 4/8), and check the version #, they both show 37.0.1. Isn't that odd? Also, executing the old executable (old defined by the date 2/28), and use restore previous session option, I get at least a few of the tabs from a previous session (not quite the 4/13 session that I crashed and lost 12+ tabs). Just sharing all this in case it makes more sense to you :)
jscher2000
  • Top 10 Contributor
8837 izisombululo 72222 izimpendulo
Kuphostiwe

Not sure either of us knows enough about how Portable Firefox handles updates to answer that.

Do you still have a previous.js from the right time frame?

When you tried to use it, did you:

  • exit out of Firefox completely AND
  • copy previous.js into the main level of the profile folder (not into the sessionstore-backups folder) AND
  • rename the sessionstore.js file to something sessionstore.old AND
  • rename previous.js to sessionstore.js

All steps are necessary, otherwise, the file will be ignored and Firefox will just use the latest sessionstore.js.

Not sure either of us knows enough about how Portable Firefox handles updates to answer that. Do you still have a previous.js from the right time frame? When you tried to use it, did you: * exit out of Firefox completely AND * copy previous.js into the ''main level'' of the profile folder (not into the sessionstore-backups folder) AND * rename the sessionstore.js file to something sessionstore.old AND * rename previous.js to sessionstore.js All steps are necessary, otherwise, the file will be ignored and Firefox will just use the latest sessionstore.js.
cor-el
  • Top 10 Contributor
  • Moderator
17673 izisombululo 159870 izimpendulo
Kuphostiwe

You can only have one Firefox version running at the time. When you would try to start another version then the startup code detects that Firefox in already running and merely opens a new window in the already running Firefox instance. There is a way to run multiple Firefox versions at the same time, each with their own profile folder (it is generally not a good idea to use a profile with different Firefox versions).

You can only have one Firefox version running at the time. When you would try to start another version then the startup code detects that Firefox in already running and merely opens a new window in the already running Firefox instance. There is a way to run multiple Firefox versions at the same time, each with their own profile folder (it is generally not a good idea to use a profile with different Firefox versions). *http://kb.mozillazine.org/Opening_a_new_instance_of_Firefox_with_another_profile *https://developer.mozilla.org/Mozilla/Multiple_Firefox_Profiles

Umnikazi wombuzo

cor-el said

You can only have one Firefox version running at the time. When you would try to start another version then the startup code detects that Firefox in already running and merely opens a new window in the already running Firefox instance. There is a way to run multiple Firefox versions at the same time, each with their own profile folder (it is generally not a good idea to use a profile with different Firefox versions).

I only run one at at time for sure.

''cor-el [[#answer-718835|said]]'' <blockquote> You can only have one Firefox version running at the time. When you would try to start another version then the startup code detects that Firefox in already running and merely opens a new window in the already running Firefox instance. There is a way to run multiple Firefox versions at the same time, each with their own profile folder (it is generally not a good idea to use a profile with different Firefox versions). *http://kb.mozillazine.org/Opening_a_new_instance_of_Firefox_with_another_profile *https://developer.mozilla.org/Mozilla/Multiple_Firefox_Profiles </blockquote> I only run one at at time for sure.

Umnikazi wombuzo

jscher2000 said

Not sure either of us knows enough about how Portable Firefox handles updates to answer that. Do you still have a previous.js from the right time frame? When you tried to use it, did you:
  • exit out of Firefox completely AND
  • copy previous.js into the main level of the profile folder (not into the sessionstore-backups folder) AND
  • rename the sessionstore.js file to something sessionstore.old AND
  • rename previous.js to sessionstore.js
All steps are necessary, otherwise, the file will be ignored and Firefox will just use the latest sessionstore.js.

I followed your instructions to the tee. Closed my browser completely, copied previous.js (from crash date of 4/13) to firefoxportable\app \defaultdata\profile folder. I presume this is the MAIN level of the profile folder? Renamed previous.js to sessionstore.js (there was no other sessionstore.js there EVEN THOUGH I had no FF browser open!). Strange indeed. Reopened the browser and I see nothing from that old session. It's worse than what I saw when I used previous.js without renaming it. That way, at least I saw 7 tabs from ONE window prior to crash on 4/13 although the second FF window with a lot more tabs was still missing. Unfortunately, I am unable to get to that point again using the same js file for some reason. Now I get just two google tabs plus this forum one, none of the 7 tabs.

I noticed session-store backups folder has my old previous.js as well as a bunch of other .js files. They all have the prefix "upgrade" and a year-month-random# suffix for each.

This has been a fun excercise although I didn't get back what I wanted. At least I understand it better. I have a better way to update to new version next time and know where the .js files are stored, how they are used etc. THANKS FOR FOR SHARING YOUR WEALTH OF KNOWLEDGE!

''jscher2000 [[#answer-718823|said]]'' <blockquote> Not sure either of us knows enough about how Portable Firefox handles updates to answer that. Do you still have a previous.js from the right time frame? When you tried to use it, did you: * exit out of Firefox completely AND * copy previous.js into the ''main level'' of the profile folder (not into the sessionstore-backups folder) AND * rename the sessionstore.js file to something sessionstore.old AND * rename previous.js to sessionstore.js All steps are necessary, otherwise, the file will be ignored and Firefox will just use the latest sessionstore.js. </blockquote> I followed your instructions to the tee. Closed my browser completely, copied previous.js (from crash date of 4/13) to firefoxportable\app \defaultdata\profile folder. I presume this is the MAIN level of the profile folder? Renamed previous.js to sessionstore.js (there was no other sessionstore.js there EVEN THOUGH I had no FF browser open!). Strange indeed. Reopened the browser and I see nothing from that old session. It's worse than what I saw when I used previous.js without renaming it. That way, at least I saw 7 tabs from ONE window prior to crash on 4/13 although the second FF window with a lot more tabs was still missing. Unfortunately, I am unable to get to that point again using the same js file for some reason. Now I get just two google tabs plus this forum one, none of the 7 tabs. I noticed session-store backups folder has my old previous.js as well as a bunch of other .js files. They all have the prefix "upgrade" and a year-month-random# suffix for each. This has been a fun excercise although I didn't get back what I wanted. At least I understand it better. I have a better way to update to new version next time and know where the .js files are stored, how they are used etc. THANKS FOR FOR SHARING YOUR WEALTH OF KNOWLEDGE!

Okulungisiwe ngu rkramadh

jscher2000
  • Top 10 Contributor
8837 izisombululo 72222 izimpendulo
Kuphostiwe

I don't have a "Portable" installation handy on this computer but generally speaking, the main level of the profile folder is one level up from the sessionstore-backups folder. For normal Firefox, it has a semi-random name, but this might not be true of Portable.

The upgrade-various.js files contain a snapshot of your session at the time you approved an update to a newer version of Firefox. If you have been keeping the same tabs open for a long time, one of those might be useful. The procedure for using one of those files would be the same as for using previous.js.

One other obscure feature might be useful: Windows restore points. If you right-click sessionstore.js (the one created when Firefox is fully closed), then Properties, then Previous Versions, you can see whether Windows saved that file in a restore point in the recent past. You could repeat the exercise with recovery.js when Firefox is running, and with previous.js, to see whether either of those has a timely backup. When restoring any previous version file, see whether you can do it in another folder rather than replacing the current file.

I don't have a "Portable" installation handy on this computer but generally speaking, the main level of the profile folder is one level up from the sessionstore-backups folder. For normal Firefox, it has a semi-random name, but this might not be true of Portable. The upgrade-''various''.js files contain a snapshot of your session at the time you approved an update to a newer version of Firefox. If you have been keeping the same tabs open for a long time, one of those might be useful. The procedure for using one of those files would be the same as for using previous.js. One other obscure feature might be useful: Windows restore points. If you right-click sessionstore.js (the one created when Firefox is fully closed), then Properties, then Previous Versions, you can see whether Windows saved that file in a restore point in the recent past. You could repeat the exercise with recovery.js when Firefox is running, and with previous.js, to see whether either of those has a timely backup. When restoring any previous version file, see whether you can do it in another folder rather than replacing the current file.

Okulungisiwe ngu jscher2000

cor-el
  • Top 10 Contributor
  • Moderator
17673 izisombululo 159870 izimpendulo
Kuphostiwe

You can use this button to go to the current Firefox profile folder:

  • Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
You can use this button to go to the current Firefox profile folder: *Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)