User1 != authenticated

You can always create another role, specially for user 1. Assign rthat role to user1 and create new ckeditor profile assigned with that speciall role for user id 1.

This is standard behavior of drupal modules and having it done differently is known & proven to cause a lot of other issues. Why the hell should it be different for ckeditor? Can we please have a solid reason?

@mephir: if people are supposed to do what you mention in #1, then please find a way so that it is done during module installation automatically for them. Try to remember that most newcomers to drupal expect things to work out of the box or at least to follow the standards they are used to from other modules. I mean ckeditor does aim to be user & developer friendly after all. Right?

I think this should be 'active', it should be considered a bug and neither a feature nor a support request and finally set to 'critical' (for all the reasons mentioned above).

PS: if anyone comes up with the idea to move this from code to documentation and simply add a few lines in the readme, I'd still consider this action a workaround and not a solution, thus also far from 'fixed'.

noise - ditto #3 - doc "workaround" in http://drupal.org/node/758614#comment-2928514

@klonos - thanks for your suggestions, I appreciate it. It might be a reasonable idea to make those things simpler in 7.x.

Thanks for taking the time to reply Wiktor.

...and sorry if I came a bit too hard in #3, but I had solid reasons to. I agree on placing new features in 7.x (and then backporting where possible), but as I said, I do not think this is a feature request. On the other hand, if we change fundamental things now, there are more changes to break things.

We can always start a 6x-2.x-dev branch I guess ;)

I have to agree that having to jump through hoops and spend hours of research to figure out why user 1 can't use the module when it is first installed is really, really annoying. Honestly, why is this labeled a feature request and not a bug?

Issue is inactive over 3 months, so i closed it.

I think that everything is explained here so more comments aren't needed.

...still, far from fixed.

...not that I agree on simply closing this. We are simply avoiding solving a valid *bug* IMO.

I am now using the admin_role module http://drupal.org/project/adminrole to assist with this, it has really helped.

yep, + in d7 that ability is in core by default, which is good news.

The thing is though that this is nothing but a workaround to an issue that should be resolved instead of being ignored. We should at the very least document this.