rjekic

@loganddiamond

edit: yes, the better and safer way should be reading the settings from the old wp-config file preserved in backup, as @threadi suggested.

• This reply was modified 4 months, 1 week ago by rjekic.

It seems that your database backup uses different prefix than default installation of WordPress. Can you check the database using some tool (I assume phpmyadmin if you are using cpanel) and see what prefix tables are using?

@morchiiid

We need more details in order to assist you effectively. Could you please provide a more thorough description of the issue? For instance, is this the message you see on the Site Health page (with all HTML tags)? Is this happening on a new installation of WordPress? Also, could you let us know which version of WordPress you’re using and which theme is currently active?

It seems that you are not using Divi by the author’s guidelines, and we cannot help you further. A general rule of thumb here would be to try to change a theme from child to parent theme, but I am not sure it will help you.

@resitdev

It seems that is error is caused by the string that contains special characters (blank space in your case). You should use urlencode() function which ensures that special characters are properly encoded for use in a URL. This should solve the issue.

So, instead of this

'content'     => file_get_contents( get_template_directory_uri() . '/patterns/asif.php?id='. $vari),

use this

'content'     => file_get_contents( $pattern_file_path . '?id=' . urlencode( $vari ) ),

@nomen1

Please provide more info about the WordPress version and the theme you are using. The default query loop behavior is to show stycky post on the top of every page, except the page where that post is originaly located. But, some themes, plugins, or page builder could change default behavior of the sticky posts feature.

@dilip2615

I think that using this function will exclude sticky posts from the query loop, so you must use two queries – one for sticky posts and one for all other posts.