In the past, I had installed the extension Cm_RedisSession on Magento 1.7.0.2. The relevant extension had been installed under the directory /app/code/local/Cm/RedisSession. Afterwards, I upgraded to Magento 1.9.4.5 which has native support for Redis sessions. So, I ended up with having code under both the following directories:
/app/code/local/Cm/RedisSession
/app/code/community/Cm/RedisSession
The file /app/etc/modules/Cm_RedisSession.xml seems to be that of Magento 1.9.4.5 which has codePool=community, and not the one of the extension Cm_RedisSession I got from github which had codePool=local. However, after conducting some checks I got the impression that the Cm_RedisSession extension actually used by my Magento installation is the initial one installed under /app/code/local/Cm, and not the native one installed under /app/code/community/Cm.
So, I have 3 questions:
The native Magento Redis Session extension optimizes session storage using Redis, enhancing performance and scalability.
To resolve the issue you're facing with Magento and the Cm RedisSession extension, you'll want to ensure that only the native version in is being used. You can disable or remove the version in to avoid conflicts. For more detailed assistance with this process, Whetstonez IT Consulting offers expert services that can help streamline your Magento setup and resolve such configuration issues effectively.