Path token doesn´t work with core file upload (node attachments)

Addition: I use a local Xamplite installation.

No - sorry, this was my fault.
I have mistaken [uid] with [user-id].

By the way: FCKEDITOR knows the path tokens %u (user-id) and %n (username).

FCKEditor claims to support these tokens / wildcards %u %n (and %d %b %f %m), but I can't get them to work.

It'd be great to get Filefiled tokens working -- my site strictly enforces user partitioned spaces, so I'm looking for a way to both:

1. have the FCKeditor file upload/browser support user-name and filefield path and title tokens for the UserFilesPath root
   (e.g.: [user-name]/[filefield_name-title]/[title] is where I store uploaded files for nodes, so this would also be a good place for images in the node body)
2. not allow browsing above UserFilesPath to preserve cross-user and even cross-node privacy.
   (e.g.: when an image/file is uploaded and used in a node body, it can be used only for that particular node.)

I read about IMCE and Image -- the former doesn't do tokens, but the latter seems to in some way (but I haven't tried yet)

It would be great if there's a way to do this either by setting up fckeditor.module or FCK's config.php to parse tokens, or in Admin settings.

@quicksketch -- It was nice seeing you posting in FCKeditor issues. I hope you have some insight on this - Thanks! :)

@ksc

Glad to hear you got it sorted.
As for FCKEditor, currently there is no integration with FileField Paths, I may look at something in the future, but it's probably a fruitless task.

@mudd

ImageField (not Image) works perfectly with FileField Paths, so you could look at that.
As for IMCE and FCKEditor, there's not much I can offer in help.

Also, quicksketch is the developer of FileField, not FileField Paths :)

Cheers,
Deciphered (the developer of FileField Paths)