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 95
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 95
From trying to reregister a login that already existing.
Along those lines, can I get a password reset over there? I don't remember what I set up when I set it up. Which I know, was, like, three days ago. But it's been a rough few days.
So, also, should I reset one over here now? Or is it irrelevant because we'll migrate soon? Or is it futile because it's still being keylogged?
Irrelevant. I'm mostly worried about the FTP accounts and stuff.
Okeydoke, and nevermind about over there, I think I worked it out.
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 95
on maintain users. But it still comes up okay.
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 95
On 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.