Bug #9737

export:bulk single-slug throws write permission error when it shouldn't

Added by Mike Gale about 6 years ago. Updated about 6 years ago.

Status:VerifiedStart date:04/25/2016
Priority:MediumDue date:
Assignee:-% Done:


Target version:Release 2.3.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:


To reproduce: try export:bulk --single-slug task, specify a file name that doesn't exist but that you should have create/write permissions to

Result: cannot write file exception
Expected result: for it to create the file

Note: this task cannot create new directories - but --single-slug option requires that you give a full path to the final file, including file name - and the file name does not have to be based on the slug - e.g. you could export cooke-fonds to /path/to/my/ead-output.xml, so long as /path/to/my/ already exists.


#1 Updated by Mike Gale about 6 years ago

  • Category set to EAD
  • Status changed from New to QA/Review
  • Assignee changed from Mike Gale to Dan Gillean

#2 Updated by Mike Gale about 6 years ago

This was a regression due to a minor change I made last week in qa/2.3.x, so the bug hasn't been around long.

#3 Updated by Dan Gillean about 6 years ago

  • Description updated (diff)
  • Status changed from QA/Review to Verified
  • Assignee deleted (Dan Gillean)

Updated issue description for more clarity. Works!

Also available in: Atom PDF