Caerydd
04-09-2006, 09:50 PM
Context: I have a current install of drupal with very little content - you can see it here: http://www.alleria.com/index.php or http://www.alleria.com/engine . The forums are installed on http://www.alleria.com/forums and will remain so. We have a large user base, and it would be nice to NOT have to create separate accounts for website editors, as well as being able to provide Blogs & other features for my subscription users.
1) My account on Alleria is NOT the first account created, although it IS a superadministrator, and I have ftp access etc etc. In Drupal the first account created is a special administrative account, like a superuser - does this superuser correspond with the first account of vbulletin, or can you configure it to connect with another account?
2) I've already created a theme for drupal (as you can see above), am I correct in guessing that this would port directly over to a drupal installation. It all matches, so that isn't a majour concern with me.
3) Modes that absolutely must work for me are glossary, bookmarks, aggregator2 (unless I find another way to promote posts from a news forum to the front page, and then organise them using e-publish) E-publish should also work, as should bio, poormanscron, dba, database, taxonomy_browser, and especially taxonomy_access . ... I'm cutting and pasting a list of my required modules right now - this is more for my records ;)
adminblock
adminrss
aggregator2 Aggregates syndicated content (RSS and ATOM formats) as regular Drupal content.
bbcode Allow the use of bbcode in your posts.
bio
blog APIs.
book
bookmarks
cronplus Calls module-specific hourly, daily, weekly, monthly, and yearly functions.
customerror Enables the creation of custom error pages for 404 and 403 errors.
db_maintenance Executes an OPTIMIZE TABLE query on MyISAM, InnoDB, or BerkeleyDB tables
dba Directly administer your Drupal database.
epublish
glossary Maintain a glossary on your site.
helpedit
image_filter Allow users to reference images from other nodes.
logintoboggan Improves Drupal's login system.
masquerade The masquerade module allows administrators to masquerade as other users.
poormanscron Runs Drupal cron jobs without the cron application.
queue Allows content to be moderated by the community.
statistics Logs access statistics for your site.
taxonomy_access Allows users to specify how each category can be used by various roles.
taxonomy_browser An interface for viewing content grouped by arbitrary taxonomy terms.
taxonomy_multi_edit Apply multiple category assignments at once.
Workspace
Hmmm, lots there, I know some are working from the list on this website.
4) Upgrading to 4.7 seems to be quite painful for a lot of users, I'm guessing you should only upgrade once all the modules you need are upgraded too.
5) Erm....*thinks* right now drupal is installed in /engine. If I install vbdrupal, it shouldn't affect that installation as it will be a separate database. And copying the theme over is pretty easy. How easy would it be to set up vbdrupal without my users seeing? I guess I would have to alter links in the vbulleting template for them to 'see' the drupal installation if they still see the old site when pointed toward http://www.alleria.com/index.php
gah..... *nervous*
1) My account on Alleria is NOT the first account created, although it IS a superadministrator, and I have ftp access etc etc. In Drupal the first account created is a special administrative account, like a superuser - does this superuser correspond with the first account of vbulletin, or can you configure it to connect with another account?
2) I've already created a theme for drupal (as you can see above), am I correct in guessing that this would port directly over to a drupal installation. It all matches, so that isn't a majour concern with me.
3) Modes that absolutely must work for me are glossary, bookmarks, aggregator2 (unless I find another way to promote posts from a news forum to the front page, and then organise them using e-publish) E-publish should also work, as should bio, poormanscron, dba, database, taxonomy_browser, and especially taxonomy_access . ... I'm cutting and pasting a list of my required modules right now - this is more for my records ;)
adminblock
adminrss
aggregator2 Aggregates syndicated content (RSS and ATOM formats) as regular Drupal content.
bbcode Allow the use of bbcode in your posts.
bio
blog APIs.
book
bookmarks
cronplus Calls module-specific hourly, daily, weekly, monthly, and yearly functions.
customerror Enables the creation of custom error pages for 404 and 403 errors.
db_maintenance Executes an OPTIMIZE TABLE query on MyISAM, InnoDB, or BerkeleyDB tables
dba Directly administer your Drupal database.
epublish
glossary Maintain a glossary on your site.
helpedit
image_filter Allow users to reference images from other nodes.
logintoboggan Improves Drupal's login system.
masquerade The masquerade module allows administrators to masquerade as other users.
poormanscron Runs Drupal cron jobs without the cron application.
queue Allows content to be moderated by the community.
statistics Logs access statistics for your site.
taxonomy_access Allows users to specify how each category can be used by various roles.
taxonomy_browser An interface for viewing content grouped by arbitrary taxonomy terms.
taxonomy_multi_edit Apply multiple category assignments at once.
Workspace
Hmmm, lots there, I know some are working from the list on this website.
4) Upgrading to 4.7 seems to be quite painful for a lot of users, I'm guessing you should only upgrade once all the modules you need are upgraded too.
5) Erm....*thinks* right now drupal is installed in /engine. If I install vbdrupal, it shouldn't affect that installation as it will be a separate database. And copying the theme over is pretty easy. How easy would it be to set up vbdrupal without my users seeing? I guess I would have to alter links in the vbulleting template for them to 'see' the drupal installation if they still see the old site when pointed toward http://www.alleria.com/index.php
gah..... *nervous*