Venkat Raj

Hi @tomaslt991

Looks like the template doesn’t seem to properly use The Loop
https://developer.wordpress.org/themes/basics/the-loop/

If it did, $post variable won’t be null and warning won’t happen

@agblee1970

I was able to reproduce the issue and async loading fixes it. Please refer this screencast. (You may be viewing the same page with browser cache, so no changes visible)

https://drive.google.com/file/d/18cgheMmBbq-YGWq4nhY3fELxJF2V-ap7/view?usp=share_link

• This reply was modified 3 years, 6 months ago by Venkat Raj.

Hi @gemmanltd

If that happens when you edit the file and trying to save it, then your hosting provider denies that change. The change you made only enables debug logging and nothing else.

Even if you have misspelled something and left semi colon at the end of the line, then it should only throw a syntax error. So please contact your hosting provider.

Also, even though the website is locked you can still do ssh/ftp and undo your changes to see if that fixes the issue.

@gemmanltd We are not talking about logging into your hosting account / cpanel.

If you login to your server using ssh or use FTP to connect to you server, you’ll see a list of files (WordPress core files, your theme, plugins, etc) where you can find wp-config.php in the root directory and you can do necessary changes.

@gemmanltd Do you see any messages in php error log or debug.log files?

You can turn on debugging by adding these lines to your wp-config.php file

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);

Hi @izzappel

Case 1: Upon any update, the cache will be purged and cached freshly. The filename depends on the version number which usually changes with update

Case 2: If your server is configured to use ETag properly, then every time the static file content changes, the ETag also changes. This ensures serving fresh file regardless of expires header. We also use Last-Modified header which also ensures fresh file content.

Hi @joshliba

For some reason WebP conversion isn’t working properly on your server and hence it is throwing warning. Beaver builder assume dynamically generated page should only contain JS, no php warning. So this happens.

This will be fixed in our next release. In the meantime you can comment out webp feature and continue to use Automatic compression by commeting out this line
https://plugins.trac.wordpress.org/browser/wp-optimize/trunk/wp-optimize.php#L539

Hi @francoc30

The error happens from files with wp-includes folder. So, replacing that (#2) is suffice. Just to be sure, follow all steps you have listed and for #4 it is 4b

> These file replacement process would not adversely affect my website setup, correct?
Yes, the site related files are in wp-content folder and in wp-config.php file.

But always take a full backup before proceeding with UpdraftPlus
https://wordpress.org/plugins/updraftplus/