[stardotstar]

Thanks Deceptor !

So, please help me ensure that I have this correct...

If I comment out the line

$config['Datastore']['class'] = 'vB_Datastore_Memcached';

from the vB config.php
BUT leave the other memcached lines in the file as is then memcache will not be used by vB's natively coded datastore - which you state is sub-optimal -
BUT AT THE SAME TIME switch vBOptimise's cache setting to memcache then we will still get memcache performance enhancements for all "customised datastore" and therefore won't be as good as having the vB native datastore using memcache PLUS the customised datastore through vbOptimised...

Not sure I got that down properly, will do some testing and see if I can get my head around it. I think that what you are suggesting will just bring up the original issue that prompted you to ask if I had the memcache setup properly in vB config.php to begin with...

Will

I appreciate the support very much!



[UPDATE]
Yes, as I currently have the memcache off in vB's config.php to prevent the wierd error; I have reenabled memcache as the optimisation method in your product and get the same/following results when I run the system test:

Running Test: Connection to memcache
Test completed successfully
Running Test: Store Cache
Your Opcache Operator extension is functioning, however it is unable to store data. Please check your extension configuration.
Running Test: Fetch Cache
Your Opcache Operator extension is functioning, however it is unable to store data. Please check your extension configuration.
Running Test: Flush Cache
Test completed successfully

In this state I can confirm that I can edit and save posts without the "maxloggedin" error showing.

I take it that this means that the product is going to have NO effect and that I need to get the vB side sorted before I can proceed.

In which case falling back to filecache is my next best option>?