Quarterbore
05-03-2006, 08:12 PM
My forums are not so huge that this is essential yet but it seems that it would be logical that some type of Archive database and forum code should be possible with vBulletin. What I would like is the ability to have a second database (on the same server would even be OK) where old forum forum posts could be moved to...
First, lets assume we set up a CRON job that looks for posts that have not had any replies in X-days or longer in forum based on a setting in the Forum Manager.
If the thread has not had any replies in the last X-days, then a script would open that thread and first copy the key thread and post information to an archive database. In addition, extra columns would likely be needed to indicate the "current" forum name so that if in the future forums names would change that the archive would still be usable.
Once the thread has been archived, the original thread would be deleted from the current and active forums. Personally, for an archive server, I would not care about any attachments.
Now, if a person did a search on the active forums and they did not find the information they needed they would have an option to search the archive database. This would be usergroup defined and limited...
The Archive search would work like the advanced search where the member would get a list of forums (generated from the forum name as pulled over when archived) plus have the ability to search via Keyword (subject or all), Username (thread or post), and the rest of the criteria.
To make this more user friendly, an AdminCP tool could be built to rename the forum name of threads in the archive for cases when minor forum name changes occur in the future. Additional AdminCP controls might be needed to make some forums only viewable by some usergroups, ability to delete some archive threads (say someone objects to something in an archive), or ???
When threads are pulled from the archive, these threads would be READ ONLY and they would have a special vBulletin files that would search for them and display them. (Say archivethread and archivepost like in the examples that follow: https://vborg.vbsupport.ru/archivethread.php?t=1 or https://vborg.vbsupport.ru/archivepost.php?p=1).
The big advantage of this would be that the primary forums database would be kept to a smaller size with the older threads getting moved to the archive but old thread information would be saved for the future. The main forum database would still contain all the member information and drive the permissions for who can search or view the archives.
I have looked at the code and tried to formulate a plan on how I could do this but I am just not a good enough coder to do this. I don't personally see this as an impossible task and it seems like a mod like this for larger forums might be useful to reduce some of their server load.
I welcome opinions on the idea and I really welcome someone to create a modification like this...
First, lets assume we set up a CRON job that looks for posts that have not had any replies in X-days or longer in forum based on a setting in the Forum Manager.
If the thread has not had any replies in the last X-days, then a script would open that thread and first copy the key thread and post information to an archive database. In addition, extra columns would likely be needed to indicate the "current" forum name so that if in the future forums names would change that the archive would still be usable.
Once the thread has been archived, the original thread would be deleted from the current and active forums. Personally, for an archive server, I would not care about any attachments.
Now, if a person did a search on the active forums and they did not find the information they needed they would have an option to search the archive database. This would be usergroup defined and limited...
The Archive search would work like the advanced search where the member would get a list of forums (generated from the forum name as pulled over when archived) plus have the ability to search via Keyword (subject or all), Username (thread or post), and the rest of the criteria.
To make this more user friendly, an AdminCP tool could be built to rename the forum name of threads in the archive for cases when minor forum name changes occur in the future. Additional AdminCP controls might be needed to make some forums only viewable by some usergroups, ability to delete some archive threads (say someone objects to something in an archive), or ???
When threads are pulled from the archive, these threads would be READ ONLY and they would have a special vBulletin files that would search for them and display them. (Say archivethread and archivepost like in the examples that follow: https://vborg.vbsupport.ru/archivethread.php?t=1 or https://vborg.vbsupport.ru/archivepost.php?p=1).
The big advantage of this would be that the primary forums database would be kept to a smaller size with the older threads getting moved to the archive but old thread information would be saved for the future. The main forum database would still contain all the member information and drive the permissions for who can search or view the archives.
I have looked at the code and tried to formulate a plan on how I could do this but I am just not a good enough coder to do this. I don't personally see this as an impossible task and it seems like a mod like this for larger forums might be useful to reduce some of their server load.
I welcome opinions on the idea and I really welcome someone to create a modification like this...