Wiki source code of Attachments

Version 10.1 by Giovanni JĂșnior on 2012/08/23

Show last authors
1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
4
5 Attachments can be uploaded either through the regular [[upload action>>platform:Features.Attachments]], [[platform:Features.WebDAV]], [[platform:Features.XMLRPC]] or [[Rest>>platform:Features.XWikiRESTfulAPI]].
6 As an administrator you can set limits on the maximum size of an attachment and where the attachments will be stored.
7
8 = Size Limit =
9
10 The maximum size of an attachment is limited by a configuration parameter in XWikiPreferences document. It is set to about 10MB by default.
11 To change it:
12
13 1. Go to <yourwiki>/xwiki/bin/edit/XWiki/XWikiPreferences?editor=object
14 2. Click on the line that says ##XWikiPreferences 0## (right below the line that says ##Objects of type XWiki.XWikiPreferences (1)##)
15 3. Scroll down to the field that says ##Maximum Upload Size## and change the number to whatever size you want (it is expressed in bytes)
16 4. Scroll to the bottom and click save.
17
18 = Versions =
19
20 When a user uploads an attachment then uploads another attachment with the exact same name, you can decide whether or not to keep a version history of the attachments like you do with documents.
21 XWiki stores all document attachment versions by default which costs more storage space. If you need only latest versions of attachments, you can disable attachment version control by editing your [[xwiki.cfg>>platform:AdminGuide.Configuration#HSamplexwiki.cfg]] and adding:
22
23 {{code language="none"}}
24 xwiki.store.attachment.versioning=0
25 {{/code}}
26
27 = Deletion =
28
29 Deleted attachments are stored in a recycle bin so that they can be restored along with the document when rolling back or previewing an earlier version where the attachment should be visible. To disable this feature, edit xwiki.cfg and add:
30
31 {{code language="none"}}
32 storage.attachment.recyclebin=0
33 {{/code}}
34
35 You can view the list of deleted attachments in your wiki and delete them permanently by going to ##XWiki.DeletedAttachments## in your wiki.
36
37 = Attachment Storage =
38
39 XWiki offers plugin attachment storage mechanisms so you can store your attachments in the database or directly in the filesystem.
40
41 No matter what type of attachment store you use, the meta-data for the attachment will be saved in the [[xwikiattachment>>platform:DevGuide.DsXWikiAttachment]] table for faster loads.
42
43 == Database Attachment Store (Default) ==
44
45 This attachment storage mechanism stores your attachments in database entries in the [[xwikiattachment_content>>platform:DevGuide.DsXWikiAttachmentContent]], [[xwikiattachment_archive>>platform:DevGuide.XWikiAttachmentArchive]], and [[xwikiattrecyclebin>>platform:DevGuide.DsXwikiRecycleBin]] tables. This system allows for easy backup of your attachments by dumping the database and keeps all of your data together but attachment size is memory constrained since the attachment content and archive must all be held in memory. As a general rule, attachments larger than 30MB are not possible.
46 **Note:** When using this attachment store with a MySQL database, you must set the ##max_allowed_packet## to about 3 times the size of your largest attachment since the attachment and it's version history must be saved. See [[platform:AdminGuide.InstallationMySQL]] for more information.
47
48 == Filesystem Attachment Store (Since XWiki Enterprise 3.0M2) ==
49
50 {{warning}}
51 The Filesystem Attachment Store is still in beta, it has passed all of our tests with flying colors but we need your help to make absolutely sure that everything is right before turning it on by default.
52 {{/warning}}
53
54 {{warning}}
55 Known issue: the Filesystem Attachment Store is [[not able>>http://jira.xwiki.org/browse/XWIKI-7088]] to deal with images contained in imported Office documents.
56 {{/warning}}
57
58 The Filesystem attachment store saves your attachments in files in a directory tree, this means you will have one more thing to do when you back up your data but it also means you can save larger (over one gigabyte) files. Filesystem attachment store implements a two stage commit mechanism to maintain integrity even if the database fails to commit the attachment meta-data.
59
60 === Filesystem attachment store location ===
61
62 The directory in which the attachments are stored in the filesystem is defined with the parameter ##environment.permanentDirectory## in the ##xwiki.properties## file. By default it's defined to be ##data##, which is a directory relative to where the Java Servlet Container was started. It's recommend to modify this value to be absolute so that you can start the Servlet Container from any directory and still have XWiki find the attachments located in this work directory.
63
64 For example:
65
66 {{code}}
67 environment.permanentDirectory=/opt/tomcat6/data
68 {{/code}}
69
70 === Directory Structure ===
71
72 [[image:FilesystemAttachmentStoreDirtree.png||height="300px"]]
73
74 The Filesystem Attachment Store puts your attachments into a directory tree on the hard disk, the directory structure is designed to be intuitive to navigate but you should **never add or remove anything**. Each attachment is accompanied by a piece of meta-data in the database and modifying the content in the filesystem store manually will lead to meta-data with no content or content with no meta-data.
75
76 === New users ===
77
78 If you are a new XWiki user, all you need to do for enabling Filesystem Attachment Store is to change some settings in the [[xwiki.cfg file>>platform:AdminGuide.Configuration#HSamplexwiki.cfg]].
79 These settings should read as follows:
80
81 {{code language="none"}}
82 xwiki.store.attachment.hint = file
83 xwiki.store.attachment.versioning.hint = file
84 xwiki.store.attachment.recyclebin.hint = file
85 {{/code}}
86
87 Also make sure they are not commented out.
88
89 === Users who already have a running wiki ===
90
91 If you already have a wiki and want to take advantage of the Filesystem Attachment Store, you should use the [[extensions:Extension.Filesystem Attachment Porter]] to move your existing attachments onto the filesystem.
92
93 === Other considerations ===
94
95 * If you are running a [[cluster>>platform:AdminGuide.Clustering]] you will need for each node to have a synchronized storage directory, you can use NFS or another means to mount the disk on each node in the cluster.

Get Connected