Byron just laid back while Mike was doing all the work, huh!SandChigger wrote:Nah.
I'm not sure what Byron is complaining about since it would have been Mike doing all the "work", no?

(Hmm, time to update Hoary Tales

Moderators: Freakzilla, ᴶᵛᵀᴬ, Omphalos
Byron just laid back while Mike was doing all the work, huh!SandChigger wrote:Nah.
I'm not sure what Byron is complaining about since it would have been Mike doing all the "work", no?
On another thread:We went round-and-round with the phpBB help threads and finally spoke with someone there. Then they told us to contact our ISP so we did, time and again, and finally they were able to fix it. I'm asking that they send us the fix so that I have it on file and can give out the information to other users that might encounter it.
A latent bug sounds possible, but I don't get the part about the ISP running the board...I thought they ran the board themselves.We hadn't done anything. Apparently it's some latent bug that pops up from time to time. If you have problems, you'll need to contact your ISP that runs the phpBB board. The problem seems to reside there. Some people never encounter this problem. We were just ...lucky.
Translation: the database size was set too small. Meaning, maybe, that Mike wasn't watching it with the database utility and optimizing it often enough to clear the overhead.Here's the solution, for other phpBB users.
Your database quota has been increased to 300MB. Your software should now be able to write to the database without error. As we discussed on the phone, it appears that your MySQL database is approximately 69MB at this time.
Also, as discussed, in order to increase the database quota, I had to increase the complexity of the database user password. In conjunction with this change, I also updated the connection strings I found for the database in the following files:
/htdocs/phpBB2/config.php
/htdocs/phpBB3/config.php
/htdocs/phpBB30/config.php
The original files were renamed to config.orig.php with the edited files being uploaded as config.php. Per our security policy, we are unable to provide passwords via email, but I have provided you with the new database password by phone. Additionally, your web administrator can get the password from the files mentioned above, or through your Account Manager at www.NetworkSolutions.com <http> .
Please let us know if you have any further questions.
Thank you for your patience.
We hope this update has been helpful. However, if you have any additional questions, or feel that the issue has not been completely addressed, please do not hesitate to email our Technical Support Department at technicalsupport@networksolutions.com <mailto> or call us at 1-866-391-HELP (1-866-391-4357). If calling from outside the U.S. or Canada, please call 570.708.8788
Sincerely,
Network Solutions Technical Support Analyst
I'd say this is exactly what happened. If I had a dime for every forum that's actually been properly maintained, I'd be poorSandChigger wrote: Chalk this one up to a possible latent boardware bug that can become active if your webmaster slacks off on database maintenance.