Josh Levinson

That is an excellent point! I don’t know how I failed to recognize that logic. However, I fail to see how that scenario would apply to theming. For plugins, it obviously wouldn’t work. But one only ever has one theme active at a time.

Right, I should have mentioned in my initial post that I also recognize that the priority parameter is available as well. However, when using this for client sites, there is no way for me to guarantee that a plugin installed at any time will override my styles. I’m looking for a real solution to the problem, not just an implementation of an already available parameter that doesn’t do exactly what I described.

Okay – that answers my question. So for single and Multisite, the serialization is the problem?

Set up a new user with the correct username and a throwaway email address. Delete the old user. during the deletion process, you should be asked if you want to delete the old user’s posts or transfer them to another user. Select the new user. Finally, change the new user’s email address to the one previously used.

Quoting myself:

I want to change the username for security reasons, as many suggest to do, but without having to create a new user, delete the original user, and assign his posts to the new user. Kind of a hassle.

I know I can do that already, and I know that plugins are out there. My initial question is why is the option expressly forbidden by default?

Again, consider this only being allowed by the Administrator role.

Why do you need to reinforce that you have a new user ID?

I’m sure I could whip up a plugin to do the job, but I just was wondering why it is explicitly not allowed when it seems (sorry if I envisage it to simplistically) so simple to me.

@andrew – your question confused me a bit. I was thinking mostly from an admin perspective.

@esmi – I have run into a few scenarios where this would be useful.

1. A wordpress setup with the ‘admin’ user, with quite a few posts. I want to change the username for security reasons, as many suggest to do, but without having to create a new user, delete the original user, and assign his posts to the new user. Kind of a hassle.

2. A wordpress setup for a client where I misspelled one of the usernames, then that person created a bunch of posts before complaining that their username was misspelled.

I’m sure I’ve run into more situations, but cannot recall those now. I’ll post later if I can think of them.

Tbh, I don’t see a good reason NOT to allow this. However, I’m open to suggestions. Why do you guys think it’s not a good feature to have by default?

I still have this issue – are you sure it was fixed?

I was wrong in my previous assessment of not having any buttons at all.

When I add a file for the first time through the upload dialog, after it is finished uploading a ‘Insert into post’ button appears. Clicking on this button only results in the page loading, with no file being attached to the cf.

I have switched themes back to twentytwelve with no success. I will try deactivating plugins.

Thanks for your quick reply.
Here you go:
WordPress 3.5
PHP 5.2.17
Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8e-fips-rhel5 DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.97 Safari/537.11

— Active Plugins —
Custom Field Suite 1.8.1
Gravity Forms 1.6.11
Jetpack by WordPress.com 2.0.4
Reveal IDs 1.3.0
Shortcode Exec PHP 1.45
Theme My Login 6.2.3
Types – Complete Solution for Custom Fields and Types 1.1.3.3
WordPress Shortcodes 1.5.1

Np! First things first, what theme are you using?
Edit nvm looks like you are using themia. Youll need to send me your wp login info.

https://snag.gy/JoMZW.jpg

This looks to me like a theme issue. Typically the sidebar gets pushed down if:
A) It is coded into the wrong place
B) It’s content is too wide for the theme’s layout. Shrink either the content width or the sidebar width.

I believe in your case it is A. I tried moving the div “grid_9 sidebar_wrapper omega” INSIDE the div “grid_24 content_wrapper”, directly underneath the content div “grid_15 alpha”. After I made this change, the sidebar showed up as expected.

Line 21 of bp-media-uploader.js in /buddypress-media/includes/js change from

if(bp_media_album_selected == false&&bp_media_is_multiple_upload==true){

to

//bp_media_is_multiple_upload==true
        if(bp_media_album_selected == false){

This change will make all uploads forced to pick album or create new.
I know this involves editing core plugin files and will be written over on update, but this may help those who need this feature while 2.4 is being developed.

Ended up going with WPEC (getshopped.org). We will see if this was a good idea soon.

Ended up going with WPEC (getshopped.org). We will see if this was a good idea soon.