I have taken in a lot of feedback regarding some changes I'll be making around here. Keep in mind that the majority of the changes are with the back-end CMS, for automation and cr@p like that, however the biggest change is that the Ninjaforum is going to be moving.
For those of you that have glazed thru the "About Ninjalane" article you will know that back in the early days, the Ninjalane Message Forum was an integrated part of Ninjalane.com. Then when the site moved to a dedicated hosting provider the old forum software was ditched for the feature rich and "free" forum, PHPBB.
The downside to this was given the architecture differences between Asp.net (the main site) and PHP (the forum) there was no way for me to combine the sites so http://www.ninjaforum.com was acquired and became the new home of the Ninjalane Message Forum.
In hindsight it would seem that spinning the forum off to a separate domain with different graphics was a mistake. So with recent advances in my coding library I am once again able to combine the 2 sites together and actually share some information between them.
So here is what will be changing.
1) http://www.ninjaforum.com will be going away in favor of http://forums.ninjalane.com
2) Shared login session between the forum and the main site.
3) direct discussion links when an article is published.
4) the "Blogs" mod will be going away in favor of a new subforum (better exposure)
5) Ninjalane.com header graphics and links will be applied to the forum so everything will look seamless
Future updates
1) Email notifications regarding new article postings to be sent to all forum members.
2) Advertisements added to the forum
So what does this mean for you?
Aside from the obvious change to your bookmarks.... Nothing, Your forum experience should get better as a result.
All of the accounts, posts and replies will be retained. Some links to various forum posts from other sites will break, but that is to be expected.
During this transition PHPBB will be upgraded to the latest version which unfortunately breaks the KittenAuth implementation. With any luck KittenAuth will be back but it’s not likely to happen any time soon.
I'll update this thread as things progress along. Look for the revisions to take place in the next week or so.
If you have any comments or concerns please post them here or send me a PM. I look forward to hearing from you all.







