77 replies to this topic

[BronxWench]

Actually, if you go into the subdomain you wish to search, the old Search feature is still there, under Member Tools, and it works just like it always has.

[DemonGoddess061]

The rich text editor has been in place for a year. You probably need to update your browser, your java, or both.

Being returned to the story add page tells me that you entered the recaptcha code incorrectly.

[DemonGoddess061]

Html uploads were disabled for security purposes. Why on earth direct html injection was allowed in to the database, I have no idea. Aside from that, the rte for text insert, when it adds data, the data inserted as compared to an html or even a text insert is roughly no bigger than 20k, even with the large chapters. Whereas a large chapter with html as the insert was running upwards of 2MB.

Without knowing what OS, what your hardware, and a few other things, or even what exactly you were doing BESIDES editing/adding to a story, I can't duplicate the issue.

[BronxWench]

The RTE has been a little flukey about centering since it was first installed about a year ago. I write in Open Office and use either Firefox or Chrome as my browser, and I generally wind up posting and then editing my chapter to correct the centering. The RTE's centering works brilliantly on editing, I find. Even before the new code rollout, you were unable to return to the text field once you selected "preview" so that hasn't changed, actually.

The age/consent thing happens because the cookies for a subdomain now expire after 30 days. When you access the subdomain, you simply need to acknowledge that you are over 18. It's a click, and you shouldn't need to fill anything in. As staff, I'm in and out of every subdomain, and I do need to renew my cookies periodically by clicking as well.

[DemonGoddess061]

I think the other age verification is the one mentioned. Although this is how the cookies work. At the BASE entry point per subdomain is a click cookie, that's set to expire every 30 days, so you need to reclick it once a month. When going in to any chapter for the first time, after clearing cookies, you hit the age verification form, which is ALSO a cookie setter. That one has an expiration of I think 90 or 180 days, don't honestly remember. Unfortunately, at this stage of code update we can't disable it outright. However, it will go the way of the dodo once the storyboard part of the coding is in place.

As to privacy, now when one enters birthday and name information, it's simply stored in the database. It's not displayed AT ALL.

[ApolloImperium]

And as for privacy - You can better believe that unless it was for some serious reason (Like a child molester or something like that) I would go to the moon and back to protect our privacy. I would never roll over and give out member information with out a fight for some dumb shit.

[DemonGoddess061]

We use member information to contact them if needed. If you're referring to birthday, we do our best to verify age of everyone who registers, as the site is restricted in use to users age 18 and up. As stated before, real name, email and birthday information are hidden.by default. The users often add the email and whatnot to their profiles anyway.

[ApolloImperium]

Depends on the reason and the lawyer - Cable companies have successfully overcome subpenas to release member information to media companies

[BronxWench]

@ThroneofSouls:

As the next phases of the new code are rolled out, some features will return. I'm not entirely sure that the author panels will go back to showing review counts and hits. I do know that ratings may be replaced with a recommendation feature instead, since ratings has proved to be a problem in the past when authors were ratings-bombed for whatever reason.

We're always happy to hear feedback from our authors and readers, and we appreciate your taking the time to let us know what you think.

[DemonGoddess061]

I'm making a guess here, but I think once the unlimited subcats are in place, that yes, you'll see that again.