-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
Custom macro which starts with underscore #226
Milestone
Comments
But you can use |
Oh! Good to know that I can call functions this way. :) |
dg
added a commit
that referenced
this issue
Nov 11, 2020
dg
added a commit
that referenced
this issue
Nov 12, 2020
dg
added a commit
that referenced
this issue
Nov 12, 2020
dg
added a commit
that referenced
this issue
Nov 12, 2020
dg
added a commit
that referenced
this issue
Nov 14, 2020
dg
added a commit
that referenced
this issue
Nov 14, 2020
dg
added a commit
that referenced
this issue
Nov 15, 2020
dg
added a commit
that referenced
this issue
Nov 15, 2020
dg
added a commit
that referenced
this issue
Nov 15, 2020
dg
added a commit
that referenced
this issue
Nov 15, 2020
dg
added a commit
that referenced
this issue
Nov 15, 2020
dg
added a commit
that referenced
this issue
Nov 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: 2.8.1
Bug Description
I'm trying to create a macro which is starting with an underscore and it fails on thinking that it's a translation.
Also using a php function that starts with underscore fails as well.
In my case I'm trying to use this function
__()
: https://developer.wordpress.org/reference/functions/__/Using the function directly or creating a macro, the problem still persists.
Steps To Reproduce
Expected Behavior
Should execute the actual function
__()
, not trying to use the translation filter.I'm using only the
Latte
engine andTracy
, withoutNette
framework.The actual error:

Another question:
Is, it possible to remove this macro:
_
?The text was updated successfully, but these errors were encountered: