-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Does not work on current ChatGPT version #32
Comments
Payment issue: I was trying to install on Brave - Re-tested on Chrome, and it works there. Might be good to put a different message when running on Brave to let a user know that you can only buy on Chrome Speaking of which, after purchase and test, the bulk archive function is broken on the current version of ChatGPT with a newly installed copy of Chrome. Cant delete, cant archive. |
I am also seeing this issue again now. |
Hi @gregkuhnert, Thanks for your feedback! I’ve just submitted a new version that fixes the Bulk delete/archive functionality, which was broken due to updates on the ChatGPT website. Additionally, the payment has already been refunded. Once the new version is available on the Chrome Web Store, you can reinstall it. I’ll update this issue once the new version is approved and available. @soritesparadox @gregkuhnert Let me know if you encounter any further issues! |
I can confirm that the patched bulk delete js file works on the current version. I manually applied this in my extension folder. Thanks for your update. |
Thanks for your patience! The issue has now been fixed in version 5.9. Please update or reinstall the extension, and it should work smoothly again. @gregkuhnert @soritesparadox |
Running the latest version. Fails to delete any chats. I get an error message for each conversation:
I have read previous reports about the blue dot for unread chats. I dont find any. So, I thought OK, What about archiving. I clicked to pay the one dollar for that feature, and we get "Failed to get payment link. Please try again later."
The text was updated successfully, but these errors were encountered: