-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FileCompilerTags not working for field rendering #313
Comments
In your file that's in templates/fields/, are you using a "namespace ProcessWire;" at the top? If so, try removing that, so that there is no namespace specified. Those field rendering files don't get touched by the compiler if a namespace is present. |
No, there is no namespace declaration, also not in the corresponding template file. |
Is this issue impacting anyone other than dreer? |
I can confirm what @dreerr found out. Possible solution:
Also, this is what Ryan said in blog:
|
@matjazpotocnik Thank you, added labels accordingly. |
Short description of the issue
With the module FileCompilerTags activated it is possible to use
{var}
or{var.property}
variables in markup sections of a file. Sadly this does not work for template files for fields stored intemplates/fields/
Expected behavior
When using
{var}
in a file intemplates/fields/
it should render the value.Actual behavior
The
{var}
is not parsed.Steps to reproduce the issue
{value.title}
Setup/Environment
ProcessWire: 3.0.64
PHP: 7.1.4
Webserver: Apache/2.4.18 (Unix)
MySQL: 5.7.17
The text was updated successfully, but these errors were encountered: