[WordPress] 外掛分享: Versilink – Replace PDFs Without Breaking Links

首頁 › 外掛目錄 › Versilink – Replace PDFs Without Breaking Links
WordPress 外掛 Versilink – Replace PDFs Without Breaking Links 的封面圖片
全新外掛
安裝啟用
—
尚無評分
28 天前
最後更新
—
問題解決
WordPress 5.0+ PHP 7.2+ v0.1.0 上架:2026-09-16

內容簡介

Versilink 外掛可讓您在更新 PDF 價目表、目錄或指南時,保持原有連結不變,確保所有已分享的連結指向最新版本。此外掛適用於任何可上傳的檔案類型,提供便捷的文件管理功能。

【主要功能】
• 將媒體庫檔案轉換為文件
• 直接替換檔案,保持原有連結
• 版本歷史記錄及可選註解
• 隱藏舊版本於專用上傳資料夾
• 短網址永久連結指向最新檔案

外掛標籤

開發者團隊

⬇ 下載最新版 (v0.1.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Versilink – Replace PDFs Without Breaking Links」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

When you update a price list, catalog or PDF guide, the links you already sent by email, in ads or on social media still point to the old copy. This plugin turns an existing Media Library file into a Document. Each new version you upload replaces the file at its current address, so links you already shared serve the new content.
It is aimed at PDF price lists and guides, but works with any file type WordPress lets you upload, including DOCX and XLSX.
Features

Create a Document from any Media Library file.
Replace the file in place: its existing address serves each new version.
Version history with an optional note per version. Users who manage the Document can download previous versions and restore any of them.
Previous versions are kept in a separate uploads folder under random file names and do not appear in the Media Library.
A short permanent link (/docs/your-document, prefix configurable) that always points to the current file. The plugin warns when the prefix clashes with an existing page, post type or taxonomy.
Media Library files that are Documents are marked, and other files get a “Create Document” action.

A note on caching
The permanent link is sent with headers that forbid caching by browsers, but if the site uses a page cache or a CDN, the file’s actual address may still be served from cache until purged. After uploading a new version, purge the relevant cache so visitors see it immediately.
A note on nginx
Previous-version files are stored under a folder with random, non-guessable names, which is the primary protection against direct access. On servers running Apache, an .htaccess file inside that folder also denies all direct requests. nginx does not read .htaccess files, so on nginx that extra layer is not present; the random file names remain the only protection.

延伸相關外掛

文章
Filter
Mastodon