Finally discovered conflict with aMember Pro - 6 months later Hi, we tried(demo), aMember Pro on a professional site approximately 6 months ago and were forced to abandon the trials without success after struggling with unexplained performance issues and high loads. However, recently, while doing some log maintenance, I found that the aMember variables would not play nice with xCache through vBulletin which would end up sending multiple requests across our entire processor array as a result. With this in mind, I wondered if there was any way to exclude or adjust the aMember queries to work properly with xCache. If so, I we would still be interested in integrating aMember on this site.