WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 4 years ago

#20531 closed enhancement (wontfix)

Version No. removed from theme name in themes

Reported by: kcssm Owned by:
Milestone: Priority: normal
Severity: minor Version: 3.4
Component: Themes Keywords: needs-patch 2nd-opinion ux-feedback
Focuses: administration Cc:

Description

The version no. of themes is removed in 3.4 from the themes page. There was a direct display of theme version no. in 3.3 and was a great help for developers with lots of theme with different versions. But now we have to click on Details to see the version number, which is just a bit time consuming. Hope you would consider my request.

Thanks
Sanam

Change History (11)

#1 @jane
8 years ago

Why would you keep multiple versions of a theme on a live install? Themes should always be kept up to date for security reasons. I'm not closing this as wontfix because I want to see what others think, but for the end user, version numbers usually are not particularly meaningful since they just have one copy installed. A notice there on the theme screen when a theme had an available update, on the other hand, would be really helpful for end users.

Do people think having multiple versions is more common that I've stated? If so, we can revisit. Otherwise, a developer-centric plugin to display version number by default would be my suggestion.

#3 @nacin
8 years ago

I would agree with Jane, but I've also seen situations where this could affect users very badly. For example, Headway and Thesis both key their theme directories by version. (thesis_18, headway_20, etc.) This then allows users to upload the zip of the new theme and activate it. It doesn't make the best user experience, because you end up with 15 themes on themes.php that are all the same. And it doesn't make the best developer or security experience, because Headway had to write code to recurse through all of their previous directories to remove Timthumb. But, I could see how this could affect users who are already stuck in situations like these.

#4 @kcssm
8 years ago

I am theme developer and there are users with different theme versions installed and I have to check each of those versions. So instead of having to go and click details of each theme to see the version number, it would be more easier and faster to just see that in the front page. Even as a user, if i have to update a theme I would like to which version i have. Since I have many themes in the themes directory, its tedious to view the version number as of now in 3.4.

#5 @nacin
6 years ago

  • Component changed from General to Appearance

#6 @nacin
6 years ago

  • Keywords needs-patch 2nd-opinion added
  • Milestone changed from Awaiting Review to Future Release
  • Type changed from feature request to enhancement

#7 @nacin
6 years ago

  • Component changed from Appearance to Themes
  • Focuses administration added

#8 @obenland
6 years ago

We could make it dependent on whether WP_DEBUG is true.

#10 @chriscct7
5 years ago

  • Keywords ux-feedback added

#11 @dd32
4 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

5 years on from removing the version numbers, and I just can't see the need for a user to see the version number anymore.

Theme authors giving updates as zips which are then uploaded with a new folder name have hopefully moved to automated updates now, and those who run multiple versions of the same theme should be far fewer.

I'm marking this as wontfix as a result of the above.

Note: See TracTickets for help on using tickets.