The Goat Pen

OK, it appears we may be back to being at least minimally functional. The board will be up and down as I try to fix all the shit that has gone wrong.

what happened?

What I think happened is that Bluehost removed the ability to run PHP version 5 (which I'm not sure if I would have known it was going to cause a problem, so this probably would have happened anyway, but it would have been nice for some kind of fucking notice that this was going to happen so I could determine that this was probably the issue from the beginning), and automatically updated us to PHP 7 which the phpbb board version we were (3.0.11 i think) using does not work with, and that basically killed it completely immediately just from calling "mysql" instead of the "mysqli" calls which are required in PHP7.

So I spent like 4 hours trying to update the forum software to a newer version with zero access to the board control panel or anything, and finally found out that I could at least get the damn thing up and get into the Control Panel just by changing one fucking line of code in one file to "mysqli"

Since then Ive been trying to update the forum software. This is version 3.1.12, it still may not be totally stable with PHP7. I need to get us up to 3.2, but Ive had problems with getting the database to update to the new version since i (apparently) dont have shell access to run commands on our server, and its been timing out when I try to update it using the web based updater that comes with the 3.2 phpbb software. I'm hoping that going through the interim step of updating to this version has at least gotten us to where the board is functional, and that it will also allow the 3.2 update to go through next time I try it.

I've also downgraded us back to the default style and had to remove our custom bb-codes which were apparently calling something that didnt work with PHP7. Any old styles used on 3.0 or 3.1 apparently will not work at all once we update to 3.2 anyway, so that will all have to be redone to get the board to look the way it used to once we update anyway.

What the fuck is happening? Total clusterfuck

auto updating to the next release is garbage

The boat fire was the perfect metaphor for Vols football and this board crashing is a close #2.

Yeah, I got several emails over the past year or more where they were making PHP 7.0, and then 7.1, 7.2, and 7.3 available, but I got nothing on ending PHP 5 or auto updating to 7. I assume thats what happened since I only have the choice for 7.0 through 7.3 now.

They also changed their goddamned cPanel interface recently as well, so not only is everything in a different spot than it used to be and some things as far as I can tell are just gone (Like Site Backup and Restore, which Im pretty sure Im fucking paying for). And so when you google something for help online, it always tells you what you need to do under the old interface, even the links to Bluehosts own support pages.

test

It seems like posting with some of BB codes right now is not working, so if you try to quote somebody, you may get an error that says your post has too few characters. So stick to text for now I guess.

Also, if you try to view a page with old posts that have the bb codes in them as well, the posts will likely not look correctly and you will likely get a bunch of PHP errors at the top of your browser window.

Is this the promised end? Or image of that horror?

If it were done, when 'tis done, then 'twere well
It were done quickly. If the assassination
Could trammel up the consequence, and catch
With his surcease, success: that but this blow
Might be the be-all and the end-all—here,
But here, upon this bank and shoal of time,
We'd jump the life to come.

we need more Vols fans here to make fun of

Carolina could go undefeated in football this year...

Carolina already lost, I watched it this weekend.

Here is the losing Carolina coach being consoled by his vanquisher at midfield.

https://imagesvc.timeincapp.com/v3/fan/ ... =736&h=485

Was it a dream?

Vanquished!

Where is the img2 button?

I'm pretty sure eCat sabotaged the site so that the img2 button would be destroyed