Skip to content
This repository has been archived by the owner on Dec 28, 2022. It is now read-only.

NewTabTools not functionning after moving Firefox profile to another computer #488

Open
ysalmon opened this issue Feb 19, 2022 · 3 comments

Comments

@ysalmon
Copy link

ysalmon commented Feb 19, 2022

Hi,

this is just for reference to future users : when moving the firefox profile folder as a whole to another computer and starting Firefox there, one may experience problems similar to #280. Indeed, opening a new tab just show an XML error page referring to some moz-extension page. At least this is what happened to me (moving from Linux to another Linux, btw).

Running firefox -purgecaches the first time after the transfer prevents this error from occurring (at least it did for me !).

@ysalmon ysalmon closed this as completed Feb 19, 2022
@ysalmon
Copy link
Author

ysalmon commented Apr 21, 2022

I have to rescind that statement ! It is not always working.

@ysalmon ysalmon reopened this Apr 21, 2022
@ysalmon
Copy link
Author

ysalmon commented Apr 21, 2022

I cannot wrap my head around the fact that the extension behaves differently when the profile is moved to another computer. HOs is this possible ? It is reading from the same files.

@ysalmon
Copy link
Author

ysalmon commented Apr 23, 2022

It seems newTabTools (and some other extensions too) store, or rely on something that stores, the absolute path of the firefox profile.

As my profile is not under the same path on both machines, this leads to malfunction. I tried replacing all instances of the old path with the new one

find $newPath -type f -exec sed -i '' -e 's:$oldPath:$newPath:g' {} \;

This seems to work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant