I'm having a very weird issue with making posts with Google Chrome. I can't tell if it's an issue with the site, or with the browser.
When I press "Post Message" after typing out a response, instead of posting it, my computer is opening up a window asking me to download/save a file to my computer. The file is Post.pl.
Any idea what might be causing this? I had to make this post with Firefox, because I can't write anything with Chrome as a result.
Edited, Jul 12th 2010 3:22pm by Darqflame Lock Thread:
·Theme
- Forums
- Cross Site
- Site and Forum Feedback
- Google Chrome
Google ChromeFollow
#3
Jun 18 2010 at 12:10 PM
Try logging out and back in with Chrome.
#4
Jun 18 2010 at 12:34 PM
Test
I had tried clearing all the browser data earlier (cookies and such) and that didn't fix it. Just logged out/in again, and now it's working properly. It's been kind of an on-and-off thing. Earlier, the error happened, then it stopped for a few hours, then it started again.
Perhaps logging out again fixed it? Here's to hoping that it's all good now. What an odd error.
Thanks for the help guys : )
Edited, Jun 18th 2010 2:38pm by Eske
I had tried clearing all the browser data earlier (cookies and such) and that didn't fix it. Just logged out/in again, and now it's working properly. It's been kind of an on-and-off thing. Earlier, the error happened, then it stopped for a few hours, then it started again.
Perhaps logging out again fixed it? Here's to hoping that it's all good now. What an odd error.
Thanks for the help guys : )
Edited, Jun 18th 2010 2:38pm by Eske
#5
Jun 18 2010 at 5:53 PM
Weird. That's exactly what used to (maybe still) happens when you try to post in a locked thread.
Fynlar wrote:
Chew is being a lot more level-headed regarding the whole issue, which is strange because he's probably drunk.
#8
Jun 20 2010 at 2:37 PM
EDIT: Nope, broken.
As far as I can tell, clearing the browser makes it work for exactly one post. Any subsequent post seems to be broken again, bringing up the download Post.dl window instead of entering the post. Perhaps I'll try changing the Google Chrome version next.
Edited, Jun 20th 2010 4:37pm by Eske
Edited, Jun 20th 2010 4:57pm by Eske
#10
Jun 20 2010 at 3:14 PM
Okay, I think I fixed it.
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
#11
Jun 20 2010 at 11:03 PM
Eske wrote:
Okay, I think I fixed it.
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
We'll have to keep an eye on the next stable release just in case, but dev is dev for a reason :)
#12
Jun 21 2010 at 8:28 AM
Nizdaar wrote:
Eske wrote:
Okay, I think I fixed it.
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
We'll have to keep an eye on the next stable release just in case, but dev is dev for a reason :)
Yeah it's working fine now. I was initially surprised, because I've been running the dev channel for a while and never had a problem with ZAM. Oh wells.
#13
Jun 21 2010 at 8:40 AM
Nizdaar wrote:
Eske wrote:
Okay, I think I fixed it.
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
We'll have to keep an eye on the next stable release just in case, but dev is dev for a reason :)
#14
Jun 21 2010 at 11:35 AM
Lubriderm the Hand wrote:
Nizdaar wrote:
Eske wrote:
Okay, I think I fixed it.
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
I regressed to the stable version of Google Chrome (I had been running the dev channel). Seems to be fine in stable, so far.
Edited, Jun 20th 2010 5:15pm by Eske
We'll have to keep an eye on the next stable release just in case, but dev is dev for a reason :)
I'm not about to spend our time fixing google chrome's problems in a dev branch. If we did that every time there was an issue, we'd never get any actual work done around here. If it's a problem on our website, it's going to be a problem on others and chrome will have to fix it.
#15
Jun 21 2010 at 10:29 PM
I know, I'm a very happy customer, I was just being a douche.
You cannot post in a locked topic!
Recent Visitors: 72
All times are in CST
Anonymous Guests (72)
- Forums
- Cross Site
- Site and Forum Feedback
- Google Chrome
© 2024 Fanbyte LLC