| Author |
 Topic  |
|
GhettoDalaiLama
Junior Member
212 Posts |
 Posted - 10 August 2002 : 15:37:52
|
from previous versions?
say 3.3.03?
is it as easy as replacing the ASP code or are there significant DB changes that need to be made? |
|
|
RichardKinser
Snitz Forums Admin
USA
16655 Posts |
Posted - 10 August 2002 : 15:50:49
|
| upload the files and then run setup.asp to update your database. |
 |
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 10 August 2002 : 15:53:01
|
of course there's some editing to config.asp (you can't use your old file) too, but that and what Richard said will do it.
Upgrading can be done, once the files are uploaded, in less than 2 minutes 
It's installing MODs (if you want to do that) that'll take most time, and that's done after upgrading so doesn't really count... |
|
|
|
GhettoDalaiLama
Junior Member
212 Posts |
Posted - 10 August 2002 : 15:53:04
|
| thanks Richard |
|
|
|
GhettoDalaiLama
Junior Member
212 Posts |
Posted - 10 August 2002 : 15:54:13
|
| lol FrutZle... we post 3 seconds apart! wow. |
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 10 August 2002 : 15:56:44
|
doesn't happen often... next time we should try to post at exactly the same second  |
|
|
|
Rasyr
Junior Member
USA
199 Posts |
Posted - 10 August 2002 : 21:48:25
|
question about the updating the DB part....
I am currently running version 3.3 with all the security patches, and a lot of mods. What I was planning on doing was to create a secondary folder next to the current forum folder and install 3.4 there, and then re-install all my mods, and redo the look so that it matches the current forums.
Up above, somebody mentioned updating the DB. Now will updating the DB break my ver.3.3? Or will I have to create a backup DB, and hook into that while updating my files for v3.4 and then when I am ready to go live, change over to the live DB and rerun the various DB change things again?
|
**TANSTAAFL** |
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 10 August 2002 : 21:52:01
|
it won't mess up your database. I did the upgrade of my forums in the way you mentioned and didn't use a database copy. Then if someone posts in the "old" forums, the topic won't show correctly in the new forum (it won't be on top). That's only one thing I noticed. There might be more "problems", but I was kind of in the middle of getting the new forums looking the way I wanted them to.
But, generally speaking it shouldn't give any problems as no fields are removed, only added. |
Edited by - Roland on 10 August 2002 21:52:27 |
|
|
|
gorman
Starting Member
Italy
47 Posts |
Posted - 11 August 2002 : 10:10:59
|
quote:
Originally posted by RichardKinser
upload the files and then run setup.asp to update your database.
Hmmm... ok. But I have a lot of mods installed (your Avatars, Active Users, Sticky Topics, Private Messages, translated Italian asp files, IP ban, some extra smilies).
So let's say I download the new version (3.4), upload it on my server and update my database using setup.asp. What will be the result?
My forum with all messages, all users, in English and working ok? Isn't there a risk that some of the mods will conflict with the new features of 3.4 (Sticky topics for instance)? |
Edited by - gorman on 11 August 2002 10:33:20 |
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 11 August 2002 : 10:23:10
|
You will lose all MODs from the ASP files so you'll have to reinstall them. Problem in that is that you can't simply use the MODs for 3.3.x in the 3.4 files because they're changed quite a bit.
Since the tables of the MODs won't be "called" in the ASP files, they can't give any conflicts. However, they might give some problems when topics are added and those tables aren't updated, and you install the MODs later and view those topics. This is because the forums will try to retrieve information from the MOD tables that won't be present. You'll have to work around that if you indeed get problems.
As for the Sticky topics MOD: that's a standard feature in 3.4, so you won't have to worry about that. Also all posts will stay in the database, aswell as the colors and other configuration settings you have now.
Yes, the forums will be in English. There's not much you can do about that except translate the files (again). |
Edited by - Roland on 11 August 2002 10:24:19 |
|
|
|
gorman
Starting Member
Italy
47 Posts |
Posted - 11 August 2002 : 10:30:57
|
quote:
Originally posted by FrutZle
You will lose all MODs from the ASP files so you'll have to reinstall them. Problem in that is that you can't simply use the MODs for 3.3.x in the 3.4 files because they're changed quite a bit.
No problem with that... it's in the nature of things
quote:
Since the tables of the MODs won't be "called" in the ASP files, they can't give any conflicts. However, they might give some problems when topics are added and those tables aren't updated, and you install the MODs later and view those topics. This is because the forums will try to retrieve information from the MOD tables that won't be present. You'll have to work around that if you indeed get problems.
Hmmm... the first thing I can think of is to completely delete the tables related to MODs that won't be installed anymore... Do you think it will be better and it will eliminate the risk of what you are describing? Although... for Kinser Avatars... my users will be hating me and reinserting all 400+ of them will be a nightmare.  
quote:
As for the Sticky topics MOD: that's a standard feature in 3.4, so you won't have to worry about that. Also all posts will stay in the database, aswell as the colors and other configuration settings you have now.
Great! Thanks for the info.
quote:
Yes, the forums will be in English. There's not much you can do about that except translate the files (again).
Yes, I gave that for granted, it wasn't part of my question... I was actually stating the obvious .
|
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 11 August 2002 : 10:33:39
|
| I'd leave the tables, edit the database to allow zero length entries (empty fields) in the fields for the MODs and then when you reinstall the MODs at a later time, you can add a simple check to see if the field is empty or not. If it's empty, don't display anything, otherwise show it. That's only 4 lines of code |
|
|
|
gorman
Starting Member
Italy
47 Posts |
Posted - 11 August 2002 : 10:36:30
|
quote:
Originally posted by FrutZle
I'd leave the tables, edit the database to allow zero length entries (empty fields) in the fields for the MODs and then when you reinstall the MODs at a later time, you can add a simple check to see if the field is empty or not. If it's empty, don't display anything, otherwise show it. That's only 4 lines of code
FrutZle... you completely lost me here  
I'm not ASP savy at all... do you think you could provide a "dumber" explanation? Thanks for all the help, I guess it must be a pain to have to deal with an illiterate like me... |
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 11 August 2002 : 10:49:24
|
It's no problem at all.
The basic idea is like this:
You have several fields in your database. As long as the ASP files don't "look for them", they're not really used. Now if you insert information in a row (like when you post a new topic) but leave some fields empty (they're not used by the ASP files 'cause the MODs aren't installed in them, right?) they might throw a fit 'cause they might not be set to allow zero length (in other words, there has to be something in them).
You'll have to open the database, look for the fields that belong to MODs, and check that they're not required and will allow "zero length" or a "null value".
If you do that, they won't give any problems until you install the MODs in 3.4. That's when you'll have to add some codes to the ASP files to check that IF a field is empty, it shouldn't show anything, otherwise it should show you the information from the field.
The second part is unimportant right now because you're not installing the MODs yet. But make sure you ask for help with this when you are going to install the MODs in 3.4
I hope this explanation is a bit clearer |
|
|
|
gorman
Starting Member
Italy
47 Posts |
Posted - 11 August 2002 : 10:59:39
|
quote:
Originally posted by FrutZle
The basic idea is like this:
You have several fields in your database. As long as the ASP files don't "look for them", they're not really used.
This I can understand. quote:
Now if you insert information in a row (like when you post a new topic) but leave some fields empty (they're not used by the ASP files 'cause the MODs aren't installed in them, right?) they might throw a fit 'cause they might not be set to allow zero length (in other words, there has to be something in them).
Ok, here is where you lose me. This "they might throw a fit" is referring to...? The fields in the database? So this problem is related to the Database, not to the ASP files?
quote:
You'll have to open the database, look for the fields that belong to MODs, and check that they're not required and will allow "zero length" or a "null value".
Ok, I'm using Access... once I open the database what's the specific action that I have to take (this starts looking like "Snitz for a dummy gorman"...)?
quote:
If you do that, they won't give any problems until you install the MODs in 3.4. That's when you'll have to add some codes to the ASP files to check that IF a field is empty, it shouldn't show anything, otherwise it should show you the information from the field.
Here you mean the ASP files of the MODs? Or all the ASP files of the forum, for every MOD I install?
quote:
But make sure you ask for help with this when you are going to install the MODs in 3.4
You can count on it!
quote:
I hope this explanation is a bit clearer
It is, thanks for your time, really! |
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 11 August 2002 : 11:20:58
|
quote:
Originally posted by gorman
quote:
Now if you insert information in a row (like when you post a new topic) but leave some fields empty (they're not used by the ASP files 'cause the MODs aren't installed in them, right?) they might throw a fit 'cause they might not be set to allow zero length (in other words, there has to be something in them).
Ok, here is where you lose me. This "they might throw a fit" is referring to...? The fields in the database? So this problem is related to the Database, not to the ASP files?
What I mean with "throwing a fit" is that you'll get an error that the field(s) is/are not allowed to be left empty That's a problem in the database due to the setting of the fields.
quote:
quote:
You'll have to open the database, look for the fields that belong to MODs, and check that they're not required and will allow "zero length" or a "null value".
Ok, I'm using Access... once I open the database what's the specific action that I have to take (this starts looking like "Snitz for a dummy gorman"...)?
Once you open the database, you find the fields that were added when you installed the MODs. Then you go into the design view (I think that's what it's called) and make sure the fields are set to allow zero length.
quote:
quote:
If you do that, they won't give any problems until you install the MODs in 3.4. That's when you'll have to add some codes to the ASP files to check that IF a field is empty, it shouldn't show anything, otherwise it should show you the information from the field.
Here you mean the ASP files of the MODs? Or all the ASP files of the forum, for every MOD I install?
I mean that you have to make some small modifications to the MOD codes that you'll have to add to the ASP files when you install the MODs (confused yet?  ) |
|
|
|
Topic |
|
Topic Locked
