Error message on codeblocks startup

[PDEE]

Hi all, not been on here for a while as i don't have problems with code::blocks. Until now. I had to put a new hard drive in because i had damaged sectors. Anyway, reinstalled code::blocks from scratch and when i start code::blocks, everytime this message pops up:

Can not enumerate files in directory 'C:\Documents and Settings\name\Application Data\codeblocks/share/codeblocks/plugins'(error 3:the system cannot find the path specified.)

There is no plugins folder inside that folder. There is only a folder called scripts. Anyone shed some light on this? The software works fine it's just that message. Thank you in advance.

Oops, should know by now...forgot the info you require hehe : Build Nov 17 2006, wx2.6.3 windows xp unicode. Never mind, it looks like i'm not the only one. Should of looked first. I know, my bad 

[OnlineCop]

PDEE:

I got the same thing (I just installed C::B two days ago).  To fix, I simply added a "plugins" folder manually and everything worked fine.

Open your My Computer, enter this on the Location Bar at the top (including both percent-signs):

  %APPDATA%

That will take you to:

  C:\Documents and Settings\~yourname~\Application Data

Find there, navigate to:

  C:\Documents and Settings\~yourname~\Application Data\codeblocks\share\codeblocks

Create the subdirectory "plugins" and when you restart C::B, everything should work.

[killerbot]

hmm,
void ConfigManager::InitPaths()

should take care of this

@Thomas : can you check this ??

[MortenMacFly]

@Thomas : can you check this ??

...I believe he did that in r3233?!

[PDEE]

Thanks everyone, works a treat now. 

[killerbot]

@Thomas : can you check this ??

...I believe he did that in r3233?!

that explains why the code looked ok to me ;-)

[thomas]

@Thomas : can you check this ??

...I believe he did that in r3233?!

that explains why the code looked ok to me ;-)

ConfigManager sure looks ok, because it was OK
The problem is that if you build your paths by concatenating substrings, rather than using ConfigManager::GetPath(), then obviously GetPath() never executes and never calls InitPaths(). That was fixed in above revision.