keithslater
Forum Replies Created
-
I do believe the problem is corrupted images. I added some code to wp_read_image_metadata so that every time it’s called, it logs out what the filename name is. Then when I receive the errors I compare the time to the log file I created. I have discovered that the files seem to load correctly but are some how corrupted and wordpress can’t read them. When I run them through the regenerate thumbnail plugin, it spits out javascript on those images. Luckily there’s only a few of them.
Alright so I know the thumbnails are being generated. I actually used that re-generation plugin and regenerated all of the thumbnails just in case.
We also set the memory limit to 1GB and it is using more than that now. Here is the error:
PHP Fatal error: Allowed Allowed memory size of 1073741824 bytes exhausted (tried to allocate 3959147893 bytes) in blog/wp-admin/includes/image.php on line 281
Thanks for taking the time to look. The blog is located here – http://www.mosbybuildingarts.com/blog/2014/06/19/opening-up-a-home-by-raising-the-ceiling/. I disabled the plugin for now since we were getting so many errors. It didn’t seem like we were getting it on every page load though.
I just checked the thumbnail settings and they are being saved as 150×150. What directory contains the cached images? I will check and make sure they are actually being cached.
I believe they resize most of their images before uploading. I quickly looked and most of the images are sized at 600 width. I did see some up to 1000 width.
I also noticed that sometimes the related image didn’t show up for some of the blog posts until I refreshed the page. Does that help at all?
Forum: Plugins
In reply to: [SEO Friendly Images] Notice: Undefined offset: 0This issue popped up for me as well. I manually fixed it for now by doing the following:
Line 185:
if (isset($source[0])) { $titletext_rep=str_replace("%name", $source[0], $titletext_rep); }Line 207
if (isset($source[0])) { $alttext_rep=str_replace("%name", $source[0], $alttext_rep); }This is just a hack so you don’t receive the errors. Hopefully the author will fix this issue permanently.