Skip to content
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

i18n:textdomain and pot not working when using blade template #9

Open
Mick00 opened this issue Jul 20, 2020 · 0 comments
Open

i18n:textdomain and pot not working when using blade template #9

Mick00 opened this issue Jul 20, 2020 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@Mick00
Copy link

Mick00 commented Jul 20, 2020

Version

Please add the exact versions used for each of the following:

  • WP Emerge Starter Plugin: 0.16.1
  • WP Emerge (if not the default): 0.16.0
  • WordPress: 5.4.2
  • PHP: 7.4

Expected behavior

Text domain should be added automatically to WP translations function such as __($string), _e($e), etc. when using the textdomain command and be added to the .pot file when using the pot command.

Actual behavior

Text domain is not added in blade files, but is in php files and class.

Steps to reproduce (in case of a bug)

  1. Install https://github.com/htmlburger/wpemerge-blade following the instruction in readme.md
  2. Add a translated string using a translation function such as __('Your string') in a blade file
  3. Run command php wpemerge i18n:textdomain or php wpemerge i18n:pot

Work around

Instead of using {{__('hello world')}} you can use the classic php way <?php echo __('hello world')?> or <?= __('hello world')?> (short syntax)

@atanas-dev atanas-dev self-assigned this Nov 24, 2020
@atanas-dev atanas-dev added the bug Something isn't working label Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants