Title: Illegal string offset
Last modified: January 29, 2017

---

# Illegal string offset

 *  Resolved [funsail](https://wordpress.org/support/users/funsail/)
 * (@funsail)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/)
 * Illegal string offset id’ in wp-content/plugins/ewww-image-optimizer/common.php
   on line 2675
 * pending’ in /plugins/ewww-image-optimizer/common.php on line 2668
 * require_once(): Failed opening required ‘/plugins/ewww-image-optimizer/classes/
   wp-async-request.php’ (include_path=’.:/opt/alt/php56/usr/share/pear:/opt/alt/
   php56/usr/share/php’)

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

 *  [Alias79](https://wordpress.org/support/users/alias79/)
 * (@alias79)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/#post-8715727)
 * Same here 🙁
 * mod_fcgid: stderr: PHP Warning: Illegal string offset ‘pending’ in …./plugins/
   ewww-image-optimizer/common.php on line 2668, referer: /wp-cron.php?doing_wp_cron
   =1485781443.0465290546417236328125
 * At the same time, I’m getting messages of “server saturated”, that’s why I have
   found this error.
    -  This reply was modified 9 years, 4 months ago by [Alias79](https://wordpress.org/support/users/alias79/).
 *  Plugin Author [Shane Bishop](https://wordpress.org/support/users/nosilver4u/)
 * (@nosilver4u)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/#post-8716025)
 * Already fixed in dev: [https://downloads.wordpress.org/plugin/ewww-image-optimizer.zip](https://downloads.wordpress.org/plugin/ewww-image-optimizer.zip)
 *  Anonymous User 357386
 * (@anonymized-357386)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/#post-8717475)
 * same here. atm disabled, attend update!
 *  Plugin Author [Shane Bishop](https://wordpress.org/support/users/nosilver4u/)
 * (@nosilver4u)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/#post-8717490)
 * You had to disable it? Why?
 *  [Alias79](https://wordpress.org/support/users/alias79/)
 * (@alias79)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/#post-8717949)
 * In my case, my server came to collapse. I have it disabled pending the update
   in the repository.
 *  Plugin Author [Shane Bishop](https://wordpress.org/support/users/nosilver4u/)
 * (@nosilver4u)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/#post-8718202)
 * If any of you that are having performance issues with the plugin have access 
   to your server logs, you should check those for clues. I highly doubt the warnings
   are causing any performance issues (although I’d love to be wrong on that one).
 *  [Alias79](https://wordpress.org/support/users/alias79/)
 * (@alias79)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/#post-8719686)
 * My server showed overprocessing messages when I had the errors I commented yesterday.
 *  Plugin Author [Shane Bishop](https://wordpress.org/support/users/nosilver4u/)
 * (@nosilver4u)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/#post-8722221)
 * Update just released about 10 minutes ago. If it still causes performance issues,
   I thought of one other thing you could try. In your wp-config.php file, there
   is a WP_DEBUG setting. If you set that to true, it will generally tell PHP to
   display errors (useful if you don’t have access to the error logs). Of course,
   you don’t want to leave that enabled very long on a production site, but it might
   give us some clues if anyone is still having trouble.
 * EDIT: also wanted to mention, that since the original issue should now be fixed,
   please use this for any remaining troubles: [https://ewww.io/contact-us/](https://ewww.io/contact-us/)
    -  This reply was modified 9 years, 4 months ago by [Shane Bishop](https://wordpress.org/support/users/nosilver4u/).

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

The topic ‘Illegal string offset’ is closed to new replies.

 * ![](https://ps.w.org/ewww-image-optimizer/assets/icon-256x256.png?rev=1582276)
 * [EWWW Image Optimizer](https://wordpress.org/plugins/ewww-image-optimizer/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ewww-image-optimizer/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ewww-image-optimizer/)
 * [Active Topics](https://wordpress.org/support/plugin/ewww-image-optimizer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ewww-image-optimizer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ewww-image-optimizer/reviews/)

 * 8 replies
 * 4 participants
 * Last reply from: [Shane Bishop](https://wordpress.org/support/users/nosilver4u/)
 * Last activity: [9 years, 4 months ago](https://wordpress.org/support/topic/illegal-string-offset-32/#post-8722221)
 * Status: resolved