Problems with a PHP-line after updating

  • eschoyen

    (@eschoyen)


    11 years, 11 months ago

    I updated an extention yesterday. When I’m trying to access the wp-admin page I’ll get this msg:

    Warning: Illegal offset type in isset or empty in /home/web4863/public_html/wp-includes/pomo/translations.php on line 72

    (also apearing on the top of the homepage: http://www.haugesund-teater.no )

    Warning: Cannot modify header information – headers already sent by (output started at /home/web4863/public_html/wp-includes/pomo/translations.php:72) in /home/web4863/public_html/wp-includes/pluggable.php on line 1121

    The line 72 is:
    isset($this->entries[$key])? $this->entries[$key] : false;

    I don’t know anything about php-coding. Can anyone help me?

    All my best,
    Erik

Viewing 3 replies - 1 through 3 (of 3 total)
  • jnhghy

    (@jnhghy)

    11 years, 11 months ago

    Hi, using the tutorial here you can disable the plugin that you’ve updated so you’ll have access to your wordpress backend.

    What plugin do you think caused this?

    Thread Starter eschoyen

    (@eschoyen)

    11 years, 11 months ago

    Thank you so much! Everythings fine now.

    This was the plugin: “s5-image-and-content-fader”

    shape5

    (@shape5)

    11 years, 11 months ago

    I will be checking the plugin code to figure out why you are getting the error and hopefully I’ll be able to post an update within a day or two.

    Please remember to post problems with Shape 5 products to the forums at Shape5.com; I get e-mail notifications for forum posts, so I would have been able to look into the problem almost a week ago instead of just finding out today because someone else posted.

    The only reason I found this thread is because the person who posted to the Shape5 forums included a link to it.

    I’ll do my best to have a patch out in the next day or two, I just have to figure out what’s causing the core WP translation engine to break like that.

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

The topic ‘Problems with a PHP-line after updating’ is closed to new replies.

Tags