Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #1374196

    Hello

    We have recently come across an issue with Enfold and the Advance Layout Builder. We have the theme updated and no issues. Until a few weeks back we couldn’t edit a single page and received a constant HTTP Error 500. This happened if we used the Advance Layout Builder or the WordPress Classic Builder. To help eliminate issues our IT team updated the PHP on the website and now we are unable to access any theme editor or options via WordPress and hit with the HTTP Error 500. The site is still functional but now has the following text at the top of the each page.

    Warning: Declaration of FEE_Field_Terms::wrap($content, $taxonomy, $before, $sep, $after) should be compatible with FEE_Field_Post::wrap($content, $post_id = 0) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/post.php on line 182

    Warning: Declaration of FEE_Field_Tags::wrap($content, $before, $sep, $after) should be compatible with FEE_Field_Terms::wrap($content, $taxonomy, $before, $sep, $after) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/post.php on line 281

    Warning: Declaration of FEE_Field_Category::wrap($content, $sep, $parents) should be compatible with FEE_Field_Terms::wrap($content, $taxonomy, $before, $sep, $after) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/post.php on line 290

    Warning: Declaration of FEE_Field_Post_Thumbnail::wrap($html, $post_id, $post_thumbnail_id, $size) should be compatible with FEE_Field_Post::wrap($content, $post_id = 0) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/post.php on line 299

    Warning: Declaration of FEE_Field_Post_Meta::wrap($data, $post_id, $key, $ui, $single) should be compatible with FEE_Field_Post::wrap($content, $post_id = 0) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/post.php on line 352

    Warning: Declaration of FEE_Field_Widget::wrap($params) should be compatible with FEE_Field_Base::wrap($content, $data) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/widget.php on line 10

    Warning: Declaration of FEE_Field_Comment::wrap($content) should be compatible with FEE_Field_Base::wrap($content, $data) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/other.php on line 10

    Warning: Declaration of FEE_Field_Term_Field::wrap($content, $term_id, $taxonomy) should be compatible with FEE_Field_Base::wrap($content, $data) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/other.php on line 70

    Warning: Declaration of FEE_Field_Single_Title::wrap($title) should be compatible with FEE_Field_Term_Field::wrap($content, $term_id, $taxonomy) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/other.php on line 115

    Warning: Declaration of FEE_Field_Option::wrap($content, $key, $ui) should be compatible with FEE_Field_Base::wrap($content, $data) in /home/cluster-sites/9916/t/thomasfranks.co.uk/public_html/my/wp-content/plugins/front-end-editor/php/fields/other.php on line 231

    This error has come about with no apparent reason or change and our hosting providers have not flagged any issues. I can’t even get into the theme options to update or check for issues so a bit stuck on this. Hoping you can help me here. The site has a login in wall as it is an internal use.

    Thanks.

    #1374202

    Hey JoshuaTF,

    All the warnings seem to be coming from a plugin called Front end editor or something similar, could you try deactivating that please?

    Best regards,
    Rikard

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.