Okay
  Public Ticket #2333459
Errors while trying to preview/update page
Closed

Comments

  •  1
    thenimo started the conversation

    Hi there,

    I am trying to preview and update my home page and I get the following errors:

    Preview:
    Warning: preg_match() expects parameter 2 to be string, array given in /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php on line 417

    Warning: strlen() expects parameter 1 to be string, array given in /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php on line 489

    Warning: Cannot modify header information - headers already sent by (output started at /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php:417) in /home2/nirmal/public_html/wp-includes/pluggable.php on line 1265

    Warning: Cannot modify header information - headers already sent by (output started at /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php:417) in /home2/nirmal/public_html/wp-includes/pluggable.php on line 1268

    Update:
    Warning: preg_match() expects parameter 2 to be string, array given in /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php on line 417

    Warning: strlen() expects parameter 1 to be string, array given in /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php on line 489

    Warning: preg_match() expects parameter 2 to be string, array given in /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php on line 417

    Warning: strlen() expects parameter 1 to be string, array given in /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php on line 489

    Warning: Cannot modify header information - headers already sent by (output started at /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php:417) in /home2/nirmal/public_html/wp-admin/post.php on line 223

    Warning: Cannot modify header information - headers already sent by (output started at /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php:417) in /home2/nirmal/public_html/wp-includes/pluggable.php on line 1265

    Warning: Cannot modify header information - headers already sent by (output started at /home2/nirmal/public_html/wp-includes/class-wp-block-parser.php:417) in /home2/nirmal/public_html/wp-includes/pluggable.php on line 1268


    I tried finding documentation to solve this but couldn't find the solution. Here's what i found.

  •  8,886
    Tahir replied

    Hey ,

    Please contact your hosting provider and have them look into this as its likely caused by a security setting. Also switch to PHP 7.3 and not 7.4 . 

    Best 


    ThemeNectar Support Team 

  • Tim replied

    I have the same problem, and it seems to be the Salient WPBakery Page Builder v5.7 that causes this issue.
    The issue does not appear to be host related as we have tested it on SiteGround, Hostgator and Hostinger now with the same result.

  •  1,079
    ThemeNectar replied

    Hey Tim, 

    The current release of Salient is v12 and the current release of the Salient WPBakery page builder is v6.1. The issue mentioned in this ticket was correct in v11.0.2: http://themenectar.com/changelogs/salient.html#11-0-2

    After updating the theme, remember to update the included plugins to get the fix: http://themenectar.com/docs/salient/updating-salient/

    Cheers

  • Tim replied

    hmmm... The theme reports itself as up to date with Version 10.0.4. 

  •  1,079
    ThemeNectar replied

    Salient is not connected to the global WordPress repository - you need to install the Envato Market plugin to automatically track updates when they're pushed to ThemeForest. We have a link to the plugin in the documentation page I posted below, as well as the alternative methods of updating.

  •  8,886
    Tahir replied

    Hey Again,

    Do you have the Envato Market Plugin Installed ?. Please see: http://themenectar.com/docs/salient/updating-salient/ . 

    Thanks


    ThemeNectar Support Team 

  • Tim replied

    Yup. Have done since install - it's how I track all Envato theme updates for all my sites that use that system.

  •  8,886
    Tahir replied

    Could you try creating a new token and check . You can also update it manually using the guide mentioned earlier.

    Thanks


    ThemeNectar Support Team 

  • Tim replied

    Yes, now that I've gone and manually updated the theme everything works fine, and I have recreated the API token for ThemeNectar. I guess there was a major disconnect looking at the v10 changelogs that just dropped any updates for earlier versions?

  •  8,886
    Tahir replied

    This is likely something on Envato end as we have no control over it.

    Thanks


    ThemeNectar Support Team 

  • Tim replied

    Thanks for helping! Happy to get this resolved so quickly.