Eleven40

This topic is: not resolved

This topic contains 2 replies, has 3 voices, and was last updated by  essaysnark 1 year, 3 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #55486

    somarco
    Participant
    Post count: 3

    Upgraded site to the new version of Eleven40 and now I am unable to access the admin section. Getting a 500 code. Contacted WPEngine for assistance.

    Here is their response.

    Please get in contact with the theme developer, and relay this error message to them. Their code isn’t correct:

    /var/log/apache2/medarticles.error.log:[Thu Aug 08 15:02:43 2013] [error] [client 71.22.198.58] PHP Catchable fatal error: Argument 3 passed to Genesis_Settings_Sanitizer::add_filter() must be an array, string given, called in /nas/wp/www/cluster-1660/medarticles/wp-content/themes/genesis/lib/classes/sanitization.php on line 287 and defined in /nas/wp/www/cluster-1660/medarticles/wp-content/themes/genesis/lib/classes/sanitization.php on line 69, referer: http://www.medicarearticles.com/wp-admin/update-core.php?action=do-theme-upgrade

    A string was given, where an array was expected. They should have the knowledge needed to know what’s wrong.

    Trying to find out how to contact developer of Eleven40

    http://www.medicarearticles.com/
    #55492

    braddalton
    Participant
    Post count: 10594

    I think its best to submit this to support http://my.studiopress.com/help/

    You could delete the new theme version until the issue is resolved.


    #55543

    essaysnark
    Participant
    Post count: 342

    You can actually fix this by making a change to Genesis core per the instructions from GaryJ here:

    http://www.studiopress.com/forums/topic/genesis-2-0-update-catchable-fatal-error/

    As he said, this change will be in Genesis core in the next update so it’s no problem to implement that yourself.

    Also: StudioPress is the developer of the Eleven40 theme (along with Genesis) so Brad’s right, you can submit a support ticket instead. But the fix described in that other thread should do it for you.

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

You must be logged in to reply to this topic.