How do I get back to a full-size CSS edit box?
-
For some reason, when I access the CSS editing area via any of the paths I’m used to using (Dashboard > Appearance > Custom Design, etc) I am now taken to the home page of my site with that darned black “Customize Your Blog” right side pop-out sidebar. Can someone help me get back to a regular size CSS editing screen? Thank you so much!
P.S. Site is not live right now…am helping a nonprofit with it and they aren’t ready yet…so you can’t see it, but I’m hoping there is just some access thing that I missed the announcement on!
The blog I need help with is: (visible only to logged in users)
-
Oh bless your pea-pickin’ little heart! :) I see it was just changed on April 11 — so relieved it wasn’t just that I am getting old and forgot how to get to it!
Hooray for you and your timely answer!
-
-
Can someone help me get back to a regular size CSS editing screen?
We’re planning to phase out the older admin page. I’d love to hear your feedback about why you don’t like the new slide-out style. I listen to and keep track of feedback like that.
-
Oh my, I have been preoccupied with my main website responsibility which uses the .org software on an organization’s domain, so had not had a reason to look at the CSS option on one of my wordpress.com sites with that feature. On browsing the forums and seeing the comments about the editor, I visited the one .com site on which I use the css editor today.
I would really dislike editing code on a black screen, but didn’t even have an opportunity. When I looked for my current custom css, what I see on the black screen is a tiny gray box – postage stamp width (actually shows just 22 characters) and height of a skimpy 3 lines. No way I can see the css I have already added, much less edit it in any way, although I can scroll it up. The rest of the black screen seems to feature a box for setting the content width of the theme. and this is with the CSS choice chosen in the more colorful menu on the right.
Admittedly I am on an ipad, but on my .org website, I am able to do about 99% of my editing on this, including a lot of css editing. When I see this I shudder as I think about a little wordpress study group we have where most of our members are novices who were led into the wordpress platform by me. Looking at this mess, I regret ever saying an encouraging word to them. I don’t want to go to our next meeting only to say “Flee. flee immediately and permanently.” And I am TERRIFIED because often wordpress.org is the test ground for enhancements for the .org version.
Since I also moved this org’s website TO a wordpress (.org) platform I have a feeling that my name will be MUD if this migrates to the .org version. Looks to me like someone thought the sliding panes was clever-looking, but didn’t take into account that it is nice to see clearly the full CSS. Will update later with my experience using it on my notebook – not that I should have to use the notebook.
-
-
what I see on the black screen is a tiny gray box – postage stamp width (actually shows just 22 characters) and height of a skimpy 3 lines.
This doesn’t sound right at all. May I bother you for a screenshot and some additional info about your browser environment (i.e. version)?
-
Not usually a public site … But you can see a screen print here:
http://csstestingwp.files.wordpress.com/2013/05/image.jpgAs I said, I work from an ipad most of the time. Safari.
My main concern is the possibility of this moving to the .org version although I won’t choose to re-up on the custom design for .com even if it come out of the little box if it remains on a black screen with no option to toggle to a white screen.
And if the black screen trend comes to .org without options to disable it, I will either leave wordpress or turn over the website I love managing to someone else. I think the black screen is simple trendiness totally at odds with functionality.
That being said, I love the wordpress community and especially the community here at .com.
-
Hi Timethief! Been having fun with shopping carts, and forms with databases with .org version. Miss hanging out here though. These forums are just amazingly helpful. I see you are as busy as ever. In the couple of times I’ve browsed back over here, I see that the CSS forum is being handled more by the pros and fewer opportunities for amateurs like myself to dabble. I think the end user is being very well served.
-
Thank you for the screenshot! Very helpful. Looks like a bug. I will check up on it and post back here when I find out more.
I won’t choose to re-up on the custom design for .com even if it come out of the little box if it remains on a black screen with no option to toggle to a white screen.
The CSS editor itself has a white background.
I think the black screen is simple trendiness totally at odds with functionality.
Why (specifically) does the black background in tools bug you so much?
Regarding WordPress.org, you should roll up your sleeves and get involved in these conversations: http://make.wordpress.org/ui/tag/mp6/ MP6 is a new direction for the dashboard, separate from the Customize panels, but those may possibly merge at some point in the future and the design trend for the two feel similar to me.
The posts are quite long, if you’re limited on time, read the main content of the first post about it by Matt:
http://make.wordpress.org/ui/2013/03/09/as-a-continuation-of-the-work-begun-in/Be open minded, and give the new admin design a chance (it has a lot dark backgrounds).
That being said, I love the wordpress community and especially the community here at .com.
Ditto. And I love that you give back to the community in the forums from time to time! :)
-
On website front end design I think that black backgrounds can be effective , especially for graphical content. However if one is working back end with content and html and css I think that is much clearer in black on white, easier on the eyes and more scannable visually.
I am reassured that the actual css editor has a white background. in my little 3 line, 22 character box, it looked as though you would be doing that in a gray box on a black background, although I assumed that the box size was supposed to be larger. I honestly see no reason to change the CSS editor at all. You are editing text. You don’t need bells and whistles. Sufficient to have a page that I can visually scan up and down, an easy way to refer to the parent stylesheet – characteristics of the previous editing features on .com and the current features on the .org software.
I would just as soon read novels on a blackboard as to do my work in white on black text, nor do I consume much content on websites or apps that have white on black. It’s just not a presentation medium for words … for me.
I also think it is one of those trends that will look dated very quickly. We will look back and say, remember when we all went to the black backgrounds? And have a big laugh about it. But front end design does follow trends, legitimately so. But so far the backend has not had that need.
Thank you for the links to the conversations about the new directions for the dashboard. I will read them. I am struck by your comment that the new admin design has a lot of black backgrounds, and I ask your same question of that choice .. Why? Specifically? Hopefully answered in the articles you provided.
I will also check out the editor on my notebook, maybe after I do my web work for the day – on my ipad, using wordpress.org version, working in text mode *almost* exclusively.
-
Hi again!
I agree so much with everything houstonweaver said. But just in case my thoughts matter…
We’re planning to phase out the older admin page.
Does this mean that I will have access *only* to this small CSS editing area?! This makes me get a sick feeling in my stomach, the thought of being limited to working in this little area. I didn’t realize, until it was gone, how much I love to be able to scan what I’ve done above and below the place I’m editing. Twenty lines of code is not very many to be able to view at once.
Also, if I can’t go full width on my screen, there is so much wrapping of long lines (usually my comments are longer, since I try to leave a thought trail in my CSS edits), and these wrapped lines fill up many of the 20 lines visible in the new editing screen.
I suppose seeing the whole field of code doesn’t seem important…but I just wonder why anybody would think that less viewable code is better, and worthy of changing an interface that works so well for anybody who is editing the CSS.
Thanks for asking! :)
–Sandy -
I agree with Sandy about needing the whole page for scanning.
As I think about the updating the user interface, it is useful to review that interface to see if it presents the wordpress software functionality clearly to the user. The goal is to improve the understandability and functionality of the product in achieving the user goals. I am looking forward to exploring the results of that review further.
I view the CSS editing to be a bit of a departure from that interface. What it offers is a step into, well, CSS editing (not a soul province of wordpress). I don’t think most editors just approach each new need as a piecemeal item. To a greater or lesser degree depending on skill level, it is done by analysis of what has gone before in the parent theme, what you (or a previous admin) has done in your child theme already, and what you currently want to do. That speaks to a need to see both parent and child full CSS and to edit the child in a full access environment. (On a white background. :-) )
It should have the look, feel, and functionality of CSS editing on any website. Simple text documents.
-
-
We released a small update tonight that corrects the size of the CSS input area on certain devices such as the iPad. Thank you for letting us know about this issue.
-
Love the rapid response.
15 lines is an improvement over 3, but I still think not nearly sufficient. The print is small as a result of using so much screen for the page view etc. and is white text on gray background. I would not view it as adequate if I were serious about editing css for my WordPress.com website. I am just appalled at the thought of this moving to the wordpress.org environment. Sandy (above) described my feelings perfectly in not understanding how viewing less can seem an improvement over viewing more. This approach seems to trivialize your product.
I do appreciate that you listen to your users. Please reconsider this approach to the CSS editing. I do not think most of your developers would work on their “coding” in this kind of presentation. Many of us are amateurs and need the broader view even more than you experts.
-
15 lines is an improvement over 3, but I still think not nearly sufficient.
Just to reiterate, the 3 lines was definitely a bug and not intended.
I do appreciate that you listen to your users. Please reconsider this approach to the CSS editing.
We are definitely listening! But do note that some users may feel the opposite that you do, and we hear all sides. The best thing to do is to keep talking about it, provide honest and detailed explanations or scenarios that back up your position. @houstonweaver, you’ve done this already, please keep the feedback coming and note that I’m keeping an eye out for more examples like yours and Sandy’s.
- The topic ‘How do I get back to a full-size CSS edit box?’ is closed to new replies.
WordPress.com Forums 
