It’s annoying for Policy & Abuse not to have the work IDs handy.
So when a user does this, before we run before_validation :clean_url, on: :create and validate :url_is_not_over_reported, we'd like to:
look up which work the chapter belongs to
add the work information to the URL
assuming the chapter and work can be found, run the usual before_validation and validation checks
if the chapter or work cannot be found, don’t modify the URL and don’t error, just send the report on through with the URL as entered
Testing
NB: Unless is fixed first, you’ll need to remove the test subdomain from the URLs as well.
Locate a multi-chapter work
Access it in chapter-by-chapter mode
Follow the Policy Questions & Abuse Reports link in the site footer
Fill out the form,
making sure to provide an email address you have access to, and
pausing at the “Link to the page you are reporting” field to remove the work info from the URL, e.g., changing https://test.archiveofourown.org/works/123/chapters/789 to https://archiveofourown.org/chapters/789
Submit the form
In the email you receive, ensure the work ID has been added back to the URL
Again, follow the Policy Questions & Abuse Reports link in the site footer
Fill out the form,
making sure to provide an email address you have access to, and
changing the “Link to the page you are reporting” field to contain a chapter URL for a chapter that doesn’t exist, e.g., https://test.archiveofourown.org/chapters/000
Submit
In the email you receive, ensure the URL looks the same as it did when you entered it
It’s also a good idea to ask someone from PAC to confirm the URL in their ticket tracker is correct.
Attachments
9
Activity
Sarken
March 27, 2023 at 10:43 PM
That’s a known issue linked in the testing instructions of this issue:
NB: Unless is fixed first, you’ll need to remove the test subdomain from the URLs as well.
So this is ready for release.
james_
March 26, 2023 at 10:23 AM
It said it was logged.
If we require the url to be edited to point at prod when we make a abuse report I am happy ( But what happens for other instances of the Archive ).
afaik, people just entered a URL like archiveofourown.org/chapters/####/ and the work portion got added in front, so I think you have it covered – thanks!
Sometimes, users will supply chapter show URLs (e.g., https://test.archiveofourown.org/chapters/123 or https://test.archiveofourown.org/chapters/123?some_params=something) in the abuse form’s “Link to the page you are reporting” field.
It’s annoying for Policy & Abuse not to have the work IDs handy.
So when a user does this, before we run
before_validation :clean_url, on: :create
andvalidate :url_is_not_over_reported
, we'd like to:look up which work the chapter belongs to
add the work information to the URL
assuming the chapter and work can be found, run the usual before_validation and validation checks
if the chapter or work cannot be found, don’t modify the URL and don’t error, just send the report on through with the URL as entered
Testing
NB: Unless is fixed first, you’ll need to remove the
test
subdomain from the URLs as well.Locate a multi-chapter work
Access it in chapter-by-chapter mode
Follow the Policy Questions & Abuse Reports link in the site footer
Fill out the form,
making sure to provide an email address you have access to, and
pausing at the “Link to the page you are reporting” field to remove the work info from the URL, e.g., changing
https://test.archiveofourown.org/works/123/chapters/789
tohttps://archiveofourown.org/chapters/789
Submit the form
In the email you receive, ensure the work ID has been added back to the URL
Again, follow the Policy Questions & Abuse Reports link in the site footer
Fill out the form,
making sure to provide an email address you have access to, and
changing the “Link to the page you are reporting” field to contain a chapter URL for a chapter that doesn’t exist, e.g.,
https://test.archiveofourown.org/chapters/000
Submit
In the email you receive, ensure the URL looks the same as it did when you entered it
It’s also a good idea to ask someone from PAC to confirm the URL in their ticket tracker is correct.