-
Notifications
You must be signed in to change notification settings - Fork 0
/
readme.txt
153 lines (98 loc) · 5.2 KB
/
readme.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
=== Assets Manager ===
Contributors: jackreichert
Donate link: http://www.jackreichert.com/buy-me-a-beer/
Tags: uploads, file share, file management, asset management, assets, share file, content, links, admin, social
Requires at least: 3.5
Tested up to: 4.4
Stable tag: trunk
License: GPLv2
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Assets Manager for WordPress is a self hosted file sharing tool, enable / disable links, set expiration and make files you share password protected.
== Description ==
Assets Manager is a self-hosted file sharing tool. Born out of the need for a file sharing tool that was not blocked 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 links to the files so that you can control how those files are shared.
[Here’s how it works.](http://www.jackreichert.com/2015/11/15/how-assets-manager-replaced-our-sharefile/)
= Features =
* Set an expiration period for when the file link will expire.
* Disable links after they've been shared (no more fretting when sending out emails).
* Force anyone trying to access a link to log into your site.
For more information check out the full blogpost about [Assets Manager](http://www.jackreichert.com/2014/01/12/introducing-assets-manager-for-wordpress/).
Questions? Comments? Requests? [Contact me](http://www.jackreichert.com/contact/).
== Installation ==
1. Upload `plugin-name.php` to the `/wp-content/plugins/` directory
2. Activate the plugin through the 'Plugins' menu in WordPress
3. Resave your 'Pretty Permalinks' structure under "Settings > Permalinks".
= 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. Hit upload.
6. Publish post (**note:** links will not be available until the Asset Set as been published).
== Frequently Asked Questions ==
= Why aren't the links working? =
You may need to reset the permalinks by going to Settings > Permalinks and pressing the "Save Changes" button.
= Why would I want to disable a link? =
Let's say there is incorrect information in the file, or there is an updated version, now you can disable the link sent out, shared, published and send out a new one.
= Are these files searchable? =
The asset sets are blocked 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 block search engines from finding them if they are linked to from someplace else. But it does make finding files harder if you do not have a direct link to the file.
= Can I upload a bunch of files and share them all with one link? =
Yes you can. Assets Manager generates a page that contains all of the links in the asset set. This page can then be shared. Note: if you have disabled or expired files they will not be listed on this page, if a file is "secure" and the visitor is not logged in the file link will not appear as well.
= Can I reorder the list of files on the public facing assets set page? =
Sure, just drag and drop. No need to save. All reordering happens via AJAX automatically.
= Does this work with nginx? =
Sure, I did notice that with Ubuntu + nginx I needed the following in my .conf file:
location ~ ^/asset/(.*)$ {
try_files $uri $uri/ /index.php?$query_string;
}
= What about foo bar? =
Answer to foo bar dilemma.
== Screenshots ==
1. Add a title.
2. Add new files.
3. Upload.
4. Publish.
5. Share.
== Changelog ==
= 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-links
= 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 permalinks on activate
= 0.2.5 =
* Changed action to prevent "headers sent" error
= 0.2.4 =
* Removed echo to prevent "headers sent" error
= 0.2.3 =
* Changed action to prevent "headers sent" error
= 0.2.2 =
* Changed 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 version.
== Upgrade Notice ==
= 0.1 =
* This is the first version.
== Roadmap ==
= Future features I'm working on: =
* **Sha1:** If you upload a file that already exists it will link that file to your post instead of keeping multiple versions of the file.
* **File replacement:** After uploading and even sharing a file you'll be able to replace the file behind the active link with a file of the same MIME type.
Special thanks to @binmind for his extensive QA testing of the company’s plugin, his testing was crucial for development of the proof of concept and making sure everything was working as it should.