WordPress.org

1. enungman
   Member
   Posted 2 years ago #

   I just upgraded from version 1.05 to 1.06 and i get the following message:

   Warning: chmod() [function.chmod]: Operation not permitted in /ajfix.se/public_html/wp-content/plugins/wp-portfolio/wp-portfolio.php on line 1470

   Line 1470 says:
   

   // Try to make the directory writable
   		chmod($actualThumbPath, 0777);

   but the directory "cache" already has permission 777 and it worked prior to upgrade..

   I tried downgrading to 1.05 again, but the error remains.. Any ideas?!
   http://www.ajfix.se/portfolio

2. Dan Harrison
   Member
   Posted 2 years ago #

   That's a new bit of code I added to handle permission problems people were having. Try changing that line from:

   chmod($actualThumbPath, 0777);

   @chmod($actualThumbPath, 0777);

   That should hide the error. Please let me know to say if it does.

   Dan

3. enungman
   Member
   Posted 2 years ago #

   Sorry..
   My computer broke down and i haven't been able to log in and answer.

   I got a new error now instead of the old one..
   

   Warning: fopen(/ajfix.se/public_html/wp-content/plugins/wp-portfolio/cache/992442113a02a477654858844aca3964.jpg) [function.fopen]: failed to open stream: Permission denied in /ajfix.se/public_html/wp-content/plugins/wp-portfolio/wp-portfolio.php on line 1697
   
   Warning: fputs(): supplied argument is not a valid stream resource in /ajfix.se/public_html/wp-content/plugins/wp-portfolio/wp-portfolio.php on line 1698
   
   Warning: fclose(): supplied argument is not a valid stream resource in /ajfix.se/public_html/wp-content/plugins/wp-portfolio/wp-portfolio.php on line 1699

4. Dan Harrison
   Member
   Posted 2 years ago #

   I'm sorry, I don't have any time to debug it in any depth for at least a momth.

   It appears you have extremely strict rules on your server, which is causing the issue. Opening files is a critical part of the plugin, without that functionality, the plugin cannot work.

   Sorry,
   Dan

5. enungman
   Member
   Posted 2 years ago #

   No problem Dan!

   For now.. i simply removed those three lines from the wp-portfolio.php file and now the plugin works like a charm :-) For now that is :-P

   Thanks for a great plugin
   (which will be better when i get this security issue to work)

Topic Closed

This topic has been closed to new replies.