@dreamxg
17 years, 4 months ago
For anyone else who gets the same error in future, its the WordPress config file, the only way I got round it was to do raw database calls, but including it generates errors.
