Thank you for taking the time to respond.
I've just recently resolved the issue, and it turned out it was merely a deployment issue and performing a clean-build completely resolved the problem.
Such a silly mistake caused way too much of a headache for me, it seems!