https://docs.whmcs.com/9-1/tags/smarty/Recent content in smarty onHugo -- gohugo.iohttps://docs.whmcs.com/9-1/troubleshooting/troubleshoot-php/php-tag-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-php/php-tag-errors/Covers the “Smarty does not allow the PHP tag” template error caused by legacy Smarty PHP tags disallowed since WHMCS 9.0, with the fix of using the Smarty Compatibility Report to locate and remove them.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-email/smarty-policy-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-email/smarty-policy-errors/Explains that the “Smarty Error: Not allowed by security policy” log entry occurs when an email template contains advanced code blocked by the default email security policy, and directs reviewing the template code in System Settings > Email Templates and adding a policy exception to allow it.https://docs.whmcs.com/9-1/system/php/smarty-security-policy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/system/php/smarty-security-policy/Details the system policy’s restriction of fetch, php, include_php, and smarty_template.object tags, the mail policy’s allowed variable modifiers and native PHP functions, and the enabled_special_smarty_vars configuration array used to define a custom Smarty security policy.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-php/smarty-variable-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-php/smarty-variable-errors/Covers the Smarty “special variable not allowed by security setting” template error caused by Smarty 4’s stricter security policy blocking $smarty special variables, with the fix of refactoring templates to use assigned variables instead.