olyma

@christinabarefoottrimmer The new font they’ve used in the admin doesn’t display good in a lot of browsers, not just yours, but mine too. I’ve got a thread going in the “Hacks” section of the forum if you’re looking to fix the font in 3.8:

https://www.ads-software.com/support/topic/turning-off-open-sans-for-the-38-dashboard

Actually, commenting out the one line of the core file (mentioned in the thread above) has just worked the best on all my installations. You’ll have to comment it out with every installation and likely with every WP update, but it completely gets rid of WP calling the new font, causing it to fall back to displaying a font that’s easier to display in more browsers.

I think it’s very telling and sad that you’re discouraging people from adding their negative experiences with the new Admin panel.

Agreed, negative feedback is what this section of the forum is for. The primary topic of this thread is the “feedback” that the 3.8 interface is absolutely horrible and the “request” that the old interface be brought back as a part of core.

If you want to focus and encourage others to just complain about the 3.8 admin GUI then you do not need my help.

Then let the “Requests and Feedback” posted here in this part of the forum be seen by those who shall help us and add it back into the core.

I’m finally getting to upgrading some of my own sites (not client sites), and as I’m doing so, I realized how much I really really hate the new interface. So I’m leaving some feedback now. Please listen to the massive amount of feedback you are receiving and allow (not just through plugins) for people to use a skin of the old interface.

If WordPress were a company, a TV or radio station, etc. and they got this level of negative feedback, they wouldn’t tell them to shut the * up and use a plugin, even going so far as deleting complaints — editing the feedback to further justify their actions against community feedback. They’d respond to those complaints. Please please please, respond and make it in core to use the old interface.

I’m looking at the old interface, and it is quaint and a bit cute. Even the “Howdy” greeting is too!!!!!!! I LOVE IT!!!!!!!!!!!!!

WordPress is making a very very grave mistake if they do not listen to these complaints and not being community driven at all.

Please put the old skin and fonts in core.

Many thanks.

Some people seem to be getting into SASS abstraction which I see as a mistake for a lot of WP development. So many sites are just relatively simple, and one shouldn’t have to learn some new abstraction to bog a little site down when the old standby css works just great. If they want massive abstraction, they should be using Drupal.

Commenting out the $open_sans_font_url in the core file seems to speed up the load time of my admin pages too. I’m not an advanced programmer, but I know there’s got to be a php solution instead of altering the core file directly.

Thank you for the plugin link, I’m looking into it now it has some things in it that might be helpful. I’ll just keep hacking on it and see where I can get.

Yeah, it is odd that they don’t somehow leave folks a 3.7 skin for the site, or didn’t set one up b/c it doesn’t seem to me that it would be that difficult to set up. Still…

Mosin Mark, it’s pretty easy to reskin the admin. You can make a simple plugin to add separating lines between menu items, or alter the admin however you like.

<?php
/*
Plugin Name: Menu Separators
*/

function menu_seps1() {
?>
<style type="text/css">
#adminmenu li.wp-has-submenu,
#adminmenu li.menu-top-last {
	border-top: #313131 1px solid;
	border-bottom: #181818 1px solid;
}
#adminmenuwrap {
	border-top: #181818 1px solid;
}
</style>
<?php
}
add_action( 'admin_head', 'menu_seps1' );
 ?>

You can fiddle with the colors to make them a bit different, but the above code should add separators for you.

Yay!!!!!!! I just updated to the latest nightly build and the dev folks fixed the icons to display right on my old system! Thank you dev folks!!!!!!!! :)))))))))))))

Please do not put down old ways and appearances of doing things as unsexy and SOL. It’s not IE, but it is quite old. Old is very sexy too. From what you’ve said, I’d imagine that I’ll have to write another plugin to remove the icons and adjust the spacing for the legacy system. Thank you.

