Attach Large Files

XWiki Standard has a new file-system attachment storage allowing you to add very large attachments to the wiki documents. This feature is disabled by default, but you can enable it by editing the xwiki.cfg file and by making the following changes under the Storage section:

#-# The attachment storage.
xwiki.store.attachment.hint=file

#-# The attachment versioning storage. Use 'void' to disable attachment versioning.
xwiki.store.attachment.versioning.hint=file

#-# The attachment recycle bin storage
xwiki.store.attachment.recyclebin.hint=file

In order for the changes to be taken into account, you will have to restart the server.

Next, you need to set the maximum size of the attachment. To do that, just edit the XWiki.XWikiPreferences page in "Objects" mode (e.g. ServerName/xwiki/bin/edit/XWiki/XWikiPreferences?editor=object) and replace the value of the "Maximum Upload Size" property with a huge number (for instance "999999999999").

ModifyMaximumUploadSize.png

Store Attachments on the Filesystem

In order to move the attached files from the database to the file-system, you can use the "Filesystem Attachment Porter" tool available here. You just have to download the snippet, edit it and copy the code in any wiki page, for instance in "XWiki.FSPorter".

The first step is to enable the file-system attachment storage as explained in the above section, then to restart the server. If the configuration is correct, when you navigate to "XWiki.FSPorter" you should see the following 3 lines colored in green:

* org.xwiki.store.legacy.store.internal.FilesystemAttachmentStore@3b69d6d3
* org.xwiki.store.legacy.store.internal.FilesystemAttachmentVersioningStore@2196d51e
* org.xwiki.store.legacy.store.internal.FilesystemAttachmentRecycleBinStore@3581b5cc

FSPorter.png

The attachments will be copied from the database into the permanent directory set for the servlet container. 

Note that the file-system porter will copy the attachments from the database to the storage folder but it will not delete the entries from the database. It is recommended to keep the attachments in the database that after the copy process finishes.

The "Dry Run" option allows you to do a simulation in order to check for corrupted attachments without necessarily having the file-system storage enabled.

The "Verbose" option displays each attachment as it is processed. 

Once you click the "Start" button, the script will work in 20 second chunks and print the results of each chunk. In order for the script to switch to the next chunk you will have to click the "Continue" button.

SwitchChunk.png

 

Related Pages

Search this space

 

Most popular tags

Failed to execute the [groovy] macro
  1. access rights
  2. activity stream
  3. Activity Stream Plugin
  4. annotation
  5. attachment
  6. CKEditor
  7. comment
  8. Document Tree Macro
  9. edit
  10. Error Message macro
  11. export
  12. Extension Manager
  13. Extension module
  14. Flamingo skin
  15. global group
  16. global user
  17. Groovy event listener
  18. Groovy module
  19. group
  20. import
  21. Info macro
  22. java macros
  23. MySQL
  24. nested page
  25. network
  26. Office Importer
  27. page
  28. RSS
  29. search
  30. skin
  31. SOLR
  32. statistics
  33. Success Message macro
  34. syntax
  35. user
  36. user profile
  37. velocity macros
  38. Warning macro
  39. wiki
  40. Wiki Application
  41. wiki macro
  42. wysiwyg
  43. XWiki Applications
  44. xwikiattachment_archive table
  45. xwikiattachment_content table
  46. xwikiattachment table
  47. xwikiattrecyclebin table
  48. xwikiproperties table

[Display all tags from this space]

External Links