Uploaded image for project: 'Archive of Our Own'
  1. AO3-3380

Posting a work and then quickly editing to add it to an anonymous collection results in a subscription notification with the author's name in the title and "by Anonymous" in the body


    • Type: Bug
    • Status: Deployed
    • Priority: Medium
    • Resolution: DeployedToBeta
    • Affects Version/s: None
    • Fix Version/s: 0.9.167
    • Google Code Issue ID:
    • Milestone:
      Internal 0.10
    • Roadmap:
    • Components:


      Originally reported on Google Code with ID 3386
      What archive revision are you testing on? (See the version label in
      the footer, for example v0.8.13.8.)


      If appropriate, enter the URL of a page where the problem can be seen:

      What steps will reproduce the problem?
      1. Post a new work intended for an anonymous challenge
      2. Suddenly realize you forgot to tick the box to add the work to the challenge
      3. Edit the work to add it to the challenge

      What is the expected output? What do you see instead?

      Expect users subscribed to me to either get a normal subscription email or (preferably)
      not be informed of my new work. Instead users get a subscription email with "<Author>
      posted <Work Name>" in the title but "<Work Name> by Anonymous" in the body.

      Please use labels and text to provide additional information.

      The subscription notification in this case is confusing and may lead users to believe
      that works posted straight to anonymous collections normally generate notifications
      (which they do not). Ideally, since subscription notifications intrinsically have
      a delay caused by batching, that time would be a grace period in which posting errors
      of this sort could be fixed.

      Related ticket: https://otw.16bugs.com/projects/4911/bugs/244856




            • Assignee:
              tickinginstant ticking instant
              lady.oscar.ao3 lady.oscar.ao3 (Inactive)
            • Watchers:
              2 Start watching this issue


              • Created: