posted this on March 13, 2013 01:48
Location of the IDE files depends on the operating system, product and version.
Should you need to change the defaults, refer to this document.
All the files are located under this directory by default:
<SYSTEM DRIVE>\Users\<USER ACCOUNT NAME>\.<PRODUCT><VERSION>
<SYSTEM DRIVE>\Documents and Settings\<USER ACCOUNT NAME>\.<PRODUCT><VERSION>
Under this directory you'll find the following sub-directories
Product directory starting with dot can be found in your user home directory, the pattern is:
~ is an alias for the home directory, for example /home/john.
PRODUCT would be one of the following:
Today I use the latest version of PhpStorm (7.0 .WebIde70)and I have old big directories .WebIde50,.WebIde60. .Can I safely delete these two directories.
Pascal, yes, you can remove these folders if you don't plan to run the old IDE versions.
What if the .<PRODUCT><VERSION> directory doesn't exist? I get an error at startup (created a ticket in YouTrack), but I can't find that directory. Intellij crashes at startup, just right after the splash screen.
Debakkerbjorn, try to override the default values with the path where you have full write permissions.
I use Intellij 11.1.5 and I can't find these directories either. Is this information still current for version 11? This is very frustrating. I get an error at startup but cannot find logs, preferences in these locations.
Just to add, I am using Mac OS Mavericks and I don't find a single one of the directories you claim above that I should find.
Barclay Dunn, yes, this information is actual for IntelliJ IDEA 11.1.5. Make sure to look under your home directory. Finder may hide these directories by default, show hidden files via cmd+shift+. (dot) can help to find them. Note that ~ stands for /Users/<user>.
Aw crap, I totally overlooked the ~. The files are there as you say.
Due to this Bug in the JDK on Windows System.getProperty("user.home") is NOT always:
Instead the JDK uses the parent folder of the "Desktop" folder from a registry key.
Maximilian, indeed, this issue is mentioned in our KB with a link to the same bug.
Support Ticket System by Zendesk