Forum Replies Created
In reply to: Deleted Admin now has no keymaster
i resolved this. I realised the bb_capabilities listed was for a user as listed by their userid which I overlooked. I looked up wp_user for the userid of the new administrator and everything is working again.
nevermind. seems the objects are overly generic. i’ll have some patch it up to work.
I think you may be confused _ck_. memcache has it’s uses like php op_code. It does not take alot for it to have a benefit and the same applies to memcache. However I am not asking for a suggestion on avoiding memcache. I would like to see a better handling of objects in the same way you create a prefix for a database. If you set a large pool for memcache say 1gb. The idea of setting another instance and monitoring it with startup script gets a little bothersome especially when an array can be used to mitigate the possibility of one failed instance to drive your site down. In short I should say you don’t usually start another mysql to house a database nor would it be useful to do that with memcache.
Thanks samhaurs again. I just want to be sure there weren’t objects that are generically named that can be seen across bbpress installations like administrative or personal details that should be separate that some are improperly written to cache much like wordpress mu does at the moment.
you are a lifesaver sambauers. I am using object cache but it’s not deeply integrated . The only other question is do you happen to know if you have to set a key (if you can set a key) to prevent object sharing. I know this is a problem with wordpress mu. I wish this was documented somewhere.