@littleread1 Unfortunately I had this problem last year and I would never had figured out the problem had I not been with @wpengine