mirror of
				https://github.com/paperless-ngx/paperless-ngx.git
				synced 2025-10-30 03:56:23 -05:00 
			
		
		
		
	Add 2 warnings about potential path length issues
This commit is contained in:
		| @@ -267,6 +267,12 @@ The filenames generated by this command follow the format | ||||
| paperless to use `PAPERLESS_FILENAME_FORMAT` for exported filenames | ||||
| instead, specify `--use-filename-format`. | ||||
|  | ||||
| !!! warning | ||||
|  | ||||
|     If exporting with the file name format, there may be errors due to | ||||
|     your operating system's maximum path lengths.  Try adjusting the export | ||||
|     target or consider not using the filename format. | ||||
|  | ||||
| ### Document importer {#importer} | ||||
|  | ||||
| The document importer takes the export produced by the [Document | ||||
|   | ||||
| @@ -336,6 +336,13 @@ value. | ||||
|     However, keep in mind that inside docker, if files get stored outside of | ||||
|     the predefined volumes, they will be lost after a restart of paperless. | ||||
|  | ||||
| !!! warning | ||||
|  | ||||
|     When file naming handling, in particular when using `{tag_list}`, | ||||
|     you may run into the limits of your operating system's maximum | ||||
|     path lengths.  Files will retain the previous path instead and | ||||
|     the issue logged. | ||||
|  | ||||
| ## Storage paths | ||||
|  | ||||
| One of the best things in Paperless is that you can not only access the | ||||
| @@ -392,7 +399,7 @@ structure as in the previous example above. | ||||
|     If you adjust the format of an existing storage path, old documents | ||||
|     don't get relocated automatically. You need to run the | ||||
|     [document renamer](/administration#renamer) to | ||||
|     adjust their pathes. | ||||
|     adjust their paths. | ||||
|  | ||||
| ## Celery Monitoring {#celery-monitoring} | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user
	 Trenton H
					Trenton H