Quote:
Originally Posted by RadioactiveMan
Losing content wouldn't have to happen. Drupal software development is my job and migrating content from the current system to it is certainly possible. No comment on the amount of effort though; it wouldn't be small. I'm not sure if that makes a ton of sense though; if you make an equivalent feature in Drupal for each current feature so the old content can be moved to the new site, have you just built an awkward vBulletin 3.8 clone instead of the shiny new thing you actually wanted?
One attractive thing to me about having a Drupal site is that it's so much easier to keep up to date. I've seen vBulletin's update process and it's absolutely revolting. Drupal actually does really well here, especially since Drupal 8, and it would make it easier to keep current.
|
Back when the subject of upgrading the site came up the last time, the younger members tended to be least resistant to big changes, as to be expected. Many of the older members wanted some changes, but generally liked the overall format of what we have. Again, this is to be expected. I fall in the "older" demographic, but being in IT all my career, I have to roll with the changes to stay employable.
I am assuming this vBulletin site uses MySQL and Drupal supports it as well. My guess is that the data migration would not be easy and there is a risk of the loss of content. I never used Drupal, so you will have to provide the answers, but what do you see right off the bat that will not migrate? Attachments used in posts? What about the URL links? Would user accounts migrate cleanly, or would there be a re-registration process?
Quote:
Originally Posted by RadioactiveMan
I'm turned off by the idea of removing the chatbox. To me, it's a critical part of the site. But that was eight years ago, so maybe it's not that critical anymore.
This option is appealing because updating vBulletin is a horrible chore that should be reserved for punishing violent criminals. Someone else doing that job is a pretty good deal.
Has a worst-case scenario been discussed? If we really can't contact Ben to renew or take over this domain and server, should we make alizeecanada.com this month so there's a way to continue, even if we lose the existing content?
|
I like the chat box as well. It's a quick way to send a note to everybody.
It's almost hard to believe that vBulletin hasn't developed a helper app to aid in upgrades.
The worst case scenario that we brushed on lightly is starting over from scratch with a brand new site, brand new domain. We hope to avoid that situation, and would rather keep things exactly the way things are right now instead of having to start over.