WCat
Forum Replies Created
-
Forum: Plugins
In reply to: [EWWW Image Optimizer] cannot get this working after update.http://codex.wordpress.org/Hardening_WordPress
“All files should be owned by your user account, and should be writable by you. Any file that needs write access from WordPress should be writable by the web server, if your hosting set up requires it, that may mean those files need to be group-owned by the user account used by the web server process.”thats from codec. user:www-data. 755 and 644, except for uploads(and wp-config.php). I self host so group ownership isn’t necessary or appealing to me.
www-data group has read and write on wp-content/ewww folder.
I shouldnt be seeing that warning. Restoring last version of the plugin doesnt do it. I’ll bump up the permissions on htdocs to make it writable to check but i dont want to keep my webroot owned by www-data.Also I dont have issues uploading.
Thanks for the quick reply. If I am missing something I apologize for wasting your time. Ill check it out tomorrow and get back to you.Forum: Plugins
In reply to: [EWWW Image Optimizer] cannot get this working after update.update: reset APC cache and the settings page wanted gifsicle updated. downloaded latest version of plugin unzipped renamed gifsicle removing -linux and uploaded. That seems to have worked everything is reading ok now but the content box warning is back to
EWWW Image Optimizer couldn’t install tools in /var/www/example.com/htdocs/wp-content/ewww/. Please adjust permissions or create the folder. If you have installed the tools elsewhere on your system, check the option to ‘Use system paths’. For more details, visit the Settings Page or the Installation Instructions.
I also went to reoptimize a few images which failed
content/uploads/2013/03/T4yADGa.jpg is not writable.Im going to restore server backup again and wait for an update. Should my image files themselves be group writable? It wasnt necessary before. I am sure this is some stupid little thing I am not thinking of.
ps didnt mean to sound like a d-bag this is a great plugin and I have become reliant on it especially for one client. I just am a little frazzled as to why I cant get the darn thing working like it was before the update.
jpegtran path: /var/www/example.com/htdocs/wp-content/ewww/jpegtran
optipng path: /var/www/example.com/htdocs/wp-content/ewww/optipng
gifsicle path: /var/www/example.com/htdocs/wp-content/ewww/gifsicle
pngout path:
disabled functions: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority
bundled jpegtran permissions: 0755
bundled gifsicle permissions: 0774
bundled optipng permissions: 0755
wp-content/ewww permissions: 0775
jpegtran checksum: e2ba2985107600ebb43f85487258f6a3
gifsicle checksum: 44273fad7b3fd1145bfcf35189648f66
optipng checksum: 4eb91937291ce5038d0c68f5f2edbcfd
pngout checksum:
user: www-data
Operating environment: Linux 3.2.0-23-virtual #36-Ubuntu SMP Tue Apr 10 23:58:38 UTC 2012 i686I would remove varnish. and use apc and memcached, also http://wordpress.org/extend/plugins/hyper-cache/. it looks to me like varnish is serving its own ip. Varnish adds a layer of complexity that imo isnt worth the headache by the time your done futzin with the vcl file to handle cookies and find that your site isnt any faster. apc is easy enough and installing memcached is a 3 step ordeal with no config neccesary.
see http://rtcamp.com/tutorials/why-we-never-use-varnish-with-nginx/
they also have a great tutorial for installing APC