freelance08

I think he means that when viewing all plugins, the activated ones should be lumped together like they used to be. I strongly second that – and is it just me, or are activated plugins no longer distinguished by having a green background? That’s an odd “improvement”, IMO.

And please do provide a way to disable the code editor – it’s noticeably delaying the loading of my plugin and theme editor pages. It’s a nice idea, like many of your radical changes are, but, like many of your radical changes, it would be better if you made it optional. There doesn’t seem to be a whole lot of recognition of the fact that some people would like to be using principally the same piece of software for more than a few months at a time. It would be great if there was a way to get some of the improvements that come from the upgrades, without having to deal with radical interface changes every time we go up a .1 version. I thought the old plugin page was fine. So much for that I guess though.

Don’t get me wrong, I’m a mad WP lover, but my upgrade to 2.8 is making things suddenly considerably more awkward. Not what I hope for in an upgrade – but that’s beginning to become a companion “feature” to each serious WP upgrade. (i.e., having to re-adapt to major–sometimes questionable–“improvements” in the interface)

Anyway, there are probably some good, non-unsettling features in this upgrade too; I assume I’ll bump into them eventually. Thanks for those! And thanks in advance for considering ways to allow us to have a stable interface for more than three months at a stretc while still following your recommended upgrade schedule. Because for now I’m going to start advising my WP-site having folks to just stay at one version (probably 2.71) for as long as they can stand it, to avoid jolting changes.

I don’t know about anyone else, but qvprof’s solution worked for me. Thanks qvprof!

I’m also very interested in this. It seems like there are FTP-like tools for the backend, but I haven’t seen one that restricts a user’s access to only a certain folder. I would like to give a user/client access to their own folder where they can upload files, while another client has access to their own folder, and so on. If anyone knows a good way to accomplish this, I’d appreciate hearing it. It’s easy to do when setting up an FTP user via cpanel, etc., but I don’t know how to bridge that into a web-based, wordpress-based interface.

So far I’ve found a couple of the backend FTP tools I mentioned, which don’t seem to have a way to restrict location access per user, and now I’m trying out cforms. But while cforms will help get files uploaded, it doesn’t provide the user directory access which would be ideal. And it requires going elsewhere to add subfolders, and creating a whole new form for each client if I want the subfolders to be used, and so on. I’d really prefer to give site clients/users a way to see and use their own (private) subfolder for uploading files.