Files in default\profile are not being copied to new profile
I am getting conflicting information on how to create a generic profile to be used throughout my organization. Using Profile Manager is not appropriate in my situation. I have tried to place files/folders within the 'Default\Profile' directory, 'Browser\Default\Profile' directory, etc., and nothing is ever copied to a new profile. Specifically, I have created a custom 'userChrome.css' file that I want to distribute. From what I've read, a chrome folder needs to be created in the user's xxxxxxx.default directory and the .css file placed inside. What am I missing?
Thanks. Eddy
所有回复 (6)
The correct path is "browser\defaults\profile" and the userChrome.css needs to be in the chrome folder in this folder ("browser\defaults\profile\chrome\userChrome.css").
No luck. The chrome folder and userChrome file are not being copied. And just to clarify, the path for the userChrome.css is: "C:\Program Files (x86)\Mozilla Firefox\browser\defaults\profile\chrome\userChrome.css"; and the chrome folder (along with the userChrome.css file) should be copied to a new user's default profile. Manually copying the folder and file is not a problem. Could it be a rights issue, or the fact that the AppData folder is hidden?
It works for me.
Are other files in \browser\defaults\profile\ copied to a new profile?
Before I replied back, I wanted to make sure I wasn't missing something. Apparently, I was. Short scenario - I'm using a batch file to install FF and am copying a custom mozilla.cfg file. We are also using PolicyPak to control the behavior of Firefox. I removed PolicyPak, uninstalled FF (and removed all references to it), reinstalled v27.01 using the file downloaded from Mozilla, et voila! Now the chrome folder and userChrome file are being copied. Now I have to see where exactly the breakdown is occurring.
Thanks cor-el.
选择的解决方案
You're welcome.
Note that some features may only work with the official version from the Mozilla website. Some features may also only work with the en-US version (*)
I just wanted to follow-up with my findings, just in case someone else out there has a similar problem. As I mentioned earlier, we are using PolicyPak to control the behavior of FF. When PolicyPak sees that FF is installed, it applies its settings to the user - it needs to create a default profile to do this. So, when FF launches the first time, it sees that a profile already exits, and does not copy the chrome folder or the userChrome.css file.