Okay I'm not really able to see anything in my FTP directory. I can see a .ftpquota file, but I cannot change directories or see anything else, so I can't see the log file. It's probably not important. I can replicate a problem on my end - if I place a Types WYSIWYG field in a Brizy template the template fails to render that WYSIWYG field. That's the issue we are trying to solve, correct? If so, I can escalate this to my 2nd tier support team for additional investigation.
Yes, please.
Please report also the original problem, which happen even when not using a WYSIWYG field.
"If I insert a shortcode in a Toolset custom field and use the Brizy Shortcode module directly in a post, it works. hidden link
But if I create a Brizy template, with the same Brizy's shortcode module, assign this template to all posts, the shortcode doesn't resolve. hidden link"
Please report also the original problem, which happen even when not using a WYSIWYG field.
Actually the WYSIWYG field is the only type of field that will resolve a 3rd-party shortcode when displayed on the front-end of the site, so the other fields types don't really apply here. Your example demonstrates the issue using a Toolset Types WYSIWYG field called "Shortcode test": hidden link
For a bit more technical information, when I installed the clone of your site on my local environment I was able to see a PHP fatal error when I tried to display a WYSIWYG field inside a Brizy template:
[07-May-2020 22:57:26 UTC] PHP Fatal error: Uncaught Error: Maximum function nesting level of '256' reached, aborting! in /path/to/site/wp-includes/plugin.php:912
Stack trace:
#0 /path/to/site/wp-includes/class-wp-hook.php(201): _wp_filter_build_unique_id('query', Array, false)
#1 /path/to/site/wp-includes/plugin.php(140): WP_Hook->has_filter('query', Array)
#2 /path/to/site/wp-includes/wp-db.php(2103): has_filter('query', Array)
#3 /path/to/site/wp-includes/wp-db.php(2123): wpdb->placeholder_escape()
#4 /path/to/site/wp-includes/wp-db.php(1173): wpdb->add_placeholder_escape('brizy-project')
#5 /path/to/site/wp-includes/wp-db.php(1244): wpdb->_real_escape('brizy-project')
#6 [internal function]: wpdb->escape_by_ref('brizy-project', 0)
#7 / in /path/to/site/wp-includes/plugin.php on line 912
Other shortcodes seem to be hit-or-miss. For example, a Types number field works well, but the wpv-post-title shortcode is simply written to the page.
It turns out I had Views and Blocks disabled when I tested the wpv-post-title field. Since this shortcode is part of Views/Blocks, obviously it won't work when those plugins are disabled. The WYSIWYG issue is still escalated to our compatibility team and I'll keep you posted as I receive more information.
