After delving into the code again to do this new update, I found that problem and it has been fixed. The details are listed in the bug-fix section!
