[PR #12128] [MERGED] Planka: migrate data paths to new v2 directory structure #9985

Closed
opened 2026-02-26 17:32:32 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/12128
Author: @MickLesk
Created: 2/20/2026
Status: Merged
Merged: 2/20/2026
Merged by: @MickLesk

Base: mainHead: fix/planka-v2-data-migration


📝 Commits (1)

  • c49a166 planka: migrate data paths to new v2 directory structure

📊 Changes

2 files changed (+19 additions, -9 deletions)

View changed files

📝 ct/planka.sh (+18 -9)
📝 install/planka-install.sh (+1 -0)

📄 Description

✍️ Description

Planka v2.0.1 moved all uploads to a unified data directory:

  • public/{favicons,user-avatars,background-images} -> data/protected/
  • private/attachments -> data/private/

The update script was still restoring files to the old locations, which made attachments, avatars and backgrounds disappear after updating from rc.4 to 2.0.1.

Changes:

  • update_script: backup handles both old and new layouts
  • update_script: restore now uses new v2 paths
  • install script: create v2 data directories on fresh install

Fixes #12066

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/12128 **Author:** [@MickLesk](https://github.com/MickLesk) **Created:** 2/20/2026 **Status:** ✅ Merged **Merged:** 2/20/2026 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `fix/planka-v2-data-migration` --- ### 📝 Commits (1) - [`c49a166`](https://github.com/community-scripts/ProxmoxVE/commit/c49a166e174fbd1f2e3ccd3532261be792a56a70) planka: migrate data paths to new v2 directory structure ### 📊 Changes **2 files changed** (+19 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `ct/planka.sh` (+18 -9) 📝 `install/planka-install.sh` (+1 -0) </details> ### 📄 Description <!--🛑 New scripts must be submitted to [ProxmoxVED](https://github.com/community-scripts/ProxmoxVED) for testing. PRs without prior testing will be closed. --> ## ✍️ Description Planka v2.0.1 moved all uploads to a unified data directory: - public/{favicons,user-avatars,background-images} -> data/protected/ - private/attachments -> data/private/ The update script was still restoring files to the old locations, which made attachments, avatars and backgrounds disappear after updating from rc.4 to 2.0.1. Changes: - update_script: backup handles both old and new layouts - update_script: restore now uses new v2 paths - install script: create v2 data directories on fresh install ## 🔗 Related Issue Fixes #12066 ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [ ] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [x] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 17:32:32 +03:00
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/ProxmoxVE#9985
No description provided.