Hi, when trying to visualize a post before publishing, I get the following error:
Fatal error: Uncaught Error: Call to a member function format() on boolean in /home/serposit/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_module_single_base.php:672 Stack trace: #0 /home/serposit/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_module_single_base.php(796): td_module_single_base->get_item_scope_meta() #1 /home/serposit/public_html/wp-content/plugins/td-standard-pack/Newspaper/loop-single.php(63): td_module_single_base->show_item_scope_meta() #2 /home/serposit/public_html/wp-content/plugins/td-standard-pack/Newspaper/single.php(26): require_once(‘/home/serposit/…’) #3 /home/serposit/public_html/wp-includes/template-loader.php(98): include(‘/home/serposit/…’) #4 /home/serposit/public_html/wp-blog-header.php(19): require_once(‘/home/serposit/…’) #5 /home/serposit/public_html/index.php(17): require(‘/home/serposit/…’) #6 {main} thrown in /home/serposit/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_module_single_base.php on line 672
Hi,
Unfortunately there is a problem with the new option add in theme panel for disable the schema article, this interfere with preview draft, in order to fix this problem you’ll need to make some changes in theme file or deactivate the schema articles from here: https://www.screencast.com/t/0E3IucACC You will have to check that in order to deactivate the schema, this issue will be fixed in the next update.
The file are wp-content/plugins/td-composer/legacy/common/wp_booster/td_module_single_base.php -> https://i.imgur.com/EMWC74l.png add “|| is_preview()” -> https://i.imgur.com/78beFgC.png
wp-content/plugins/td-cloud-library/state/single/tdb_state_single.php
-> https://i.imgur.com/WIIKHSU.png -> https://www.screencast.com/t/VbigQIINRB
or you can send us an email at contact@tagdiv.com and provide admin login, as well as cPanel or FTP if possible. We will take a look and make the proper changes for you. Include a link to this topic in the email.
Thank you for your understanding!
