The two names are very similar, and it's easy for a user to assume the memcached extension should be installed because the plugin is named memcached, and the readme mostly references memcached. That's made worse by the fact that the plugin directory moved the Installation instructions to a secondary page ~5 years ago, so the link to the extension is not as obvious as it used to be.
The general changes and FAQ address #38. The FAQ also addresses #148.
Related #6 / #133. This PR won't be needed if that one is merged, but there's currently no movement there. This is a simple readme-only change, so I think it's good to do this now, and then it can be revised if that PR is merged.
The two names are very similar, and it's easy for a user to assume the
memcachedextension should be installed because the plugin is namedmemcached, and the readme mostly referencesmemcached. That's made worse by the fact that the plugin directory moved the Installation instructions to a secondary page ~5 years ago, so the link to the extension is not as obvious as it used to be.The general changes and FAQ address #38. The FAQ also addresses #148.
Related #6 / #133. This PR won't be needed if that one is merged, but there's currently no movement there. This is a simple readme-only change, so I think it's good to do this now, and then it can be revised if that PR is merged.