Destination path too long error message
I get this sometimes when moving/backing up profile contents, even when the the eventual path of the moved contents will be shorter than the original.
I have a problematic profile, so I copied it's contents to another folder with a shorter title in the same directory, but I prevented from including the file in question.
In this particular situation, the file in question is an .html file opened in a session tab. I assume It's omission not going to be detrimental.
Has anyone seen this sort of thing occurring with files that directly affect profile operations? I'm wondering if that sort of thing might be contributing to my current recurring profile issues.
Alle Antworten (4)
If you save an HTML file then Firefox also creates a files_* directory (it's name depends on the locale) that stores extra files like CSS and JavaScript and image files. The name of the HTML file is the page title and some webpages can have a very long title.
cor-el said
If you save an HTML file then Firefox also creates a files_* directory (it's name depends on the locale) that stores extra files like CSS and JavaScript and image files. The name of the HTML file is the page title and some webpages can have a very long title.My focus is not on the html file. It's simply an example pf the latest incident of the restriction. The path/path length for the html file has already been established in the original folder.
Were talking about backup folders. Essentially storage spaces, with no current Firefox engagement. I just now added one letter to the title of that folder, and created a new folder with the name of the original folder. I was still not permitted to move the html file.
The original folder was named ALL BACKUP++ GOOD - 7-28-24. I then renamed that new folder ALL BACKUP++ and got the error. I just renamed it again to the single letter "A'. I still got the the pop-up (see image}. No mention of the html file this time. In fact, it offers no clue as to why it appears, but now, the html file is in the new folder.
My concern is addressing the situation when it involves files critical for proper performance.
Geändert am von noel_envode
cor-el said
Whats under More details?That may be the strangest part of this already weird situation.
When I said "No mention of the html file this time. In fact, it offers no clue as to why it appears", I was being quite literal. I should have made it clearer that what you see in that image is all you get.
"More details" is greyed out. It says Destination path too long but there is no reference. no explanation? How can that possibly happen? For me, that kinda follows the pattern here. None of this stuff makes sense to me.
This may be a stretch, but this topic kind of evolved from the recurring problem discussed in my previous thread Non functioning Export/Import, upload images.
If we don't do anything else here, can you please address my question from there about importing tabs? The only way I was able to overcome the problems addressed in that thread last time was to go thru the one one month gap in the library history from the latest profile with the broken sessionstore.jsonlz4 compared to the backup profile, and add/restore all those items manually, one buy one, to the backup profile.
That backup profile eventually became the broken profile that I now, once again, have to gather history from for transfer to my current backup, which is what I'm using today to write this.
If this recurring problem keeps recurring, in the least I need the simplest way possible to restore my session/history from the corrupt profile.
Geändert am von noel_envode
Sie müssen sich mit Ihrem Benutzerkonto anmelden, um auf Beiträge zu antworten. Bitte stellen Sie eine neue Frage, wenn Sie noch kein Benutzerkonto haben.