DemonGoddess

When adding a story, the category list is a drop down menu as it is. IF we did such a thing, it'd be way down on the list of the must do to bring the archive up to date. At the moment, you can simply open the category up in a separate tab in your browser anyway, so it's really not necessary to add a pop up.

Just glad to hear you're doing okay!

As to avatars, if for the archive, bear in mind that if the file name exceeds 15 characters, it will be deleted. As to merging pictures in to one, which programs do you have to work with? Each program has different capabilities to do what you want to do, and depending on what you have, is what kind of stuff you can actually do.

The archive is where you publish your stories. As this post was originally in the naruto sections, this subdomain (if for naruto stories) is where you'd publish to. If publishing for other fandoms, either navigate to the correct subdomain (i.e. inu, anime2, books, etc), or use the jump menu in your user cp to navigate to it. Select the subdomain name, and click go, then add the work.

So, the techs advised me to wait an additional week, while 3.2.1 is being readied for release. With the mass release, a number of bugs were found, and 3.2.1 fixes them. When I given them the permissions, again, to perform the upgrade for me, I will post that here. At that point, we can expect the forum to be upgraded anytime from the day I give the permission, to up to two weeks later. They are horribly overloaded with upgrade reqs, so I understand the wait time.

Updated 7/31/11 10:26am EDT Underage Users in queue for age check/processing - 0 Deleted for the first time - 397 Deleted, turned 18 and allowed to return - 436 Confirmed 18 or older - 571 Inconclusive results - 415 Deleted for posting for a minor - 22 OLD minors in queue to process - 375 OLD minors processing complete - 1012 Accounts taken over - chronic returning minors - 6 Accounts taken over - posting for chronic returning minors - 2 Total accounts looked at - 3236 Trolls/Flamers/Spammers monitoring behavior in archive - 3 accounts processed for this - 233 accounts taken over - 9 Total accounts looked at - 245 Plagiarism Monitoring for arrival to this archive (known plagiarists offsite) - 6 in queue while checking - 4 resolved - 135 permissions given - 47 unsubstantiated - 47 co-authored, verified - 27 uncited sources (not yet corrected) - 14 uncited sources, corrected - 90 accounts taken over - 28 Total instances looked at - 398 Other TOS Violations in queue - 1 resolved - 324 Total instances looked at - 325 Duplicate Users in the archive in queue - 0 merged/processed - 595 Shared and duplicate accounts allowed/documented - 32 *Total instances - 627 Orphan and Duplicate stories repaired/processed in queue - 1 processed - 123 Total stories looked at - 124 Invalid Email in queue - 4 processed -267 Total accounts looked at - 271 *This number does NOT include the total accounts per user merged. Number is also subject to change depending upon age verification. If they are minors, they're not merged, they're deleted. This will also apply in other areas where it turns out the member in question isn't so much what they were being reported as (i.e. troll), but actually underage. _____ I'm going to revisit the topic of underage users. You'll all have noticed that the numbers have increased significantly. This is, in part, due to the clean up. One of the things we do look for, are old underagers. If, for some reason, you login and find that you're missing stories and they're not hidden, chances are we've found data indicating you were underage at the time of posting. Because the site is owned and hosted in the United States, we cannot allow anything to stay that was or is posted by a minor. This applies to active users who are now of age, but were underage at time of account creation, and adding data to the archive. It doesn't matter if the data has been sitting there for years. It still has to be deleted if it was posted when the user was underage. One other thing about the age restrictions for this site. I know we have many users from overseas where age restrictions are not the same. Again, regardless of where you, the user, are; we have to abide by the age restrictions in the US, which is WHY users must be 18 or older to use any part of this site.

Archive profile This one was reported by the original author. Buh-bye!

So this one managed to kill two birds with one stone... Not only did this person lift a story from someone, but that person who the story was lifted FROM is underage. Archive Profile Proof

The upgrade will be happening some time today. There may be some hooks which don't translate over to the new version. If so, I'll have to either wait for an updated version, or reinstall. I'll find that out when the upgrade is finished.

The FAQ is pre-existing, and will not be added.

You should now be able to post from an actual word doc, docx. I tested it, and it added, with NO loss of your chapter data. The only other weird thing I'm seeing is a string at the very top that has a series of binary code, then something saying "html code", etc. That's a simple fix. Delete it, it has no affect on your data. So, now I have to chase down why it does that, but I think that may very well be a Word issue with the RTE itself, rather than the system issue that was happening where exceptions had to be made in Apache. Chasing down another thing is irrelevant, at least you can all add chapters and publish stories from your docs in native Word format!

Sounds like you had a drop in connection. When that happens, where your connection tries to drop, or slows down; php pages will only load partially. The same happens with html pages, but not quite as drastically.

Here's the link to it on AFF

One other thing (which I will let them know as well) it appears to be specific to c/p from a word document. I can c/p from any other program and have it add. Just not word. I also let the other tech know, in case it's something in the conf file for the rte. She installed and configured it, so it's possible there's something else at play as well. Although I doubt it, as it was all working before the upgrade and file migration. Heard back from Nexcess as well, and they are checking the perms at the root level on their end.

ty . Wish I could fix this myself, but it's an Apache command that the hosting company has to add exceptions to. They're the only ones with access to that.

Ok, this has to do with mod_security options, and has to be handled by the hosting company. I'll get that fixed by them ASAP

We'll start with my machine specs AMD Phenom II X4 805 (quad core) 8GB DDR RAM 1 TB HDD OS - Windows 7, SP 1 Connection - broadband --- I will be doing this test in the original subdomain, as that appears to be where you're all having issues. --- Safari v 5.1 build 7534.50 Firefox v 5.01 Internet Explorer 9.0.0 Chrome 12.0.742.122 Opera 11.50 Build 1074

No hack. I tried looking you up, going by the name you used to post, and cannot find a profile which even remotely resembles that pen name. What subdomain was this story in, so I know which part of which document to look in, to see if there was a TOS violation?

As the techs for Invisionpower are horribly backlogged, they asked if they could just go ahead and do it, rather than schedule a time. I expect the upgrade will take place some time within in the week. In any case, when the upgrade is being done, you will get a series of errors while it happens, including being unable to access the forum at all. Past experience with this software and major upgrades tell me that I expect that time to last no longer than an hour, when they're doing it.

Just got home from work, it'll be about 1/2 hour then I'll start test adding with the chapter data sent to me, and see if I can recreate the problem.

Could you make your responses to the tech support issue about this? That way it's all in one place, pls. thanks!

One thing which needs to be addressed, is that with the hardware and DNS changes, any user visiting will have to reset their cookies. The cookie strings are no longer valid. That being the case, if you've not done that, I'd expect unexpected behaviors from any of the software. To do this, you clear history, cookies and etc in your browser. CLOSE the browser. Restart it. You will have to re-do the age verification page, as it is a cookie setter.

One thing I forgot to ask about, as the data has been migrated to a new dedicated server, this means that your cookies for the archive very likely need reset. They would no longer be valid. Have either of you tried clearing your cookies, closing the browser, restarting it, and then posting?

I'll be checking the documents sent to me after work. One other thing, you may need to clear your cookies for the archive. This is a new machine, so the data was transferred from the old one. As a result, unless you clear your cookies, I expect most will have issues, now that everything is pointing to the new machine.