[wp-hackers] Possible OT: shot in the dark

[Alex Blackie]

And if it's on GoDaddy's end - there's no hope. They'll blame it on you, 
your ISP, or anyone else who might be loosely affiliated with you 
because even if it is their problem, they won't admit it.

I've learned this from experience.

- Alex -


On 10-05-18 4:49 AM, Tim Moore wrote:
>   On Tue, May 18, 2010 at 12:12 AM, MarvinC<marvinc at gmail.com>  wrote:
>
>    
>> Warning: filesize() [function.filesize]: stat failed for /tmp/phpaAk9Pb in
>> /home/content/s/l/a/slapstick/html/wp-admin/includes/mu.php on line 15
>>
>> Warning: filesize() [function.filesize]: stat failed for /tmp/phpaAk9Pb in
>> /home/content/s/l/a/slapstick/html/wp-admin/includes/mu.php on line 15
>>
>> Warning: Cannot modify header information - headers already sent by (output
>> started at
>> /home/content/n/u/s/nusolutions/html/wp-admin/includes/mu.php:15)
>> in /home/content/s/l/a/slapstick/html/wp-includes/pluggable.php on line 868
>>
>>      
> Marvin,
>
> That looks like a file permission problem (that the system doesn't have read
> access to the files) or a potential block that GoDaddy has on that PHP
> function call. If the plugin worked on a non-GoDaddy server and now doesn't
> work on GoDaddy, then the problem exists on GoDaddy's end.
>
> Hope that helps,
>
> Tim
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>