From 3febad351d3851eebe167c6e979c632ebdad93fd Mon Sep 17 00:00:00 2001
From: nmemmert <nmemmert@users.noreply.github.com>
Date: Tue, 8 Sep 2026 14:45:51 -0400
Subject: [PATCH] Fix Seafile upload-link using wrong query param ?path=
 instead of ?p=; v2.0.12

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>
---
 package.json                         | 2 +-
 server/routes/nuggets-host-upload.js | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/package.json b/package.json
index 0ec55b0..ad306bd 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "siteforge",
   "private": true,
-  "version": "2.0.11",
+  "version": "2.0.12",
   "type": "module",
   "scripts": {
     "dev": "vite",
diff --git a/server/routes/nuggets-host-upload.js b/server/routes/nuggets-host-upload.js
index ba5f0ae..9646847 100644
--- a/server/routes/nuggets-host-upload.js
+++ b/server/routes/nuggets-host-upload.js
@@ -103,7 +103,7 @@ function seafileConfigured() {
 }
 
 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, {
     headers: { Authorization: `Token ${SEAFILE_TOKEN}` },
   })