Omega Tools could not create the directory temporary... [#1248774]

Comment	File	Size	Author
#3	omega_error.PNG	4.3 KB	apmsooner
#3	omega_temp_directory.PNG	18.77 KB	apmsooner

Comment #1

fubhy CreditAttribution: fubhy commented 18 August 2011 at 17:13

Category:	bug	» support
Priority:	Critical	» Normal
Status:	Active	» Fixed

The temporary:// folder must be writeable. Looks like the folder you have set as temporary:// folder in your Drupal installation is not configured properly.

Log in or register to post comments

Comment #2

apmsooner CreditAttribution: apmsooner commented 18 August 2011 at 20:01

I havn't modified the temporary folder settings on any of the accounts i'm getting this error on. The only thing that comes to mind is that these accounts are all in development stage and thus clean urls are not enabled. Is clean urls a requirement for this module to write to the directory? If so, any way to get around that?

Log in or register to post comments

Comment #3

apmsooner CreditAttribution: apmsooner commented 23 August 2011 at 21:23

Status:

Fixed

» Active

File	Size
omega_temp_directory.PNG	18.77 KB
omega_error.PNG	4.3 KB

I'm reopening this issue with attached screenshots of the error i'm receiving and my files directory setting. Please advise what's wrong with my setup here... I have the default settings that Drupal installs with.... didn't change a thing so what do you advise i'm doing wrong here please?

Log in or register to post comments

Comment #4

apmsooner CreditAttribution: apmsooner commented 23 August 2011 at 21:57

Possibly this is a core issue?

I'm seeing this show up in other modules like here: http://drupal.org/node/981188

My temp directory is writeable. I thought it might be a clean urls issue but on another site where the domain is propagated and clean urls are enabled, i still can't get omega tools to write to the temp folder. I wish i knew what on earth if anything i'm missing here... any advice is appreciated.

Thanks

Log in or register to post comments

Comment #5

GeminiAgaloos CreditAttribution: GeminiAgaloos commented 18 November 2011 at 08:56

Assigned:

Unassigned

» GeminiAgaloos

This could be resolved by going to your web server (via ftp or ssh) and creating a new temp folder just above your webroot folder.

Make note of the full path to the folder you just created. For example: /home/user/temp and make sure that folder is writable.

Back to your Drupal site, go to Configuration --> Media --> Filesystem (or go to the url path admin/config/media/file-system)

Enter your full temp path information under "Temporary Directory"

This should fix your issue. The problem is that the default entry "/tmp" in this field either does not exist or is not writable.

Log in or register to post comments

Comment #6

himerus CreditAttribution: himerus commented 17 February 2012 at 15:58

Assigned:	GeminiAgaloos	» Unassigned
Status:	Active	» Fixed

Log in or register to post comments

Comment #7

2 March 2012 at 16:00

Status:

Fixed

» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Log in or register to post comments

Comment #8

apmsooner CreditAttribution: apmsooner commented 2 March 2012 at 16:11

FYI, the actual solution to my problem with this is that while working on sites where the domain is not propagated and therefore clean urls are disabled, i had to set the file path to this: ../tmp

Omega tools works fine when this happens and probably wouldn't hurt to have in documentation because developing a new theme is most likely going to take place in a devel environment.

Log in or register to post comments

Comment #9

CaseyShultz CreditAttribution: CaseyShultz commented 15 March 2012 at 23:14

Version:	7.x-3.0-rc2	» 7.x-3.0-rc4
Status:	Closed (fixed)	» Active

I stumbled on this thread having the same problem. The problem I experienced is because the default /tmp directory is shared between all the users and it seems that each website it set up on my VPS has its own username so when I first created a subtheme for website1, it created a folder /tmp/omega-tools with the owner set to website1 and the permissions set to 755. When I tried to create the subtheme for website2 it attempted to write to the /tmp/omega-tools directory but was disallowed.

I think I'll have to add a step to my workflow to make a temp directory for each site just above the web root as was indicated above.

Log in or register to post comments

Comment #10

dalessioa CreditAttribution: dalessioa commented 20 June 2012 at 01:39

The ".../tmp" solution worked great for me. Thanks!

Log in or register to post comments

Comment #11

frost CreditAttribution: frost commented 5 March 2013 at 12:35

Thanks CaseyShultz for that -- I have a dedicated server and it was the same problem - in the server's /tmp directory there was an omega-tools subdir that had been created the first time I used Omega Tools for one of my websites, so it was owned by that user and didn't have enough permissions for other users (it had drwxr-xr-x, which means that only the owner could write to the folder)

My solution was to SSH to the server as root and issue:
chmod a+xrw /tmp/omega-tools

Which gives all users full rights to that directory.
Obviously you need SSH rights and enough rights to change permissions on that file - as I have root access that isn't a problem, but might not be possible with shared hosting.

Two possible ways to address this in the code would be for Omega Tools to delete the temp directory after its done using it, or else Omega Tools could give full rights to all users to the directory when it creates it.