There seems to be an issue submitting the Fivestar admin form when the wigdet is a basic, outline or oxygen color widget that's anything but the default. Any browser ends up with a blank screen, and Safari reports the infamous "Operation could not be completed. kCFErrorDomainCFNetwork error 302" error, which would lead me to investigate problems with DNS.

Comments

nodiac’s picture

nodiac commented

This is happening on our project. Works fine on our local machines but not on the production server. We're getting the white screen of death after submitting any custom configuration, but submits fine if you use the non-configurable images.

White screen is appearing even with error reporting turned on.

Can anyone suggest a workaround?

quicksketch’s picture

quicksketch
he/him
commented

Yikes, I've never seen a similar error. The "Works fine on our local machines but not on the production server" situation could make this difficult to correct. My only suspicion is that your server does not have the GD image library installed, as Fivestar requires it to properly create custom star widgets.

robertdouglass’s picture

robertdouglass commented

This is a bizarre one. I'm seeing this on a live site WITHOUT fivestar where the whole site is absolutely fine, but all of the individual blog posts get the kCFErrorDomainCFNetwork error 302 error. Googling doesn't help much.

boldfish’s picture

boldfish commented

Is this a Mac?

I'm having the same problem with Safari on Leopard 10.5.5 and also issues uploading images with Firefox, and IE under parallels

(nothing to do with Drupal or Fivestar, but just a general PHp file upload issue - googling suggests Leopard network issues.)

robertdouglass’s picture

robertdouglass commented

It's not a browser problem. It's a server problem. How your browser reports it might be different, but every time I've encountered this error, I've been able to prove that it is a server problem. This most recent time it meant that Apache was segfaulting. Telnet received no return header. IE 6 said it was a 404 error (although no header ever reached IE) The kCFErrorDomainCFNetwork bit seems to be Safari specific, but people who see this should immediately start investigating server failure.

quicksketch’s picture

quicksketch
he/him
commented
Category: bug » support
Status: Active » Closed (fixed)

Oddly all posts about "kCFErrorDomainCFNetwork error 302" mysteriously stopped sometime in December last year. My guess is that this was a browser problem, since everyone affected reported using Safari, and suddenly no one is having the problem any more, probably after Safari was updated by a newer version.

Top Google hits:
http://echofaith.com/2008/06/beware-of-kcferrordomaincfnetwork-error-302
http://discussions.apple.com/thread.jspa?messageID=8146693
http://drupal.org/node/301021 ;)

Anyway, unless someone can reproduce the problem today with a new version of Safari/Mac OS X, I think this is closed.