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

Sussy Toons #7324

Closed
7 tasks done
QuagZy opened this issue Jan 25, 2025 · 5 comments · Fixed by #7461
Closed
7 tasks done

Sussy Toons #7324

QuagZy opened this issue Jan 25, 2025 · 5 comments · Fixed by #7461
Labels
Bug Bugs in existing sources

Comments

@QuagZy
Copy link

QuagZy commented Jan 25, 2025

Source information

Sussy Toons 1.4.49

Source language

Português (Brasil)

Steps to reproduce

A atualização recentes da extensão tá diferente da atualização recentes do site

Extensão

Image

Site

Image

Expected behavior

Estarem iguais

Actual behavior

Estão diferentes

Mihon/Tachiyomi version

Komikku 1.12.2

Android version

Android 11

Other details

No response

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
  • I have written a short but informative title.
  • I have updated the app to version 0.15.3.
  • I have updated all installed extensions.
  • I have tried the troubleshooting guide.
  • If this is an issue with the app itself, I should be opening an issue in the app repository.
  • I will fill out all of the requested information in this form.


Add a 👍 reaction to issues you find important.

@QuagZy QuagZy added the Bug Bugs in existing sources label Jan 25, 2025
@Smol-Ame
Copy link
Contributor

It's probably the source's shitty API/servers that's not caught up to their site's changes. Wait a few hours to see if the newer updates show up in the Recents tab (or I'll check & close out this issue in the morning).

@deividgabrielpeira
Copy link
Contributor

deividgabrielpeira commented Jan 28, 2025

Approximately 12 hours or 13 hours and updated the manhua in the extension
Possibly it is the API that is bad.

I don't know if Chopp will make the correction or if it's because of Sussy's API, that's bad, if there isn't much PR, I believe the "Issue" has been closed.

@GodMan10
Copy link

GodMan10 commented Jan 28, 2025

new manhwas/mangas are also not showing up when you search for them, even though they are on the site

Image

Image

@deividgabrielpeira
Copy link
Contributor

#7417

Image

As shown in the image above, some Sussy chapters will be on "Paywall", but will be released in around 1 hour or 5 hours, I think it's a good idea to set a timer to know what time it will be released.

@Lugolz
Copy link

Lugolz commented Jan 31, 2025

Talvez isso já foi relatado
Mas mesmo após atualizar as obras várias vezes e depois do horário falado, a obra e os caps não carregam seja os novos que foram lançados e os antigos, não dá para visualizar e aparece mensagem de erro HTTP error 404.
Eu verifiquei e vi que esse erro dá em todas as obras.
Não sei se alguma configuração tá errada mas tá assim

URL padrão: https://www.sussytoons.site
URL da api: https://api-dev.sussytoons.site

Api tá errado ou foi mudada?

Maybe this has already been reported
But even after updating the works several times and after the stated time, the work and the chapters do not load, whether the new ones that were released or the old ones, it is not possible to view them and an HTTP error 404 message appears.
I checked and saw that this error occurs in all works.
I do not know if some configuration is wrong but it is like this

Default URL: https://www.sussytoons.site
API URL: https://api-dev.sussytoons.site

Is the API wrong or has it been changed?

(Sorry for repeating the comment, I don't know if Github translates the reader's language)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 5, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Bugs in existing sources
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants