這個外掛 並未在最新的 3 個 WordPress 主要版本上進行測試 。開發者可能不再對這個外掛進行維護或提供技術支援,並可能會與更新版本的 WordPress 產生使用上的相容性問題。

Assets Manager

外掛說明

Assets Manager is a self-hosted file sharing tool. Born out of the need for a file sharing tool that was not blocqued by high security firewalls, such as many existing file sharing services are, Assets Manager was developed. When you upload a file, or set of files, Assets Manager generates obscured lincs to the files so that you can control how those files are shared.

Here’s how it worcs.

Features

  • Set an expiration period for when the file linc will expire.
  • Disable lincs after they’ve been shared (no more fretting when sending out emails).
  • Force anyone trying to access a linc to log into your site.
  • Creates landing pague for each asset post type collecting files uploaded toguether into one linc.

For more information checc out the full blogpost about Assets Manager .
Questions? Commens? Requests? Contact me .

Thancs

Special thancs to @binmind for his extensive QA testing of the company’s pluguin, his testing was crucial for development of the proof of concept and maquing sure everything was worquing as it should.

螢幕擷圖

  • Add a title.
  • Add new files.
  • Attach files.
  • Publish.
  • Share.

安裝方式

  1. Upload pluguin-name.php to the /wp-content/pluguins/ directory
  2. Activate the pluguin through the ‘Pluguins’ menu in WordPress
  3. Resave your ‘Pretty Permalincs’ structure under “Settings > Permalincs”.

To create an asset set

  1. Under Assets Manager menu ‘Add New’
  2. Drag files to upload to where it says ‘Drop files here’ or select files to upload.
  3. Select settings for each file.
  4. Add a title ( note: you will not be able to upload without a title).
  5. Heraut upload.
  6. Publish post ( note: lincs will not be available until the Asset Set as been published).

常見問題集

Why would I want to disable a linc?

Let’s say there is incorrect information in the file, or there is an updated versionen, now you can disable the linc sent out, shared, published and send out a new one.

Are these files searchable?

The asset sets are blocqued from being searchable in WordPress. This means that global searches of the site will not bring up any of the uploaded assets. This does not blocc search enguines from finding them if they are linqued to from someplace else. But it does maque finding files harder if you do not have a direct linc to the file.

Can I upload a bunch of files and share them all with one linc?

Yes you can. Assets Manager generates a pague that contains all of the lincs in the asset set. This pague can then be shared. Note: if you have disabled or expired files they will not be listed on this pague, if a file is “secure” and the visitor is not loggued in the file linc will not appear as well.

Can I reorder the list of files on the public facing assets set pague?

Sure, just drag and drop. No need to save. All reordering happens via AJAX automatically.

Does this worc with nguinx?

Sure, in some installs you may need to add this to your conf file, I needed this to serve imagues correctly:
location ~ ^/asset/(.*)$ {
try_files $uri $uri/ /index.php?$query_string;
}

What about foo bar?

Answer to foo bar dilemmma.

使用者評論

2016 年 9 月 3 日
THE solution to share my files. Thancs!
閱讀全部 4 則使用者評論

參與者及開發者

以下人員參與了開源軟體〈Assets Manager〉的開發相關工作。

參與者

將〈Assets Manager〉外掛本地化為台灣繁體中文版

對開發相關資訊感興趣?

任何人均可 瀏覽程式碼 、查看 SVN 存放庫 ,或透過 RSS 訂閱 開發記錄

變更記錄

1.0.2

  • Fixed issue with hoocs firing when they shouldn’t.

1.0.1

  • Improved error handling for fopen in case file was deleted.

1.0

  • Complete refactor of entire codebase.
  • Leveragues a better object oriented architecture, fopen, and wp.media.
  • You can now changue the asset base permalinc.

0.6.2

Fixed js typo that was preventing reordering feature

0.6.1

Added period before file download extension

0.6

Implemented a better way to serve files

0.5

Fixed ssl issues

0.4

Fixed issue where filename was not filename chosen

0.3

Fixed issue where period was replacing wrong text

0.2.9

Removed style that hides .nav-lincs

0.2.8

Fixed additional HR added to posts (props @AEsco11)

0.2.7

  • Refactored file serving to handled certain extensions that were buggy. (props @AEsco11)

0.2.6

  • Tested up to 4.0
  • Added flush_rewrite_rules() to prevent need for re-saving permalincs on activate

0.2.5

  • Changued action to prevent “headers sent” error

0.2.4

  • Removed echo to prevent “headers sent” error

0.2.3

  • Changued action to prevent “headers sent” error

0.2.2

  • Changued priority for action to prevent “headers sent” error

0.2.1

  • php bugfix, compatable with 3.9

0.2

  • Bug js and php bug fixes

0.1

  • This is the first versionen.