Loading Profile...
Draft did not save
After about 30 minutes oif writing I saved my draft. At this stage I had a look around hte community and when I returned to my draft I was unable to locate it, nor was I able to write a new story.
Using Firefox 3.5.3
Using Firefox 3.5.3
I’m particularly displeased in a way that enticed the complete obliteration of the nearest piece of hardware that is non mission critical.
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
The best answers from the company
-
There's a good chance that it was because you'd been writing longer than the site's session timeout and your draft got trashed in the process.
Unfortunately, that's an issue that I resolved about two weeks ago (keeping sessions alive as long as you have a browser window active on the site), so it's quite possible that that's what caused the loss of the draft.
I'd ask that you try and save a draft in Firefox on your account again and see if it works this time. The problem would have occurred no matter what browser you were using, mind you; it's a server-side issue that should no longer be a problem.
The oops page is just the default error page, 404 or 500 HTTP errors will bring it up. Most often it's just a typo in the URL, other times it could actually be an error. If you see an error message, please forward it my way as per the instructions on the page. I'm only one person developing and operating the site, so getting feedback with error message helps me solve recurring issues that I can't easily reproduce myself.
Cheers,
-nick
The company says
this answers the question
-
As much as it might surprise you, Protagonize is developed entirely in Firefox, and Internet Explorer is tested afterwards. If you're having trouble, go through my instructions above and let me know if you're able to see your drafts.
If you let me know what your user name is, I can check and see whether or not any partial drafts are present for your account.
Thanks,
-nick
I’m confident
The company says
this answers the question
-
Hi Admin,
If you let me know what your account handle is, I can take a look and see what happened to the draft. Drafts (if they saved properly) should be accessible from the "My Drafts" option in your Profile menu.
I’m confident
The company says
this answers the question
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Admin,
If you let me know what your account handle is, I can take a look and see what happened to the draft. Drafts (if they saved properly) should be accessible from the "My Drafts" option in your Profile menu.
I’m confident
The company says
this answers the question
-
-
Inappropriate?As much as it might surprise you, Protagonize is developed entirely in Firefox, and Internet Explorer is tested afterwards. If you're having trouble, go through my instructions above and let me know if you're able to see your drafts.
If you let me know what your user name is, I can check and see whether or not any partial drafts are present for your account.
Thanks,
-nick
I’m confident
The company says
this answers the question
-
Inappropriate?The site didn't just 'lose' a draft. It simply did not function in firefox. It does not surprise me that the site was designed in firefox. Ghoistofanonion is my handle. And the site appear to be funcitoning with firefox although I often get the oops page.
I’m meh
-
Inappropriate?There's a good chance that it was because you'd been writing longer than the site's session timeout and your draft got trashed in the process.
Unfortunately, that's an issue that I resolved about two weeks ago (keeping sessions alive as long as you have a browser window active on the site), so it's quite possible that that's what caused the loss of the draft.
I'd ask that you try and save a draft in Firefox on your account again and see if it works this time. The problem would have occurred no matter what browser you were using, mind you; it's a server-side issue that should no longer be a problem.
The oops page is just the default error page, 404 or 500 HTTP errors will bring it up. Most often it's just a typo in the URL, other times it could actually be an error. If you see an error message, please forward it my way as per the instructions on the page. I'm only one person developing and operating the site, so getting feedback with error message helps me solve recurring issues that I can't easily reproduce myself.
Cheers,
-nick
The company says
this answers the question
-
Inappropriate?I was under the ipression it was a one man setup. Which is an impressive feat. I will in future (When i am using the site more) send you the error's.
I’m Better
EMPLOYEE
