Title: Illegal string offset errors with Thesis theme
Last modified: August 21, 2016

---

# Illegal string offset errors with Thesis theme

 *  Resolved [asmichael](https://wordpress.org/support/users/asmichael/)
 * (@asmichael)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/illegal-string-offset-errors-with-thesis-theme/)
 * We’re running WP 3.8.3 running the Thesis them and recently updated our plugin
   to 7.4.4.
 * With that, we started receiving the following error on specific pages:
    [http://thethriftycouple.com/wp-content/uploads/2014/04/error-from-nextgen.jpg](http://thethriftycouple.com/wp-content/uploads/2014/04/error-from-nextgen.jpg)
 * Warning: Illegal string offset. ‘width’ in …media.php on line 252
    Warning: Illegal
   string offset. ‘height’ in …media.php on line 252
 * I understand from another ticket that this might be due to another plugin not
   implementing a call correctly to `wp_get_attachment_metadata()`:
    [http://wordpress.org/support/topic/warning-illegal-string-offset-6](http://wordpress.org/support/topic/warning-illegal-string-offset-6)
 * In the meantime, I have added a defined Image URL for that page (understood –
   that’s best practice anyway) but am concerned about all the other pages that 
   might be showing this error.
 * I did try to go in and find the option “WP Auto-Resize” under the General tab
   in the settings but cannot find it. Even if I did, is this just a workaround 
   that might have other ill effects?
 * Should this bug be handled differently with the different version of NGFB? I 
   apologize but wonder if this is happening with other plugins wonder if there 
   is a better way to handle this – possibly by checking whether the height/image
   is missing upon call to `wp_get_attachment_metadata()` and handling that error
   instead of generating the warnings back to the user?
 * Thank you so much for this plugin – it truly has solved many of our problems.
   My request it to find a fix and give you update that this is a problem with this
   specific configuration – assuming others might have this issue as well.
 * [https://wordpress.org/plugins/nextgen-facebook/](https://wordpress.org/plugins/nextgen-facebook/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [JS Morisset](https://wordpress.org/support/users/jsmoriss/)
 * (@jsmoriss)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/illegal-string-offset-errors-with-thesis-theme/#post-4813819)
 * The error is because `wp_get_attachment_metadata()` did not return any information
   for the image size in question. It’s assumed the image size exists because an
   earlier call to `image_make_intermediate_size()` should have created it (if it
   didn’t exist). And that’s where the problem is – never assume. 😉
 * I’ll add an extra check to control that condition and release an update shortly.
 * Meanwhile, make sure the “Auto-Resize Images” option (on the NGFB Advanced settings
   page) is checked. This should create the missing sizes. If WordPress can’t create
   the image size, then you might have to uncheck the “Ignore Small Images” option–
   at least until I can push out the next version (probably later today).
 * Thanks,
 * js.
 *  Plugin Author [JS Morisset](https://wordpress.org/support/users/jsmoriss/)
 * (@jsmoriss)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/illegal-string-offset-errors-with-thesis-theme/#post-4813826)
 * Correction – it’s the width / height information for the original / full-size
   image that’s missing from the image metadata. That’s not good. You might want
   to use a plugin like “Simple Image Sizes” to regenerate your image sizes and 
   fix the WordPress image metadata.
 * I’ll code an appropriate error in the upcoming version.
 * js.
 *  Plugin Author [JS Morisset](https://wordpress.org/support/users/jsmoriss/)
 * (@jsmoriss)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/illegal-string-offset-errors-with-thesis-theme/#post-4813920)
 * Are you ok with installing plugins from ZIP files? If so, you can install the
   following new version, and it should fix your problem. 😉
 * [http://downloads.wordpress.org/plugin/nextgen-facebook.7.4.5.zip](http://downloads.wordpress.org/plugin/nextgen-facebook.7.4.5.zip)
 * If you need help uninstalling the old version and installing this ZIP file, see
   here: [http://wordpress.org/plugins/nextgen-facebook/installation/](http://wordpress.org/plugins/nextgen-facebook/installation/)
 * js.
 *  Thread Starter [asmichael](https://wordpress.org/support/users/asmichael/)
 * (@asmichael)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/illegal-string-offset-errors-with-thesis-theme/#post-4813965)
 * Wow – thank you so much for all your responses and the quick resolution! I am
   ok to install it via zip and will get that done later today when I have access.
 * Thanks so much!
    Alex
 *  Plugin Author [JS Morisset](https://wordpress.org/support/users/jsmoriss/)
 * (@jsmoriss)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/illegal-string-offset-errors-with-thesis-theme/#post-4813967)
 * Never mind – I found some time to test and released v7.4.5 earlier today. You
   should see the update in your WordPress admin interface. 😉
 * js.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Illegal string offset errors with Thesis theme’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/nextgen-facebook_f2c17e.svg)
 * [NextGEN Facebook](https://wordpress.org/plugins/nextgen-facebook/)
 * [Support Threads](https://wordpress.org/support/plugin/nextgen-facebook/)
 * [Active Topics](https://wordpress.org/support/plugin/nextgen-facebook/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/nextgen-facebook/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/nextgen-facebook/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [JS Morisset](https://wordpress.org/support/users/jsmoriss/)
 * Last activity: [12 years, 1 month ago](https://wordpress.org/support/topic/illegal-string-offset-errors-with-thesis-theme/#post-4813967)
 * Status: resolved