44 Comments

  1. Ashley

    I would LOVE changelogs.

    I build my own themes so this doesn’t affect me personally but I also host sites for my clients, and those clients may use free WordPress.org themes. I perform updates for my clients and I hate not knowing what has changed in the theme. My client may not care, but as a developer/maintainer, it would be really useful for me to know what’s going on and what this update is actually doing.

    Report

  2. Alec Kinnear

    I would suggest Justin is right: many WordPress developers are such sloppy skateboard kids that his parody comment would come true. On the other hand, automatically generated diff logs by default with space for explanatioin would be very helpful.

    Thanks for letting us know about this discussion.

    Report

  3. Matt

    Yes!

    Report

  4. David Decker (deckerweb)

    Absolutely YES!

    And I really wonder, why they still have no changelogs yet…!

    Report

  5. Austin Pray (@AustinPray)

    > Do WordPress.org Themes Need a Changelog?

    Is a fat dog heavy?

    Report

  6. Matt Cromwell

    Justin Tadlock says: ” Changelogs are largely develop tools…” honestly, Themes are developer tools as well, and when you manage many many websites with many different themes on them, you want to know whether they are updated with important security updates or just adding ads into the options page. Changelogs are best practice for code. I honestly can’t think of one reason to ignore them completely that is justifiable.

    Report

  7. Carl Hancock

    Users don’t look at plugin changelog’s either but I can’t picture anyone in the community saying they are unnecessary for that reason.

    Are changelog developer facing? Absolutely. Does that mean themes shouldn’t bother with them? Absolutely not.

    Report

  8. mike finley

    The lack of any description of what has changed when a theme is ‘updated’ is a strong disincentive to update – If there’s no description of what has changed in the theme why would I spend time changing it and potentially having to undo the change because I don’t like the changes?

    Report

  9. viriv (@concepura)

    Pls yes!
    I hatte updates, but sometimes i check changelogs to see what is interesting for me….

    Report

  10. Satrya

    Some peoples/users still not use child theme to make changes to the parent theme, so change logs might be helpful for them. I guess so.

    Report

  11. Bradley Allen

    I fully agree with Ashley, Matt, David, Matt, and others: Yes!

    Report

  12. Shapeshifter 3

    Arf, Arf, Arf, Arf, Arf !

    I give 5 out of 5 barks FOR mandatory theme changelogs.

    Let the Lowest Common Denominator WordPress users get their websites up-and-running from WordPress dot com, where the least amount of setup thought is required. WordPress dot org users go there because they want more control over their individual websites. Let them have it.

    Report

  13. Justin Tadlock

    I don’t think I was clear with my joking comment, especially when not in the context of previous discussions. I just don’t think change logs in their current format hidden away in the theme folder serve much purpose for the average WP user. TRT’s primary focus is centered on users. Everything we do starts there. Now, you add in support for displaying change logs prior to theme update directly into core, it’s a whole different matter. We have something that’s useful, informative, and fits into our primary focus.

    We’ve been asking for a similar readme standard for themes (like plugins) for years, which would have included change logs. The primary ticket for change logs has been sitting there for the last 16 months. The ticket for the readme standard has been stale for 18 months.

    Maybe TRT should pioneer this standard. I’d rather see some movement in core first. Maybe this discussion will kick-start that movement. We probably need TRT and some of the core leads communicating.

    Report

  14. jteague

    Why does it seem so many WordPress devs argue that users are either too lazy or too stupid to take advantage of information about products they use? Gets on my nerves, seriously.

    Yes, changelogs are important, vitally. Yes, people who merely maintain sites use them all the time as reviews prior to pretesting an update. I have paid programming interns that do just that who are not quite yet engineers, but learn through maintainenance and support. We mentor them on the process, which includes prioritization of updating client sites. And that starts with changelogs.

    And yes, mere mortal users also check changelogs. Maybe not with the frequency of other groups, but that’s not the point. Please, when did WordPress devs become such snobs?

    Report

  15. Scott Hartley

    Changelogs should be required by all developers. The main issue is that users are not able to get any insight other than trial and error unless a developer provides a changelog.

    Frankly, every developer should have a changelog for their themes, and plugins.

    Report

  16. Rick

    Wherever there is code a changelog should be in place. NOT for things such as layouts, styles etc. Thats simply ridiculous unless VERY brief.

    For example “Added 16 CSS classes” is fine. Dont need define each one and what they do. Added “3 column Layout” fine.

    Fixed this/that in code. Fine.

    In other words, a brief synopsis of updates. Especially given that the TMT is working to get away from getting function per se away from themes.

    Report

  17. chuck reynolds

    I believe it’s in everybody’s best interest to have a dated changelog for everything.

    Report

  18. Ryan Hellyer

    I don’t care too much either way. My only request though, is that themes and plugins use a common standard. Having a different system for each would be a bit weird IMO.

    Report

  19. mac2net

    Yes please

    Report

  20. Johnathan Lyman

    +1 for a changelog. I hate having to figure out on my own via digging and chewing on .diffs to figure out why WordPress is telling me my theme is out of date.

    Report

  21. Andre

    I believe a Change Log should be part of the theme package because it’s like software, every change should be noted, especially for those who do check them out. There’s also instances where a web designer or webmaster is managing a client’s website; should there be an update, it’s important to see what changes were made.

    I’ve also seen themes get radical changes, so it wold be nice to know what was changed. As one who designs and develops WordPress themes, I like to include a changelog, in both my free (at wordpress.org) and commercial themes.

    For the most part, the average user of themes from the repository probably does not read or even realize there’s a change log, but again, there are some who know it and read them.

    Report

  22. Emil Uzelac

    This would be even better if the change log would be integrated into core like plugins do i.e. ` View version `1.4 details` before the update :)

    Report

  23. Ajay

    You have them for plugins, why should themes be different? I always want to know what is updated in anything that I am upgrading, either in the WordPress world or outside

    Report

  24. sonja

    Why is this even a question? Of course themes should have changelogs. IMHO lack of them is a dangerous bug :)

    Report

  25. Otto

    Yes, we’ll get there. My goal is to get them working with a full readme, not just a changelog. Easier in the long run to unify things. But, there are structural differences and we also must solve existing problems before tackling new ones. Slow, and annoying. I know. I agree. Small steps leading to big steps.

    Report

  26. alex

    The need more than a changelog, they need some semblance of version control as well. My feeling is that theme version numbers should be matched to the highest wordpress version that they actively support (ie, have been tested for). So most themes now should be 4.2.xxxxx, where the .xxxxx incremental is the only part of the version number controlled by the developer. The rest should be automated in some manner. Perhaps even tie the version number to a changelog system, where the developer explains the change and wordpress assigns the version number to match.

    It would make it much easier to search through themes to find the ones that are actually updated and current, and not out of date. So many themes are just not maintained.

    Report

  27. Marcelo

    Simply put, if you are serious working with WP for your customers, then you MUST know what are you installing or modifying every time an update is applied.

    And yes, themes should also show a visible link to the changelog. Even more, themes should also show the its last update full date to allow you to determine if that theme is so old that could be obsolete and hence break your site.

    Report

  28. Ændrew Rininsland (@aendrew)

    Haha, whuuuut? Only in WordPressland would people actually question the value of changelogs. Are people seriously suggesting that a diff is an adequate replacement? Seriously?

    Here’s an idea — instead of getting bogged down in terms of whether people would use them or not, or use them properly, or whatever, how about let’s just build the functionality in and if people use them, they do?

    And if you’re worried people are going to be shitty developers and not use the facilities available to document their code and inform their users — maybe that has something to do with the fact there are practically no processes within the WordPress community for cultivating good open source developers and the whole development is experience seems stuck in about 2006? Maybe if the plugin submission process was a little bit more than a lint and a rubberstamp, maybe people would be more invested in their projects and might take the time to do things like fill out changelogs?

    I’m getting off topic — yes, ffs; changelogs!

    Report

  29. Matthew Dorey

    YES. And have a pro-forma so that inane cut/pasting could be avoided.

    Report

  30. Dot 07

    Part of me is amazed this conversation has to take place because I see multiple marketplaces thriving which are focused on complex themes and plugins and all of them provide changelogs for both themes and plugins.

    The other part of me knows that the only people who seem to still believe users of WordPress aren’t smart enough to know or have the desire to have anything other than pre-configured software to make a website easily are the developers of WordPress and their teams. And therefore, they need to be educated as to what the current trends are.

    I don’t know about most of the people here, but I look through a lot of plugins regularly and based on the usage of those plugins there are many, many people downloading plugins with complex settings areas. Of course, the arrangement isn’t the same for themes so there isn’t the same information available for them. But seeing the market place platforms selling loads of themes, I would venture to say the trend is the same for themes as well.

    I know a lot of “developers” who started developing because they weren’t satisfied with the little bit of control and flexibility of WordPress for their own projects. That goes for themes as well as plugins. With over 37,000 plugins along side of a lot of themes (the number isn’t readily available on WordPress due to the different structure of the themes area) changelogs are vitally important.

    Maybe some day the WordPress team will accept the fact that their beliefs about users needs to change quite a bit. We aren’t the same group they started out with. We want to know and we need to know what is being changed in themes to help us know what potential issues we might face when there is an update without having to run comparisons through diffmerg to find out. Not all updates are equal. Changelogs are vitally important for many reasons.

    IMHO, WordPress repository for themes is one of the weakest links in the project. Themes hosted on WordPress.org need to be handled the same way plugins are handled.

    I find the comments coming from WP team members to be both irritating and arrogant. Listen to the users for a change.. log.. You aren’t as unique as you used to be.

    Report

  31. Jeffrey

    Yes, a changelog is needed.

    Report

  32. Garrett W.

    I would LOVE for themes to have changelogs. I invariably tend to add custom CSS (through Jetpack) to themes, and I’d love to know what to expect when I hit the Update button.

    Report

  33. Luke

    Yes! I always check changelogs and I know lots of others that do too.

    Love them or hate them, changelogs are the most user friendly approach. People want to know “what’s been changed?” and “will it break my stuff?”

    Report

  34. Joe Marsden

    I would absolutely love to see changelogs for theme updates – I don’t know how this isn’t a thing already! Just so long as the changelogs didn’t contain something like “1. Security fixes” and that’s it. What a waste of time that is.

    Report

    • Alec Kinnear

      Just so long as the changelogs didn’t contain something like “1. Security fixes” and that’s it. What a waste of time that is.

      Good point, Joe. Apple almost single handedly (okay with a little bit of help from Microsoft) has made changelogs completely useless.

      The changelogs should contain a detailed diff file and require notes from the developer on each groups of changes made. The diff bit could then be folded in for the changelog (to make it shorter) but with the possibility of folding the code back out.

      Anything less and we’ll get the nonsense Joe feared. Changelogs which don’t tell us anything.

      Report

  35. Shapeshifter 3

    Theme Updates vs Changelogs vs Unneeded Plugins:

    What if a Theme’s developer adds functions or features to his/her product that end users previously had to install a plugin to facilitate?

    If Easy Access to a Changelog doesn’t exist, the end user may continue to use an unnecessary plugin unaware that the theme itself now provides the desired function or feature.

    The end result may be plugin conflict with the updated Theme, or just duplication of code.

    Report

  36. CJx

    In my view a changelog is so fundamental there shouldn’t even be a debate on whether or not one is needed. We’re talking software behaviour here and I, for one, want a heads-up on what impact an update may have before it happens.

    I check plugin changelogs beforehand and this has saved me from several embarrassing moments and at least one critical event. Not so with themes unfortunately :o(

    I remain frustrated that this basic document management tool is not present for themes. I have resorted to running fully-functioning and up to date localhost sites in parallel with those online, so I can update themes in a managed environment first, and get to the changelog before updating for real.

    Report

Comments are closed.

%d bloggers like this: