And its also not going to change, its part of the software. Our software code needs to be up to date or we dont get support. That was one of the main reasons why it was changed because our template code was so far out of date, that we needed to bring it up to the vBulletin 3.8 code structure to get support.
Perhaps vBulletin 4 will change things, I do know we are going to have a totally new look as the templates and design for the new software is going to be totally different. I am going to wait out a little bit after vBulletin 4 is released to see if its worth upgrading to before making any changes though.
Perhaps vBulletin 4 will change things, I do know we are going to have a totally new look as the templates and design for the new software is going to be totally different. I am going to wait out a little bit after vBulletin 4 is released to see if its worth upgrading to before making any changes though.
