This website is a ****ing joke
- Thread starter CyYoung31
- Start date
50PoundHead
Hessmania Forever
I'm getting those (2 today) as well. I don't like (but don't mind) getting spammed with miracle cures for the gout or whatever, but when it's advertising links for child porn, I think the administrators need to get to the bottom of this BS. I'm not that serious a guy, but this is total crap and tars everyone here.
bravesfanMatt
Steve Harvey'd
Are you getting emails or private messages. I don’t think I am getting anything.
I'm working on it.
I haven't had power thr last 5 days thanks to Helene. But I am trying to find an experienced vbulletij software person to patch it up.
bravesfanMatt
Steve Harvey'd
it will be over tonight and we can all stop posting for a few months.. maybe the DB errors can be resolved by the time the Braves fire all their coaches/managers...
Tapate50
Well-known member
I think the website is tipping its posts.
bravesfanMatt
Steve Harvey'd
I predict this site won't survive the off season. what are other locations. I hate reddit, so that is not an option for me personally.
WaitingFor2017
Well-known member
Reddit is the pits. You say one negative thing about Snit, and your inbox will have 20 idiots after you thinking they are the smartest people on the board.
chop2chip
Well-known member
A database error on a vBulletin website can be caused by a variety of issues, such as corrupted database tables, misconfigured settings, or problems with your database server. Here are some steps you can take to troubleshoot and fix the issue:
1. Check the Error Message
• The error message often provides clues about what went wrong. Note the details, like which table or query failed.
• If the error message is unclear, enable debugging mode to get more information:
• Open the config.php file in the /includes/ directory of your vBulletin installation.
• Set the following:
$config['Database']['debug'] = true;
2. Verify Database Connection Settings
• Open your config.php file in the /includes/ directory and ensure the database connection settings (host, username, password, and database name) are correct.
• Example:
$config['Database']['dbname'] = 'your_database_name';
$config['MasterServer']['username'] = 'your_database_username';
$config['MasterServer']['password'] = 'your_database_password';
$config['MasterServer']['servername'] = 'localhost'; // Or the actual database server name
3. Check the Database Server
• Make sure your database server (e.g., MySQL) is running and accepting connections.
• You can check this from your hosting control panel or by using a command line if you have access.
4. Repair Corrupted Database Tables
• Use phpMyAdmin or a similar tool to repair any corrupted tables:
1. Log in to phpMyAdmin.
2. Select your vBulletin database.
3. Check all tables and choose “Repair table” from the dropdown menu.
5. Check Database User Permissions
• Ensure the database user has adequate permissions to access and modify the database tables.
• Permissions needed include SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, and ALTER.
6. Optimize the Database
• Use phpMyAdmin or a similar tool to optimize the database. This can help improve performance and resolve minor issues.
• In phpMyAdmin, select all tables and choose “Optimize table.”
7. Restore from Backup
• If the issue persists and you have a recent backup of your database, consider restoring from the backup.
• Make sure to back up the current database before performing any restoration, in case you need to revert.
8. Update vBulletin
• Ensure that your vBulletin installation is up to date. An outdated version may have compatibility issues with the database server.
• Check for updates and follow the instructions provided by vBulletin to upgrade.
9. Check for Add-ons or Plugins
• If you’ve recently installed or updated a plugin, it might be causing the issue. Disable all plugins and see if the error persists.
• You can do this from the Admin Control Panel if accessible or by editing the database directly to disable the plugins.
10. Contact Your Hosting Provider
• If none of the above steps work, the problem might be with your hosting environment. Contact your hosting provider for support, as they may need to check server-side issues or adjust configuration settings.
If you continue to experience problems, you may need to consult with a vBulletin expert or a developer familiar with database troubleshooting.
1. Check the Error Message
• The error message often provides clues about what went wrong. Note the details, like which table or query failed.
• If the error message is unclear, enable debugging mode to get more information:
• Open the config.php file in the /includes/ directory of your vBulletin installation.
• Set the following:
$config['Database']['debug'] = true;
2. Verify Database Connection Settings
• Open your config.php file in the /includes/ directory and ensure the database connection settings (host, username, password, and database name) are correct.
• Example:
$config['Database']['dbname'] = 'your_database_name';
$config['MasterServer']['username'] = 'your_database_username';
$config['MasterServer']['password'] = 'your_database_password';
$config['MasterServer']['servername'] = 'localhost'; // Or the actual database server name
3. Check the Database Server
• Make sure your database server (e.g., MySQL) is running and accepting connections.
• You can check this from your hosting control panel or by using a command line if you have access.
4. Repair Corrupted Database Tables
• Use phpMyAdmin or a similar tool to repair any corrupted tables:
1. Log in to phpMyAdmin.
2. Select your vBulletin database.
3. Check all tables and choose “Repair table” from the dropdown menu.
5. Check Database User Permissions
• Ensure the database user has adequate permissions to access and modify the database tables.
• Permissions needed include SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, and ALTER.
6. Optimize the Database
• Use phpMyAdmin or a similar tool to optimize the database. This can help improve performance and resolve minor issues.
• In phpMyAdmin, select all tables and choose “Optimize table.”
7. Restore from Backup
• If the issue persists and you have a recent backup of your database, consider restoring from the backup.
• Make sure to back up the current database before performing any restoration, in case you need to revert.
8. Update vBulletin
• Ensure that your vBulletin installation is up to date. An outdated version may have compatibility issues with the database server.
• Check for updates and follow the instructions provided by vBulletin to upgrade.
9. Check for Add-ons or Plugins
• If you’ve recently installed or updated a plugin, it might be causing the issue. Disable all plugins and see if the error persists.
• You can do this from the Admin Control Panel if accessible or by editing the database directly to disable the plugins.
10. Contact Your Hosting Provider
• If none of the above steps work, the problem might be with your hosting environment. Contact your hosting provider for support, as they may need to check server-side issues or adjust configuration settings.
If you continue to experience problems, you may need to consult with a vBulletin expert or a developer familiar with database troubleshooting.
It's being worked on.
I'm changing to more secure servers.
The guy I'm working with is juggling projects, but he's done a test import so far to the new software/servers.
Trying to retain most of the look of the current forum. Should be ready to go by spring training.
zitothebrave
Connoisseur of Minors
I'm representing the new Government agency, Citizens United Need hTtpS or CUNTS for short. We need you to get compliant or we'll send our best man to shut you down.
