Does any one know what these errors mean in OOP?
beckyjohnson - February 27, 2009 - 17:04
We hired a company to program some custom functionality for us and they used OOP to extend the flexibility of Drupal. Recently I decided to make a copy of our site for a test server we were going to use. I installed site nearly perfectly on our back up server with only one error, this:
warning: mkdir() [function.mkdir]: Permission denied in /var/www/vhosts/wimaxforum.org/subdomains/beta/httpdocs/sites/all/modules/oop/oop.module on line 208.
warning: file_put_contents(sites/sitename/files/oop/oop_module_path.module) [function.file-put-contents]: failed to open stream: No such file or directory in /var/www/vhosts/sitename/subdomains/beta/httpdocs/sites/all/modules/oop/oop_module.module on line 152.
warning: mkdir() [function.mkdir]: Permission denied in /var/www/vhosts/wimaxforum.org/subdomains/beta/httpdocs/sites/all/modules/oop/oop.module on line 208.
warning: file_put_contents(sites/sitename.org/files/oop/oop_module_path.module) [function.file-put-contents]: failed to open stream: No such file or directory in /var/www/vhosts/sitename.org/subdomains/beta/httpdocs/sites/all/modules/oop/oop_module.module on line 152.Could someone explain what these mean and how I can go about fixing them? I looked at these lines of code they mention but it means nothing to me..
Any insight would be great,
Becky
Never used OOP but it looks
Never used OOP but it looks like the permissions for the directory are incorrect. OOP is trying to make a directory and it isn't allowed. You'll have to CHMOD the files folder to 777
I would start with this
I would start with this error
warning: mkdir() [function.mkdir]: Permission denied in /var/www/vhosts/wimaxforum.org/subdomains/beta/httpdocs/sites/all/modules/oop/oop.module on line 208.What directory is it trying to make and where is it trying to make it.
Given that check the information on the live site and check the ownership and permissions there.
I'm pretty sure its trying to
I'm pretty sure its trying to do something in the files directory, no?
file_put_contents(sites/sitename.org/files/oop/oop_module_path.module)
Ok it's weird. I took all
Ok it's weird. I took all your advice and made my files folder chmod 777 and it took the error away. Also what it did was screw up my css, I had it optimized to squish all into one file and when I refreshed the page after the chmod 777, it said something was wrong with the CSS folder in the files folder that had all these optimized css files in it. So then, I un-chomd 777 the files folder and that fixed the css problem, also oddly, which I don't understand two things happened: the OOP error is now gone (yay) but I am left with one more problem. In the performance area the enable/disable css and js is grayed out and set to disabled. I want it disabled but I don't think it actually, really disabled it. I am now getting this error:
warning: unlink(sites/sitename/files/css/0cec0532aaa4dccfc954a0878df91bac.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.warning: unlink(sites/sitename/files/css/1320e502bf4ad1a6042d370856e1e286.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/27020a66d43e1098f4ba84ee5325daf6.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/3defb697297b4f14c69041ca8e75ebaa.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/4be17a427aed67b693112991c2c54d13.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/6455e8cdf84581da495c34e8dcb5392c.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/662552749a03089f43266eeeb07e1503.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/6a810c85ee86c8605e9da757b9336746.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/7f868f7c280358966a2b16b8f908a164.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/7fffb456cfd53cb44e6eb2699cc1423a.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/c32e418a9502b13ad0935505771c9bae.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/d5632604b5d853ca33660afcaebe9c3d.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
warning: unlink(sites/sitename/files/css/e8a7c247dd881a6e2c623f17afc7cd73.css) [function.unlink]: Permission denied in /var/www/vhosts/sitename/subdomains/beta/httpdocs/includes/file.inc on line 435.
Which makes no sense to me.
Any more insight?
Becky
Hmmm! Well the OOP error
Hmmm!
Well the OOP error probably went away because it made the file it needed to when the chmod was 777. Unlink probably has something to do with a symlink that existed/exists/is created?. I'm guessing when the permissions were 777 whatever is trying to unlink the css from a directory succeeded and then your css's were 'gone.'
As far as how to fix it, I dunno. If you are able to it would be worthwhile to see how the directory permissions and structures existed on the previous host.
I know that themes which have
I know that themes which have customizable color schemes create css files, I'm assuming that they must symlink the custom css file to the theme's css file. It might have something to do with your theme configuration? See what options are available. I really think the files directory should always be CHMOD 777
Ok I fixed this. I found out
Ok I fixed this. I found out I had to delete the css folder in my files folder that contained the compressed css. After that, it was peachy. Thanks for the information though, because it was enlightening.
Becky