Bug when renaming a project's slug #129

New issue

Closed

opened 2026-08-27 09:37:33 +02:00 by qwc · 0 comments

qwc commented

2026-08-27 09:37:33 +02:00

Owner

we did:

renamed a project's slug
then tried to access the new content, which resulted in a 404
accessing the OLD slug's content did also result in a project not found
renaming the project's slug back, did again show the projects content on the old slug

we suspect this might be an permissions/access issue with the database

we did: - renamed a project's slug - then tried to access the new content, which resulted in a 404 - accessing the OLD slug's content did also result in a project not found - renaming the project's slug back, did again show the projects content on the old slug we suspect this might be an permissions/access issue with the database

qwc added the

Kind/Bug

label

2026-08-27 09:37:37 +02:00

qwc referenced this issue from a commit

2026-08-28 13:10:53 +02:00

Refuse a project rename when its storage directory is missing (#129)

qwc referenced this issue from a commit

2026-08-28 13:10:53 +02:00

Repair projects whose storage directory no longer matches their slug (#129)

qwc referenced this issue from a pull request that will close it,

2026-08-28 13:11:16 +02:00