Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Going to Reports > Docket Report > Search for docket doesn't work #249

Closed
mlissner opened this issue May 18, 2018 · 3 comments · Fixed by freelawproject/recap-chrome#273
Closed

Comments

@mlissner
Copy link
Member

Just got a bug reported by a user.

We've optimized the workflow of

Login > Query > Docket Report,

but

Login > Reports > Docket Report

Neither uploads nor provides a notice to the user that something might be free.

Steps to Reproduce:

  1. Log into PACER (https://ecf.pawb.uscourts.gov)
  2. Click the Reports button.
  3. Select Docket Report
  4. Put in a docket number (18-21428-TPA)
  5. Hit "Find this Case" button
  6. Run the report to buy the docket.

Expected results:

  1. After step five above, you should see a notice saying whether we have that docket.
  2. After step six above, when you see the docket itself, it should get uploaded to us (it's not presently).
@s-zeid
Copy link

s-zeid commented Jun 14, 2019

I just ran into this issue with 2:17-cv-00455 in the Eastern District of Virginia. Following the steps to reproduce (with the appropriate domain name and docket number) reproduces the issue, but using https://ecf.vaed.uscourts.gov/cgi-bin/DktRpt.pl?372143 (PACER case ID in the query string) to access the case gives the expected results.

To get the PACER case ID, I had to view the console for the RECAP background page to find output such as:

RECAP: Got case number '372143' for pacer_doc_id: '18908914387' recap.js:20:17
RECAP: Attempting PDF upload to RECAP Archive with details: pacer_court: vaed, pacer_case_id: 372143, pacer_doc_id: 18908914387, document_number: 21, attachment_number: 0.

The issue can be reproduced even after the docket is uploaded using the query string URL.

@mlissner
Copy link
Member Author

Thanks @scottywz.

@mlissner
Copy link
Member Author

mlissner commented Nov 1, 2022

Weird. This is still broken and we should at least see how hard it is to fix. @ERosendo, can you analyze this and see what's going on, please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants