OP
- Thread Starter
- #61
Until I can find a consistent revenue stream, we're gonna keep having issues unfortunately.
Forum Updated 5-27-2007
- Thread starter Bob Hubbard
- Start date
Until I can find a consistent revenue stream, we're gonna keep having issues unfortunately.
What would it run in the way of $$ to carry out the server upgrades necessary to eliminate these problems?
OP
- Thread Starter
- #63
About another 150-200 per month plus about 300 for setup.
That's not all that much... For the maintenance side, if you added another ten bucks a month to the Gold Key memberships, wouldn't that take a fairly big chunk out that part of the cost? And for the setup costs, maybe another big supporting-membership drive is in order?
OP
- Thread Starter
- #65
I think the idea is more supporting members and more paid sponsors at the current rates, rather than charging more.
Hey, maybe I'll win the lotto too....then we can get 2 servers.
Hey, maybe I'll win the lotto too....then we can get 2 servers.
So maybe a new `fund drive' with some cool incentives....
Hey, maybe I'll win the lotto too....then we can get 2 servers.
That always works! :ultracool
The last two days when I log in and click new posts it tells me there are none. So I have to select posts in the last 24 hours and search the threads that way. The issue is that if it is a big thread I can only link to the start or end, not to last unread.
I know it is most likely solved with more moeny and more POWER.
Yet, I thought I would give a data point.
Thanks
I know it is most likely solved with more moeny and more POWER.
Yet, I thought I would give a data point.
Thanks
Just got the following message while I was changing pages.
vBulletin datastore error caused by one or more of the following:
Fatal error: vBulletin datastore cache incomplete or corrupt in /includes/init.php on line 213
vBulletin datastore error caused by one or more of the following:
- You may have uploaded vBulletin 3.6 files without also running the vBulletin upgrade script. If you have not run the upgrade script, do so now.
- The datastore cache may have been corrupted. Run Rebuild Bitfields from tools.php, which you can upload from the do_not_upload folder of the vBulletin package.
Fatal error: vBulletin datastore cache incomplete or corrupt in /includes/init.php on line 213
vBulletin datastore error caused by one or more of the following:
1. You may have uploaded vBulletin 3.6 files without also running the vBulletin upgrade script. If you have not run the upgrade script, do so now.
2. The datastore cache may have been corrupted. Run Rebuild Bitfields from tools.php, which you can upload from the do_not_upload folder of the vBulletin package.
Fatal error: vBulletin datastore cache incomplete or corrupt in /includes/init.php on line 213
vBulletin datastore error caused by one or more of the following:
1. You may have uploaded vBulletin 3.6 files without also running the vBulletin upgrade script. If you have not run the upgrade script, do so now.
2. The datastore cache may have been corrupted. Run Rebuild Bitfields from tools.php, which you can upload from the do_not_upload folder of the vBulletin package.
Fatal error: vBulletin datastore cache incomplete or corrupt in /includes/init.php on line 213
1. You may have uploaded vBulletin 3.6 files without also running the vBulletin upgrade script. If you have not run the upgrade script, do so now.
2. The datastore cache may have been corrupted. Run Rebuild Bitfields from tools.php, which you can upload from the do_not_upload folder of the vBulletin package.
Fatal error: vBulletin datastore cache incomplete or corrupt in /includes/init.php on line 213
vBulletin datastore error caused by one or more of the following:
1. You may have uploaded vBulletin 3.6 files without also running the vBulletin upgrade script. If you have not run the upgrade script, do so now.
2. The datastore cache may have been corrupted. Run Rebuild Bitfields from tools.php, which you can upload from the do_not_upload folder of the vBulletin package.
Fatal error: vBulletin datastore cache incomplete or corrupt in /includes/init.php on line 213
OP
- Thread Starter
- #70
I'm trying to find solutions....ones that don't kill me financially, or force me to dumb down the site any more than I have.
This has happened to me almost from the first day I joined... I thought it was supposed to be normal!
OP
- Thread Starter
- #72
I can't recreate that issue, so can't troubleshoot it. It's most likely a cookie issue which would be a setting on your browser, firewall and/or antivirus software. All I can suggest is clearing your cache, and being sure to check the 'remember me' box on login.
The cache-clearing thing is a biggie, for sure. I'm starting to do that every couple of days or so.
Which I do. But I understand the "issues" at hand. Just because I give a data point does not mean I expect a solution. I would rather give a data point so you and others understand that it exists and then we can all move on versus someone down the liine going well if you would have told us we could have done something.
