Okay, this isn't a true mod where there's code to download - but it does discuss a mod that you can implement on your own.
Let me ask this question. Do you currently have multiple copies or versions of Snitz running? Maybe multiple websites, different databses?
Let me explain my situation. On the forum (using SQL server) I'm currently working on, I have a development, a staging, and a live production copy. I also work on the forum code at both home and work. In the past, I would either forget not to copy over the config.asp file or forget to make a copy of it. The first time I would access the forum, I would get an error and be directed to the setup page. This also happened the first time I was going to test and demo the forum on the production server. DOH!!
Well, realizing that this was a major pain and also that in the future, I could have a couple of websites on different servers running this forum, I knew that I had to do something. So here is what I did:
I first created a folder called inc_sitespecific.
I then created an include file that held the db type and connection string code from config.asp. I replaced that section of code in the config.asp with this:
'#################################################################################
'## SELECT YOUR DATABASE TYPE AND CONNECTION TYPE (access, sqlserver or mysql)
'#################################################################################
%><!--#include file="inc_sitespecific\site_connectioninfo.asp"--><%
I also had a requirement to display the parent websites standard navigation (header and footer) in the forum. This would change between sites, thus for the header, I included this in the inc_top.asp file:
<!-- SITE & FORUM HEADER -->
<!--#include file="inc_sitespecific\site_header.asp"-->
This also works great for unique sets of meta-tags, differing privacy policies, terms, etc.
By doing something like this, it allows you to maintain a portable core of Snitz code that can be modified and then quickly copied to different websites. You don't have to worry about the connection string and other unique elements as long as the inc_sitespecific folder doesn't get copied over during the update.
Topic Locked
Posted - 25 March 2001 : 12:49:28
