• Resolved Malae

    (@malae)


    Hello Ben,

    I have had a page with SVG images for some time and am doing some tidying up. I found your plug-in and have installed it. It has helped to show images of the SVG files in the Media library on my test site, which is useful. I noticed when clicking View, it is showing warnings (same for all images):

    Warning: Illegal string offset 'width' in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentyeleven\image.php on line 34
    
    Warning: Illegal string offset 'height' in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentyeleven\image.php on line 35

    Do you have any idea why this is happening?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Benbodhi

    (@benbodhi)

    Hi,

    I’m not sure this is related to my plugin. But please make sure you are using the latest version (even re-install) of the twentyeleven theme. That’s a really old theme ??

    Maybe go through some standard WordPress troubleshooting steps and see if you can find any more information.

    Deactivate all other plugins and revert to twentysixteen theme. Is the error still there?
    If not, then activate one by one, checking each time for the error to find the culprit.
    If error still there with plain WordPress, twentysixteen theme and SVG Support active only, then let me know.

    I’d be interested to see what this is caused by anyway.

    Thread Starter Malae

    (@malae)

    Thank you for your prompt reply.

    First of all, you will be happy to know that this issue is

      not

    caused by your SVG Support plug-in. The reason that I suspected the plug-in was that, after installing, it was the first time that the SVG graphics were visible in the Media Library and I clicked on View out of interest. It was late in the day and I did not have time to start eliminating the various possible causes.

    I think you will be interested to hear of my findings.

    All my themes and plug-ins are up-to-date, with Twenty Eleven at Version: 2.5, released 15 August, 2016.

    However, this issue occurs with all plug-ins deactivated and not only with Twenty Eleven:

    Twenty Twelve
    Warning: Illegal string offset ‘width’ in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentytwelve\image.php on line 30
    Warning: Illegal string offset ‘height’ in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentytwelve\image.php on line 31

    Twenty Thirteen
    Warning: Illegal string offset ‘width’ in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentythirteen\image.php on line 46
    Warning: Illegal string offset ‘height’ in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentythirteen\image.php on line 47

    Twenty Fourteen
    Warning: Illegal string offset ‘width’ in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentyfourteen\image.php on line 31
    Warning: Illegal string offset ‘height’ in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentyfourteen\image.php on line 31

    Twenty Fifteen
    \Warning: Illegal string offset ‘width’ in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentyfifteen\inc\template-tags.php on line 115
    Warning: Illegal string offset ‘height’ in H:\XAMPP-2\apps\wordpress\htdocs\wp-content\themes\twentyfifteen\inc\template-tags.php on line 116

    Twenty Sixteen is clear!

    Although this leaves you in the clear with your plug-in. I would be interested to hear your ideas on why this is happening. I will also do some further digging.

    On an another issue, I found that the latest versions of WP themes from Twenty Eleven up to and including Twenty Fourteen all throw up several CSS3 errors, if you attempt to validate their style.css files on W3. Presumably certain coding updates cannot be implemented because of the need to preserve backwards compatibility with earlier versions of WordPress.

    Plugin Author Benbodhi

    (@benbodhi)

    Hi,

    Sorry for the late reply.
    All of those themes are quite old now, I wouldn’t pay much attention to them really.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Illegal string errors’ is closed to new replies.