TimThumb WordPress MU WordPress BetterSecurity error? (1 post)

  1. redhorizon0289
    Posted 2 years ago #

    Hello group,
    I have a mutlisite setup for WordPress using a premium theme that uses TimThumb. When doing an export from one site to the other all the thumbnails break but showup in the media library of the newly created site. I tend to think this might come back to a wordpress better security settings. I am using the subdomain format, I have added all the sites / subdomains to the array for TimThumb and turned off the "filter suspicious URL queries" in WordPress Better Security but the error persists. Perhaps a directory permission error? Any light you can shed would be fantastic.

    Warning: fopen(./temp/291de51c0c7c902aebd2274d07968dad.png) [function.fopen]: failed to open stream: No such file or directory in /home/content/63/7309663/html/gridone/wp-content/themes/trademark/lib/timthumb/timthumb.php on line 668

    Warning: curl_setopt(): supplied argument is not a valid File-Handle resource in /home/content/63/7309663/html/gridone/wp-content/themes/trademark/lib/timthumb/timthumb.php on line 676

    Warning: fclose(): supplied argument is not a valid stream resource in /home/content/63/7309663/html/gridone/wp-content/themes/trademark/lib/timthumb/timthumb.php on line 686

    Warning: Cannot modify header information - headers already sent by (output started at /home/content/63/7309663/html/gridone/wp-content/themes/trademark/lib/timthumb/timthumb.php:668) in /home/content/63/7309663/html/gridone/wp-content/themes/trademark/lib/timthumb/timthumb.php on line 808
    local file for http://g1usa.gridone.us.com/wp-content/uploads/sites/18/2013/08/EPRCable.png can not be created
    Query String : src=http://g1usa.gridone.us.com/wp-content/uploads/sites/18/2013/08/EPRCable.png&w=580&h=200
    TimThumb version : 1.15


Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

  • RSS feed for this topic
  • Started 2 years ago by redhorizon0289
  • This topic is not resolved
  • WordPress version: 3.6.1