Back to Community

Why Isn't the Members Plugin Changelog Updated?

Content

If you're a user of the 'Members – Membership & User Role Editor Plugin', you may have noticed that the changelog sometimes lags behind the latest plugin updates. This is a common point of confusion for users who want to know what changes, improvements, or fixes are included in a new version before they update.

This article explains why this happens and what you can do to find the information you need.

Why the Changelog Might Be Out of Date

Based on community discussions, the primary reason for an outdated changelog appears to be an oversight in the plugin's release process. On multiple occasions, users have reported that the changelog.md file within the plugin and the online version on GitHub were not updated immediately after a new version was pushed to the WordPress repository.

The 'Members – Membership & User Role Editor Plugin' team has acknowledged these reports and typically updates the changelog shortly after being notified by the community. This suggests the issue is not a lack of transparency but rather a procedural step that is sometimes missed during deployment.

How to Find the Information You Need

If you find yourself looking at an outdated changelog, here are a few steps you can take:

  1. Check Again Later: The changelog is often updated within a short period after a community member points out that it's missing. Refreshing the page a day or two after an update may reveal the completed notes.
  2. Review the GitHub Repository: While the changelog.md file might be outdated, the GitHub commit history can sometimes provide a more technical, real-time log of changes. You can view the repository here: https://github.com/caseproof/members.
  3. Ask in the Support Forum: As seen in the sample threads, politely asking for the changelog to be updated in the plugin's support forum is an effective way to get the team's attention and a quick resolution.

Staying informed about updates helps you manage your website's compatibility and security. While the delay can be frustrating, the historical pattern shows that the information is made available once the oversight is corrected.