ATutor

Unable to create import directory

• innaz
  

  2004-11-18 14:26:43

  Unable to create import directory

  Hello,
  
  I am using:
  
  ATutor 1.4.2
  php4.3.9
  Apache1.3.33
  Internet Explorer 6.0
  WindowsXP
  
  I have created a new course on our server - this worked fine. Now I am trying to import a content package into my new course - and I am getting an error message:
  "Unable to create import directory"
  
  The content package that I am trying to add is fine - I have used it with the localhost installation of ATutor and everything worked well.
  
  What could be the problem here?
  
  I have contacted my sysadmin, and he tells me that the permissons are 777.
  
  Any ideas?
  
  Thanks,
  
  Inna

• innaz
  

  2004-11-18 15:53:15

  Unable to create import directory - RESOLVED

  Hello,
  
  First of all I did find an answer to my question in FAQs. But it did not help. I have opened both content and content/import directories, but still was getting the same error message.
  
  So I noticed that on my local system another directory was getting created: in tools/ims directory, the system created a new directory called "AT_CONTENT_DIRimport".
  
  Once the sysadmin changed permissions on the server for the tools and tools/ims directories, I was able to import content files without any problems.
  
  Hope this helps someone else. :-)
  
  Inna

• Trevor
  

  2004-12-03 13:36:47

  content/import worked

  Of course I had this problem as well. I found changing the permissions on the content/import directory to match the content directory did work for importing content packages. Is it ok to leave as read/write for others though?
  
  Trevor D

• greg
  

  2004-12-03 14:08:44

  Recursively writable

  The Content directory, should have been set to be recursively writable (including all subdirecties) during the install process, so you should not need to separately set the import directory to be writable. It needs to remain writable. Perhaps XP handles subdirectory permission differently.
  
  Positioning the content directory outside your Webserver's document directory is a good idea, so there is no chance of an outsider taking advantage of the writable directory. Though the chance is small, a web accessible writable directory could be compromised.