Error
 

OK Danny I've managed to get on here with Firefox.

Doesn't work with Safari, all other sites are still OK.

This is the safari notice
Warning: require_once(./includes/vba_cmps_include_error.php) [function.require-once]: failed to open stream: No such file or directory in [path]/includes/functions.php(2937) : eval()'d code on line 21

Fatal error: require_once() [function.require]: Failed opening required './includes/vba_cmps_include_error.php' (include_path='.:/usr/local/php5/lib/php') in /home/www/dannystewart.com/forums/includes/functions.php(2937) : eval()'d code on line 21

I'm also getting this on firefox now when I click on my favourites link. Only reason I'm still here is because I pressed the back button a few times to get it working!

Is it anything to do with the fact that I'm getting linked to the Home Page and not the forum index? Same error comes up on the google link! I'll try to cancel cookies! If I don't reply I can't get on here so send me an email.

jamieminty@hotmail.com

Think I've just cracked this! Index page works fine but not the Home page!

you should use Firefox instead of Safari anyway.

Filthy lies. Let the man use whatever he wants. I use Safari on both Mac OS X and Windows. It's faster than Firefox and renders pages more nicely, and that's pretty much all I care about.

Jamie, I'm looking into this problem right now, but it's a bit difficult to investigate considering it doesn't happen for me (and I've tested just about everything). I'll email you and let you know what I come up with.

I appear to be having the same problem as well.

[quote]
Warning: require_once(./includes/vba_cmps_include_error.php) [function.require-once]: failed to open%

Okay, I've fixed it using a really ugly solution. I uninstalled the vBadvanced CMPS portal solution we were using to provide the dannystewart.com/ main page, and instead replaced it with a barebones HTML redirect to the forums. I realize it's not exactly elegant but it should make the problem go away. I hope no one was relying on the portal for anything.

o rly

Firefox ftw...

Thanks

Yeah really. This was not a Safari issue, it was a site issue. I saw it using Safari, Pete saw it using Chrome, and even Jamie saw it using Firefox. Browser had nothing to do with anything.

And if it actually were some kind of browser-specific site error, Safari actually displaying the error and bringing it to my attention would be significantly better for me and my users than Firefox's "ignorance is bliss" policy. So Safari + 2 in this particular case. One is just hypothetical but it gets a point for it anyway.

Yes, Firefox ftw, and Safari ftmw. :P

You're welcome.

I was about to say, no trouble on this end with accessing the site via Safari.

Well it's all fixed now anyway.

Well this is an efficient place.

I do try to keep things running smoothly. :)