Contrib.social

Memcache(d) version on status report

Open on Drupal.org β†’
Created on 3 September 2020, about 5 years ago
Updated 25 August 2025, 18 days ago

Problem/Motivation

On the status report a Memcached version is shown. This is the version of the php extension installed, not the version of the memcached instance the site it connected to.

Other modules that connect to external services show the version of the running service here.

Steps to reproduce

  • Enable the memcache module
  • Go to the status report
  • See the memcache(d) version

Proposed resolution

Add a small bit of help text here to make it abundantly clear this is the version of the php extension, not the version of the external service.

This is a VERY minor change, but would help people like me that saw no issue on the status report and assumed Memcache was working fine.

Cheers

Tom

✨ Feature request
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom blacklabel_tom

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
  • @xurizaemon opened merge request.
  • Comment 18 days ago β†’
    πŸ‡³πŸ‡ΏNew Zealand xurizaemon Ōtepoti, Aotearoa 🏝

    Yeah, this had confused me in the past too; especially if your PHP makes both `memcache` and `memcached` extensions available, you'll see two versions in the status report with no additional context, which might lead to the understandable interpretation that client and server are both shown there. Instead, the user is being shown two versions.

    We can do what's proposed in the issue currently - add additional text (as shown in screenshot above) to indicate that this is the version of the extension. It would be nice to also add the server version to the status page, but no need for this issue to wait on that.

    Test reports failure on PHPUnit run, but it does not look related to the code changes in this MR.

  • Comment 17 days ago β†’
    πŸ‡³πŸ‡ΏNew Zealand RoSk0 Wellington

    Thanks Chris!

    The changes look good and make sense.

    Pipeline failure is not related to changes here and are addressed in πŸ“Œ Fix tests on 11.2 Active .

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024