Are you following SDLC practices right?
By now these sorts of "functional collapses" should not be happening as your dev, test, and prod platforms should all be separate things. major issues with site functionality should not make it out of test, and "beta" test functionality for end-user testing usually happens in a different testing environment altogether - I've heard various names for that - like "Stage" and "UAT" servers/platforms used for this. I hope you are managing changes appropriately and observing formal SDLC practices, but this last set of functional collapses of the new UI casts doubt on that presumption.
As for overall feedback on the site - I'd like to be able sot set some "permanent" filters on my profile - so I don't have to even see some of the story listings for things that are turn-offs to me - let users set filters at the category level so that the New story listings for story types that are not turn-ons for them don't even appear in the listings (until they chose to turn those category filters off, anyway). A simple categories filter list should be simple enough to implement. (I know the SQL WHERE clauses are easy enough to build.) If you want to go further and offer filters on keywords, keep those filters separate from (and complimentary to) the category filters.
For example, one person may like BDSM stuff while to someone else it's a turnoff. a third person may like some BDSM but gets turned off for involuntary or scat/golden shower game stuff... while the BDSM category-level filter would help with the first part, someone who wants to see the fetish stiff minus the scat games would likely need the keyword-level filters to make things work best for them.
By now these sorts of "functional collapses" should not be happening as your dev, test, and prod platforms should all be separate things. major issues with site functionality should not make it out of test, and "beta" test functionality for end-user testing usually happens in a different testing environment altogether - I've heard various names for that - like "Stage" and "UAT" servers/platforms used for this. I hope you are managing changes appropriately and observing formal SDLC practices, but this last set of functional collapses of the new UI casts doubt on that presumption.
As for overall feedback on the site - I'd like to be able sot set some "permanent" filters on my profile - so I don't have to even see some of the story listings for things that are turn-offs to me - let users set filters at the category level so that the New story listings for story types that are not turn-ons for them don't even appear in the listings (until they chose to turn those category filters off, anyway). A simple categories filter list should be simple enough to implement. (I know the SQL WHERE clauses are easy enough to build.) If you want to go further and offer filters on keywords, keep those filters separate from (and complimentary to) the category filters.
For example, one person may like BDSM stuff while to someone else it's a turnoff. a third person may like some BDSM but gets turned off for involuntary or scat/golden shower game stuff... while the BDSM category-level filter would help with the first part, someone who wants to see the fetish stiff minus the scat games would likely need the keyword-level filters to make things work best for them.