[GH-ISSUE #385] Adding a URL doesn't automatically create an archive #246

Closed
opened 2026-02-25 23:33:47 +03:00 by kerem · 6 comments
Owner

Originally created by @thelazyoxymoron on GitHub (Feb 25, 2022).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/385

I have turned on the "Create archive by default" setting and I see the relevant option ticked as well when I'm adding a new URL. However, it doesn't actually create an archive, I have to manually go and do update archive.

Originally created by @thelazyoxymoron on GitHub (Feb 25, 2022). Original GitHub issue: https://github.com/go-shiori/shiori/issues/385 I have turned on the "Create archive by default" setting and I see the relevant option ticked as well when I'm adding a new URL. However, it doesn't actually create an archive, I have to manually go and do update archive.
Author
Owner

@Grauwolf commented on GitHub (Feb 25, 2022):

when using SQLite it seems to work as intended. when configuring a PostgreSQL database, I can confirm that no archive is created, even though "create archive" is enabled.

<!-- gh-comment-id:1051101990 --> @Grauwolf commented on GitHub (Feb 25, 2022): when using SQLite it seems to work as intended. when configuring a PostgreSQL database, I can confirm that no archive is created, even though "create archive" is enabled.
Author
Owner

@fmartingr commented on GitHub (Feb 26, 2022):

I have turned on the "Create archive by default" setting and I see the relevant option ticked as well when I'm adding a new URL. However, it doesn't actually create an archive, I have to manually go and do update archive.

Is this happening to you in postgresql as well?

<!-- gh-comment-id:1051985512 --> @fmartingr commented on GitHub (Feb 26, 2022): > I have turned on the "Create archive by default" setting and I see the relevant option ticked as well when I'm adding a new URL. However, it doesn't actually create an archive, I have to manually go and do update archive. Is this happening to you in postgresql as well?
Author
Owner

@MidnightSnowleopard commented on GitHub (Feb 26, 2022):

I can confirm I am seeing the same behavior with PostgreSQL. Haven't test for SQLite but the behavior is present on Shiori 1.5.2 and 1.5.2 in docker.

<!-- gh-comment-id:1052424561 --> @MidnightSnowleopard commented on GitHub (Feb 26, 2022): I can confirm I am seeing the same behavior with PostgreSQL. Haven't test for SQLite but the behavior is present on Shiori 1.5.2 and 1.5.2 in docker.
Author
Owner

@thelazyoxymoron commented on GitHub (Feb 27, 2022):

Is this happening to you in postgresql as well?

Sorry, should've mentioned this, I'm using Postgresql, haven't tried with SQLite.

<!-- gh-comment-id:1052867487 --> @thelazyoxymoron commented on GitHub (Feb 27, 2022): > Is this happening to you in postgresql as well? Sorry, should've mentioned this, I'm using Postgresql, haven't tried with SQLite.
Author
Owner

@fukajun commented on GitHub (Sep 29, 2022):

Maybe I fixed it. Please review PR #480.

<!-- gh-comment-id:1261747779 --> @fukajun commented on GitHub (Sep 29, 2022): Maybe I fixed it. Please review PR #480.
Author
Owner

@fmartingr commented on GitHub (Jul 21, 2023):

Apparently fixed in #484, please open a new issue if you experience something similar again.

<!-- gh-comment-id:1645349245 --> @fmartingr commented on GitHub (Jul 21, 2023): Apparently fixed in #484, please open a new issue if you experience something similar again.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/shiori#246
No description provided.