May 3rd, 2012, 1:05 PM
Hi guys,
Sorry for the wait on this. Turns out it was a Core problem. Just upgrade to 2.2.5 and the problem should go away!
- Ben
Sorry for the wait on this. Turns out it was a Core problem. Just upgrade to 2.2.5 and the problem should go away!
- Ben