RyanWilliams

There does appear to be a quirk with its behaviour, but ALT+PLUS and ALT+MINUS are definitely intended to increase and decrease the editor width.

After some brief testing it would appear that the shortcuts don’t work at all when you first initiate the distraction-free editor, however if you click on the title the shortcuts begin working as intended.

• Government or school with aggressive security procedures such as disabling JavaScript
• Person using browser add-on such as NoScript to block JavaScript unless manually executed after page load

As for having an outdated browser, it’s not uncommon for people to simply neglect updating their browser, or perhaps the automatic mechanism for doing so has failed for whatever reason and won’t check again for another several days/weeks.

In my opinion the nag is unnecessary. If it were only pointing out very outdated browsers such as IE6 and IE7 then fair enough, but if it’s nagging people when they’re only a sub-version or two behind then that’s OTT I reckon.

Running Page Speed, YSlow, and RSS Subscription Extension. Problem remains when all are disabled.

I’ve just verified the issue on a colleague’s machine, the common factor being we’re both on Windows 7 and both using Chrome 12. Doesn’t happen in Firefox.

I think what’s important is to identify what you dislike about the new full-screen mode and then request that functionality. The new full-screen mode isn’t going anywhere, and while the old one could have been maintained WordPress generally tries to avoid cruft and redundant features.

I used the old full-screen mode a little and from what I can tell the new mode isn’t that different at all. The key changes that I’m assuming are annoying people are:

• No ability to have editing area expand to full width of browser window — could be fixed with a simple toggle
• Editing bar is simplified and doesn’t have full range of options presented on the main editing page — could be fixed by simply duplicating the WYSIWYG of the main editing page, even if stylised and/or toggled

Anything else?

Indeed.

I agree that some things need refinement. Don’t like all the side menu title being bold, don’t like the weirdly thin serif table headings, and I think having a contrasted top bar worked well.

However it’s far from ugly. In fact it’s not even that different to the last one for the most part, and as with the other several admin designs of the past it’ll continue to be refined and improved with future versions.

You’re best off specifying how it can be improved rather than issuing the usual blanket ‘don’t like it’ response 99% of people give when faced with change, because it ain’t going anywhere. You can use an older version if you wish but we both know it’s only a matter of time before you desire WordPress’s future new features and start getting scared about security problems.

Should be there, just below the ‘howdy’ text — I’ve got 3.2.1 installed and see both ‘Screen Options’ and ‘Help’ exactly as before.

Could it be those notifications you’ve got? Try getting rid of the Akismet warning and the Jetpack banner to see if it helps. Might be a style clash.

This message is displayed to anyone with an outdated browser. I just got it when viewing the admin area in Firefox 4 which has only just been superseded by Firefox 5 — it clearly uses some kind of check to see whether or not your browser matches the vendor’s latest version.

I do think it’s a little intrusive though as browser updates come thick and fast nowadays, and I don’t need WordPress telling me Chrome is out of date every few weeks just because it hasn’t gotten around to auto-updating yet. Hopefully turning these notifications off is a setting somewhere, if not it should be.

Echoing this wish.

Excellent, I’ve sent it across.

Hiya,

Fast response! I’ve just given the updated version a go, unfortunately it’s still saying the details aren’t valid when I use the ‘Check Details’ button and uploading just stops at the first file (ie: fails and doesn’t proceed).

Interestingly I also have a Rackspace US account and I can’t get it to work using those details either. However, if I use W3 Total Cache and use my US Rackspace details there, it works — but the UK details do not.

Is it possible your new update has broken support for both Rackspace variations? :s

If you like I can privately send you my CNAME, username, API key, and container to test with — I can destroy them afterwards. If you can get it working on a set-up you’re familiar with then at least I know it’s nothing on my end.

Try deleting (or ideally opening and emptying) your .htaccess file in the main folder of your website, it might still be trying to direct things through to the non-existent cached files.

This is the log of everything that happens the moment I hit the ‘preload now’ button:

https://pastebin.com/z1FLHRAH

Fairly concerning that this is still an unresolved issue despite WordPress 3.1 having been out for several weeks. Ideally the plugin would be made as compatible as possible in advance of an official WordPress release, considering how the site is supposedly used on large sites such as Smashing Magazine, and that the plugin is relatively critical to the smooth running of a site.

If the plugin author is having trouble maintaining it I’d recommend going on some kind of drive to get donations (I’m sure the larger sites using it would be happy to contribute), or perhaps finding someone else to help with its maintenance.

There is an easier way to get the ID, but it still really needs just putting right in the media uploader as like a checkbox or something.

Go to the main media library in your WordPress sidebar, and when you click ‘Edit’ on any of them the ID will be in the URL. You can obviously also preview the URL by just hovering over it.