Thread creation failed. Please find a developer and kick them in the nads.
From trying to maintain the slug on an existing thread. But it did carry out the edit.
'The Train Job'
Do you have problems, concerns, or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Thread creation failed. Please find a developer and kick them in the nads.
From trying to maintain the slug on an existing thread. But it did carry out the edit.
Folder maintenance works but there is no message indicating it has. That's new stuff, so not a bug so much.
Warning: error_log( /home/buff_com/buffistas.com/phoenix/www.buffistas.com/logs/20130607_log.html) [function.error-log]: failed to open stream: No such file or directory in /home/buff_com/buffistas.com/classes/giles.php on line 95On trying to maintain links, and then on the links page. Again, it did in fact work.
line 95 is a real asshole.
Is it still called keylogging if it's not running on the machine where the typing is happening?
But all the passwords are new for b.org.
If you guys keep testing and posting before I have a chance to look at the site myself, I'll never get out from under everything en masse here--many of the issues should be fixed with a few waves of the magic wand, but not until I get home from work.
So no need to keep testing.
However, I would be really curious if the same errors happen at [link] since it has identical code and is against the same database.
Oh. Okay. Headed over there.
Sorry, I've been out of the loop a bit.
No, they do not appear there, with the exception of the "thread creation failed" one. Which is weird.
Shit. I just worked out the other difference--the bufftest code is running on PHP 5.2.17, and buff.com is running on 5.3.x. Gnargh. I guess I better tool it up for 5.3. ::sigh::
So much for resting.
Does PHP really break things that much between point releases?
I do know that there is some documentation I read that I tossed up making the 5.3 changes or the 5.2 ones, and went with the fastest (read 5.2).
There is one problem--it's not writing to the error log properly.
But why is it writing to the error log? It's not doing that on the 5.2 install. b.com is connecting to the 5.2 database, so that's the same. I copied every single file over from the 5.2 install directory structure to b.com, and then took way too long to remember the right path for the error logs. But it's set right now, as are the permissions on the folders, so I'm going to focus on the things that I know are different between the installations first in troubleshooting. Once those are removed, then I'll move on.
If anyone, including you, has any other suggestions for what could be causing different behaviours on two dreamhost sites, I'm all ears. I certainly don't want to do the work involved in checking the code to 5.3. That's very low on my list of ways to wrap up the week.