If you have already applied those fixes, you don't HAVE to upgrade.
I did update setup.asp to insert the new version # in the database when you upgrade, and for MS Access users, I include a section that fixes the FORUM_A_TOPICS.T_MESSAGE & FORUM_A_REPLY.R_MESSAGE fields. They were erroneously set as a TEXT(255) field when they should have been a MEMO field. The Access DB included with this release is already fixed.
Becuase without checking your version change by change, what assurance do they have that you've not introduced additional bugs when you applied the bug fixes ? one small typo is enough to cause a problem.
I doubt its a case of they don't trust that your version isn't 100% fine, but unless they code and release it themselves theres always that risk.
This wasn't meant to be a "All bugs are fixed" version. That is what v3.4 is for.
Most of the changes had already been made in the download file, I just had made the mistake of not incrementing the version # which caused some confusion.
quote: I also included a few other bug fixes, I'll update a list here as I remember them:
This sounds like you included bug fixes in 3.3.04.
My whole point is that you have a lot of dedicated people working to better Snitz, but none of that work is leveraged in any way by the official developers.
You can read into many of these topics an underlying frustration by a lot of the members that the development team doesn't accept feedback or help.
I added them the other day when it was suggested to me that I should update the download file with the Security Related bugs that we have had recently. I went ahead and included a few of the main bugs that we get posts about (the main one being the Allowed Members List bug in post.asp).
Not to start developer bashing but speakign for myself I was a little irritated that I had to get all kinds of fixes from all over the place instead of a released 'fixpack' or some other official looking way. I'm glad that has been taken care of. It might be a good idea to streamline the whole bugfixing proces to make it easier to fix.
(apart from that i'm very pleased with the forum, so a big thanx to the team )
quote:for MS Access users, I include a section that fixes the FORUM_A_TOPICS.T_MESSAGE & FORUM_A_REPLY.R_MESSAGE fields. They were erroneously set as a TEXT(255) field when they should have been a MEMO field.
Is there a way to change this in an existing database? For example a dbs script?
Has the function to compact the DB been omitted for some specific reason? I see the file there, but it's not on the Archive Forum Topics menu with this 3.3.04 version.
Topic Locked
Posted - 16 May 2002 : 22:31:48
)
Nathan Bales