nate/Siteforge
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix Seafile upload-link using wrong query param ?path= instead of ?p=; v2.0.12
Publish Container / docker (push) Successful in 14m0s
Details

Browse Source 
Seafile API uses ?p= for the directory path parameter. Using ?path= caused
the request to never match an API route, returning the web UI 404 HTML page.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
nmemmertandClaude Sonnet 4.6 committed 2026-09-08 14:45:51 -04:00
1 parent ce12ae1d0d
commit 3febad351d
2 files changed
+2 -2
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

package.json
+1 -1
View File
@@ -1,7 +1,7 @@
{ {
"name": "siteforge", "name": "siteforge",
"private": true, "private": true,
"version": "2.0.11", "version": "2.0.12",
"type": "module", "type": "module",
"scripts": { "scripts": {
"dev": "vite", "dev": "vite",
server/routes/nuggets-host-upload.js
+1 -1
View File
@@ -103,7 +103,7 @@ function seafileConfigured() {
} }
async function getSeafileUploadLink(dir) { async function getSeafileUploadLink(dir) {
const url = `${SEAFILE_URL}/api/v2.1/repos/${SEAFILE_NUGGETS_REPO_ID}/upload-link/?path=${encodeURIComponent(dir)}` const url = `${SEAFILE_URL}/api/v2.1/repos/${SEAFILE_NUGGETS_REPO_ID}/upload-link/?p=${encodeURIComponent(dir)}`
const res = await fetch(url, { const res = await fetch(url, {
headers: { Authorization: `Token ${SEAFILE_TOKEN}` }, headers: { Authorization: `Token ${SEAFILE_TOKEN}` },
}) })