I upgraded from 184.108.40.206 to 220.127.116.11 and the default images on each post no longer showed. I could not see how to fix it so re-installed 18.104.22.168. Any help resolving this would be much appreciated. Philip
Default image not showing on upgrade(22 posts) (2 voices)
I've done the timthumb troubleshooting and can't seem to fix the problem. The best I can achieve is using the latest timthumb code 2.8.10 within your upgrade 22.214.171.124. The result is bfthumb images where the zoom cropping doesn't work (ie all the image compressed into the thumbnail). This is only from my computer and browser (Firefox). When I try it from my laptop with other browsers (Explorer and Chrome) no images come up either in the posts or the bfthumbs.Also I am not able to change file permissions from 750 to 755 or 777. It simply reverts back every time to 750.
When I switch back to 126.96.36.199 everything is fine. Which seems to indicate that its not a problem with hosting or with the file permissions because this is 750 and it works fine.
Sorry to be a pain but I really want to upgrade.
I'm getting this error message when running timthumb.php directly on your website:
Warning: chmod() has been disabled for security reasons in /web2/user24239/website/wp-content/themes/bigfeature/library/timthumb/timthumb.php on line 238
It is just a warning, but this causes timthumb not to work. The solution is to turn off warnings. You can do that by adding this line to the top of timthumb.php (after <?php):
Many thanks for looking into it and so quickly!! I'm afraid, though, its still not working. Are there any other directions you can suggest e.g. getting the hosting company to renable chmod() or can I do this directly by going into the mySQL database or is this irrelevant?
still getting the same error message, did you add that line of code to the timthumb.php? it should solve it. You can instead add this line of code to the top of the functions.php (preferably in a child theme) to hide warnings (after the <?php line):
error_reporting(E_ALL ^ E_WARNING);
Again, I very much appreciate your attention to my problem. I am sticking with it because I like your theme so much. However I am still not having success. First the reason that you still get the error message is that I have to switch back to the 188.8.131.52 version of bifgeature so that the website can still function without problem and I am hesitant about introducing any additional code into somehthing that works.
So yes, I did put the code into the first line of timthumb.php. for the updated version (184.108.40.206). This didn't work. Then I made a child theme and used the function.php and things got worse - screen shot: http://www.kassanis.co.uk/bf-update-difficulty/.
The only small progress that I can make is if I use the timthumb.php file from bf 220.127.116.11. within bf 18.104.22.168. With this all the default images show. However the bfthumbs do not crop but show the whole image compressed into the container. In any case using old timthumb code does not seem to be the right way to proceed but it may give an indication of what is causing the problem.
With this hosting provider I can only host one website. However I have another provider for my other site (GoDaddy) where I can host multiple sites. Therefore I am doing a fresh installation of wordpress and intend to install bigfeature 22.214.171.124 and rebuild the website by importing the post and pages etc. For the moment this would be accessed under another URL but if successful would re-point this website's url.
It seems a rather long way round to get an update. Are there any other avenues that you think I could explore?
It seems a rather long way round to get an update. Are there any other avenues that you think I could explore?It is, and I thought turning off warnings would fix it, but maybe the hosting is overriding this, so it must be turned off in a .htaccess file instead. Here's a method to log php errors instead of displaying then.
First the reason that you still get the error message is that I have to switch back to the 126.96.36.199 versionok. So I never tested the timthumb with version 188.8.131.52? Do you know if it has the same warning? This can be tested by using the direct url to timthumb (with a new image width). After running timthumb the second time with a new image width it works, because it uses the cached image. This show that timthumb works, and it's just the warning that is the problem.
Maybe the easiest way is just to remove chmod from timthumb. The strange thing is that the timthumb version that comes with version 184.108.40.206 the theme doesn't have any chmod, but 220.127.116.11 does. This proves that this can't be the problem in the new version, and also that I have never tested that version on your server, so I can't say what the problem is.
I recommend to setup a test wordpress with the new version of the theme, just so I can see how the new timthumb is working on your hosting. Maybe it was just that the cache folder was not made writable, and you switched to 18.104.22.168 before that was done right. Also note that some hosting setups do not allow the folders to be set as 777 (fully writable by all users). I have had cases where timthumb failed because the cache folder did not have the allowed rights (755 usually work).
Thanks - you've given quite a few things to work on. I'll let you know how I get on. It may be a few days now.
It is, and I thought turning off warnings would fix it, but maybe the hosting is overriding this, so it must be turned off in a .htaccess file instead. Here's a method to log php errors instead of displaying then.
I have followed this up but don't have the confidence to insert code into the right place in the .htaccess file.
I recommend to setup a test wordpress with the new version of the theme, just so I can see how the new timthumb is working on your hosting.
I've done this http://kassanis.co.uk/wordpress-test/?page_id=7 and maybe you could check it out? I have put the code
error_reporting(0);at the beginning of the file.
I did try to do the url to timthumb thing. Not sure if I fed in the right link into the browser but this is what came back as a error message:
The requested URL /website/wordpress-test/wp-content/themes/bigfeature/library/timthumb/timthumb.php was not found on this server.
Apache/2.2.3 (CentOS) Server at http://www.kassanis.co.uk Port 80
I can confirm that timthumb is not working with 22.214.171.124 on your server. It can't find the source image, so it got nothing to do with the cache folder.
The best I can achieve is using the latest timthumb code 2.8.10 within your upgrade 126.96.36.199. The result is bfthumb images where the zoom cropping doesn't work (ie all the image compressed into the thumbnail).Upload timthumb 2.8.10 to the test wp installation. I read several support posts with similar issues, and that they fixed this issue. Something you also confirmed since it worked when you tested it. I looked at the code concerning zoomcrop, and it should work as the other version, but if it's not I will figure out how to fix it.
I'm afraid that I'm not so lucky this time round, or maybe I was mistaken before because I was trying so many options at the time. Now it doesn't deal with the default images at all.
Anyway the bf 188.8.131.52 on wordpress-test now has timthumb 2.8.10 (and timthumb has the
error_reporting(0);at the top). Also I deleted and replaced the cache file. Do you think you can still figure something out?
Your support much appreciated!
The only reason I used timthumb 2.8 and not 2.8.10 in version 184.108.40.206 of the theme is that the newest version doesn't work localhost (the developement environment on my pc). It has the same problem, that it doesn't find the source file, so maybe if I get it working here it will for you too.
I found the problem in windows with timthumb 2.8.10, but since you are using linux I'm not sure this fix will work for you (it works on my linux hosting though). You can download the fixed version here. Upload it to the test wp installation and see if it works.
If it doesn't I would like to try to fix it for CentOS too, because I suspect it is an OS specific problem, like it was on windows. If you want this, you can create a ftp account for me to upload timthumb to the test installation.
I am glad that you were able to fix the windows version. As you suspected it doesn't work for linux. I would be glad if you could fix it for CentOS. However my hosting company (Easily.co.uk) are not making life very easy because there is no obvious way to create another ftp user account. I am in dialogue with them to find out how to create another account.
In the meanwhile I have also asked them to fix the permissions so that we can have 777 on both the cache folder and the timthumb.php file. So all in all it seems as though Easily are not making things very easy.
If you can find a secure way of doing it, I'll just send you all my ftp account details. Perhaps you could suggest a method or doesn't it matter now that I am on the trail of them fixing the permissions?
I am in dialogue with them to find out how to create another account.So you don't have a control panel where you can create more ftp accounts? sounds like a very limited hosting solution. It is better with a separate ftp account with only access only to the test area, than full access, but if you don't get an answer back to the hosting support then you can send me the details for the full access one (use the contact form on the sidebar here (must be logged in to see it)). Also include login details for Wordpress on the test installation.
In the meanwhile I have also asked them to fix the permissions so that we can have 777 on both the cache folder and the timthumb.php file.They don't really need to be 777, 755 is good enough in most cases. The chmod error from the older version of timthumb is not a problem with version 2.8.10, so it's no necessary to add the error_reporting in the top either for that one. The problem here seems to be the internal file path, and not the file rights.
So you don't have a control panel where you can create more ftp accounts? sounds like a very limited hosting solution.
That's right and this whole escapade has led me to the conclusion that I need to transfer to another hosting provider.
(use the contact form on the sidebar here (must be logged in to see it)).
Unfortunately this doesn't exist for me even when logged in. I did, however, use the contact form which is included in the documentation section of this site. I don't know whether you made it fully functional or whether it is just a sample. If my message gets through perhaps you ccould let me know through the forum and I will sent you the ftp and log in details for Wordpress on the test installation.
Found the problem. The DOCUMENT_ROOT variable is set wrong. It is set to
/admin/www/, but the right root folder should be
/home/user24239/. I added a constant to timthumb, LOCAL_FILE_BASE_DIRECTORY, to override the $_SERVER php variable, and it works.
You can use the uploaded timthumb on your other installation and it will work, but the permanent solution is to get the hosting support to change the DOCUMENT_ROOT variable.
Thank you so much and I appreciate the support you've provided. I'll go through what you've come up with tomorrow and I'll also follow up with the hosting support.
Just to let you know that I have now upgraded and it's working fine. Once again thanks!
I have asked the hosting people to change the DOCUMENT_ROOT variable. If I am successful with the request, should I revert to the original timthumb or can I leave the one with the extra code?
If I am successful with the request, should I revert to the original timthumb or can I leave the one with the extra code?You can upload timthumb 2.8.10 (get it here) since the one that comes with the theme is an older version (2.8). The one I uploaded with the fix, is also version 2.8.10, so you can just leave it there too, but it's best to test if the new unchanged timtumb works with the hosting support changes. Also since it will be that one used in the next version of the theme.
You must log in to post.