I've had the same problems and I've noticed that I've had to post a sentence at a time and hit "preview" in order to find whatever word or character was causing the issue. It's putzy, but it works.

__________________
Il mio aliscafo è pieno di anguille

I was messing with fanfiction last night and being technologically challenged, I didn't get very far.

__________________
I'm writing a book. I've got the page numbers so far...

The one sentence at a time thing isn't so bad when it's a short piece, but I can see how it would be a pain in the rear on a longer one. The one thing about FF.net that I would be leery of is that they censor stuff over there.

__________________
Il mio aliscafo è pieno di anguille

Thanks to ChrisW, I got an invite to Archive of Our Own, and I like what I see over there, especially the interface and the ease of posting. I also posted up my "Too Hot for Zark" fic over there.

http://archiveofourown.org/works/3796981

__________________
Il mio aliscafo è pieno di anguille

Woohoo. I have more invites available if anyone wants one.

__________________
Eagle Whisperer

Hey folks, could you send Julieann a detailed description of what's happening when you're trying to post? Am talking to her in chat and she doesn't seem clear on the issue. For tech stuff like this it's good to give a total step by step breakdown.

__________________
Eagle Whisperer

It's not a browser issue. It's a permission issue with the server that the site runs on.

This is what happens (and this is as detailed as I can get):

When I try to post a story to gatchfanfic.com, I get a 403 (Forbidden) error. This happens regardless of whether I hit submit or preview.

In order to work around this and post, I have to post my work one sentence at a time and hit "preview". If the preview shows up, then I post the next sentence. If I get another 403 error, then I have to post that sentence one word at a time until I find what word in my text triggered the 403 error.

One word that I've noticed consistently triggers a 403 error is the word "having". There are other words that do this, but having is the only one that I've consistently seen trigger this error. It's not always words. It can be punctuation.

I did some googling on this and I found that the error could be caused by one of two things--the executable's permission is not set to 644 or there are security settings on the hosting end that are not set correctly.

__________________
Il mio aliscafo è pieno di anguille

Boeke, I know Julieann has her hands full, but if the script needs to be updated, I have a few friends who ran another archive with the efiction-based script. If this is the direction that Jules wants to go, I can get ideas and suggestions on the best way to proceed with the upgrade.

I do know a few issues with the newest platform with the older versions are this: transfers of stats and reviews, transfer of registrations (mostly with high volume of non-author members), and worst case is manual transfer of stories and reviews or loss of reviews.

The biggest issue with manual transfer is registration, especially of non-active members. Other than losing numbers and reviews, manual transfers can be done quickly with a few volunteers, and asking active members to transfer their own stories.

Another option, is creating a new archive, keeping the current read only, and allow active members to move stories in their own time. This is the easiest for the webmistress and admin, but it does depend upon server space and available bandwidth.

__________________
Perspective Alters Reality

Becky, did you ever hear anything back from Julieann?

__________________
"The heart has its reasons, of which reason knows nothing." -- Blaise Pascal

Oh, that's not good. I'm sorry to hear that.

__________________
"The heart has its reasons, of which reason knows nothing." -- Blaise Pascal