I’ve found this too, but not just on hovering over admin text. Where resolutions are less and on a lot of older browsers, I have also found the new fonts to pixilate or simply display rather badly. Trying to fix the problems on my own machine, I created a tiny plugin on the fly, this has resolved the issue on my installation. If you are having the same issue, just substitute in whatever font works better for the older browsers you may be using:

<?php
/*
Plugin Name: Better fonts
*/

function betterfonts1() {
?>
<style type="text/css">body {font-family: Times New Roman,Times;}</style>
<?php
}
add_action( 'admin_head', 'betterfonts1' );
 ?>

This seems to work very well and the fonts all display nicely now.

Along these lines, on older browsers, none of the dashboard icons display at all, but instead, for each icon is a small rectangle with a jumble of four numbers and letters in it. It just makes the dashboard awkward to look at. Looking through some of the code, the icons seem to be embedded in a font of a sort. Is there any chance they’ll change the icons to be image files so it’ll still look nice on older browsers?

It’s just a very nice orientational administrative enhancement really, and one can turned it on or off within the register_taxonomy function itself.

When you register a custom taxonomy, using the register_taxonomy function, see the codex:

https://codex.www.ads-software.com/Function_Reference/register_taxonomy
and
https://codex.www.ads-software.com/Taxonomies

to create a custom taxonomy, for a custom post type you create using the register_post_type function, see the codex:

https://codex.www.ads-software.com/Function_Reference/register_post_type
and
https://codex.www.ads-software.com/Post_Types

if you were to visit the admin area where all of the entries of that specific custom post type were listed, you’d see whatever custom taxonomies you’d created listed in their own individual columns! See:

https://make.www.ads-software.com/core/2012/12/11/wordpress-3-5-admin-columns-for-custom-taxonomies/

It’s the wellest!

I am not familiar with the woo_commerce plugin, but whatever the custom taxonomies, the code examples above should allow you to select for use only the custom taxonomies YOU WANT, and when you do so, everything else will be, by consequence, excluded.

I was having the same difficulty, below is an answer I found that seems to work well.

First go to your categories-images.php file within the plugin directory for this plugin. Open the file, and near the beginning of it you will find the following lines of code:

add_action('admin_init', 'z_init');
function z_init() {
	$z_taxonomies = get_taxonomies();

The above makes this plugin apply to ALL of your taxonomies. To make it so it will work with only one of them, replace the above code with the following code, and where “my_taxonomy_01” is, stick in the name of your taxonomy, specifically the code version of it:

add_action('admin_init', 'z_init');
function z_init() {
	$args=array(
		'name' => 'my_taxonomy_01'
		);
	$output = 'names';
	$z_taxonomies = get_taxonomies($args,$output);

Now if you wish to apply the plugin to MULTIPLE SPECIFIC taxonomies, then use the following code replacement, replacing of course where “my_taxonomy_01” and “my_taxonomy_02” are with the specific names of your taxonomies:

add_action('admin_init', 'z_init');
function z_init() {
	$args=array(
		'name' => ('my_taxonomy_01' && 'my_taxonomy_02')
		);
	$output = 'names';
	$z_taxonomies = get_taxonomies($args,$output);

For more details about how this was done you can also look up “get_taxonomies” in the Codex, see:

https://codex.www.ads-software.com/Function_Reference/get_taxonomies

Wellest wishes!

Just checking back in with an update, in case anyone else might be engaging with this issue too. I tried a bunch of things to try to get it to work, but couldn’t seem to.

In the end, I’ve just let the out-of-the-box Media attachment section that comes with WordPress remain as is as THE thing that deals with all the images for the site I’m working on — and then I’ve created a custom taxonomy and used a plugin to attach images to the taxonomy. This way I can just select from that taxonomy array, the images to associate with a post. It’s a bit of a different solution that I expected, but it’s working out.

Thank you, the print_r code you gave me is extremely insightful, and helpful — I know I’ll use a chunk of it to get this working. I still don’t have it completely working yet, but I’ll post back here a bit later on my progress and if I have any further questions. Thank you again!