-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Nothing in PSDLE list showing after date 11/21/2016 #44
Comments
What method (userscript, chrome, etc) and version (displayed on the startup screen below the logo)? |
Please run this version of PSDLE by copy-pasting the contents of the URL into your browser's console (Firefox: Ctrl+Shift+K, Chrome: Ctrl+Shift+J). Do not activate any other method of PSDLE while doing this. |
Thanks,
I tried that test code in the console on Chrome, and it populated properly.
No issues, even tried it twice just to verify. I have over 3000 items, so it takes a while to load.
I was using version v3.1.5 of the PSDLE extension in Chrome.
On Wednesday, November 29, 2017, 6:11:03 PM EST, RePod <notifications@github.com> wrote:
Please run this version of PSDLE by copy-pasting the contents of the URL into your browser's console (Firefox: Ctrl+Shift+K, Chrome: Ctrl+Shift+J).
Do not activate any other method of PSDLE while doing this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Good to hear. I've pushed all versions to 3.1.6 with the fix, however the Chrome extension may take up to an hour from this reply to appear on the webstore. |
Just went on to export a new list with some titles I had recently purchased as apart of the Black Friday sales.
Low and behold, nothing will populate past the date 11/21/2016. Try changing filters, switching between PLUS/Non-PLUS/Both, yet nothing seemed to change.
All platforms are populated in the list, PS1, PS2, PSP, PS3, PSV, PS4, and PS2 on PS4 all show up in the list, just nothing after said date 11/21 date.
Not sure if this is related to the Valkyrie API update or not, but I figured I'd add my input and see if there is a fix.
The text was updated successfully, but these errors were encountered: