Show theme path in ms-themes.php and ms-sites.php?action=editblog in network admin

Description

ms-themes.php and ms-sites.php?action=editblog leaves me guessing as to where each theme is. Please show the filesystem path, under the WordPress root folder, where the theme is.

I think this is especially important for network sites. At least in my case, we had to develop a few child themes that are subtly different from each other, and it would be helpful to immediately know where on the filesystem each theme is. Right now I have to inspect each child theme to remember which one corresponds to what I see in the themes list.

Summary
changed from Show theme path in ms-themes.php and ms-sites.php?action=editblog to Show theme path in ms-themes.php and ms-sites.php?action=editblog in network admin

Wait a second, this isn't for "end users" or "non-technical users". This enhancement is for system administrators who deal with administration of a WordPress Network, which may have many themes. That's why I put this ticket in the Network Admin category. Sorry if my original post didn't make this clear.

It's difficult to figure out which theme corresponds to what directory without WordPress explicitly showing it to us.

After talking to Ryan in #wordpress-dev I would recommend closing this as a wontfix again. I don't think this makes sense for the majority of the users is already a filter in place for you to add the info in your use case.

After talking to Ryan in #wordpress-dev I would recommend closing this as a wontfix again. I don't think this makes sense for the majority of the users is already a filter in place for you to add the info in your use case.

Huh? I am asking for more information to be added to /wp-admin/network/themes.php, not for the ability to filter stuff.

I'm confused. Apparently we want this product easy enough for non-technical people to use, and we do that by forcing these people to customize delivered PHP files to get information that will be essential for large WordPress networks with a lot of themes. I'm not seeing the logic in this.

I'm confused. Apparently we want this product easy enough for non-technical people to use, and we do that by forcing these people to customize delivered PHP files to get information that will be essential for large WordPress networks with a lot of themes. I'm not seeing the logic in this.

I'm not asking you to hack any core files. I simply don't see the benefit (for the majority of the users) of adding this to the WordPress core. I understand your use case and that is why I suggested that you write a 10 line plugin to add the info you want.