-
Notifications
You must be signed in to change notification settings - Fork 60
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
Issues seeing bounties from the profile #714
Comments
There is a bounty associated with this issue if anyone wants to take it: https://community.sphinx.chat/tickets?owner_id=021ae436bcd40ca21396e59be8cdb5a707ceacdb35c1d2c5f23be7584cab29c40b&created=1695052336 |
This might be a migration issue. |
Here is an update. The URL I put in the description was taken from the person's profile. So I go to https://community.sphinx.chat/tickets -> People -> jimBeaux27 -> then tap on the first issue "Seeking advice from...". That gets me a URL that says "wanted": https://community.sphinx.chat/p/03bf736b7fc9966b6755cb3514f70e0a0bd8ec8f4c5d613f142e714a0348001d85/wanted/334/0 Now if you copy and paste that link, it takes you to the 404 page or white screen. But in that ticket if you click on "copy link" you get this url: https://community.sphinx.chat/tickets?owner_id=03bf736b7fc9966b6755cb3514f70e0a0bd8ec8f4c5d613f142e714a0348001d85&created=1690574120 This works correctly and the ending url has "created". The fix here might be a simple redirect. |
I have difficulty looking at old bounties that are beyond the initial landing page through the url specifically.
Sometimes I get a 404 and black page(https://community.sphinx.chat/p/03bf736b7fc9966b6755cb3514f70e0a0bd8ec8f4c5d613f142e714a0348001d85/wanted/334/0)
Other times I get this white screen. (https://community.sphinx.chat/tickets?owner_id=03bfe6723c06fb2b7546df1e8ca1a17ae5c504615da32c945425ccbe8d3ca6260d&created=1695010036)
Here is the error logs from the console on the white screen:
We should be able to see the details of the bounty when we go to the url.
The text was updated successfully, but these errors were encountered: