cmhello
Forum Replies Created
-
Hello, the addon plugins I downloaded from my order at shop.greenshiftwp.com are still older versions; the .pot files are outdated (some even from 2024). Please ensure that the files you provide for download are the latest (and not cached by a CDN).
Furthermore, some addon plugins lack
wp_set_script_translations, causing my translated JSON files to fail to load correctly.I noticed that the new version of the Greenshift core plugin includes a new .pot file, which contains almost all translatable fields!
However, this .pot file is generated in the Greenshift plugin development directory (which includes the src directory), while the plugin package downloaded from ww.wp.xz.cn does not include a src directory (e.g., “source”:”src/blocks/counter/edit.js”). Therefore, users cannot generate a .pot file containing all translated fields using the downloaded plugin package.
This is because the WP CLI command cannot correctly recognize the contents of the webpack-packaged build/index.js to generate a .pot or .po file.
Therefore, the correct approach (choose one):
1. Generate the latest .pot file and include it in the plugin package with each new release.
2. Include the original files and directories in thesrcdirectory in the plugin package (this method should allow the official WordPress translation library to recognize all translated fields).
Simultaneously, the same approach should be adopted for addon plugins, and the download files in your marketplace user center should be updated.
This way, our users can translate the plugins themselves. Thank you!Thank you for the tutorial. I already know how to use WP CLI commands; that’s not my real reason for asking the question here!
You’ve consistently avoided directly answering my question:
During the generation of the compressed version of
greenshift-animation-and-page-builder-blocks\build\index.js, the core plugin breaks the original__(),_e(), and other functionalities, causing the WordPress translation library and WP CLI commands likewp i18n make-potto fail to retrieve the fields to be translated from that file.This is why the official WordPress translation library doesn’t correctly parse the translations of the Greenshift plugin’s blocks (it’s not that the translation library has a bug, but that your plugin has a bug!).
If the plugin doesn’t have the above error, the
wp i18n make-potcommand should be able to retrieve all the translated fields.You can easily test this yourself using
wp i18n make-potto see if the problem I’m pointing out actually exists.Why do I urgently need you to provide the core plugin’s pot file? I expect you to actually test it. I’m certain you can’t possibly get a pot file containing all the translated fields because your plugin has bugs!
You’ve consistently refused to address this issue. Perhaps you believe that non-English speaking users aren’t worth your time maintaining, even paid users!
As a paid user, I’m extremely disappointed with your handling of this problem!
I know the typical path to generating JSON:
- Generate a .pot or .po file
- Translate the .po file
- Generate a .json file using the method you repeatedly mentioned.
I know how to do all of these.
The real issue is: because all the fields displayed in the Gutenberger editor by the Greenshift plugin reside in the compressed
greenshift-animation-and-page-builder-blocks\build\index.jsfile, it has broken the original correct translation of fields like__(),_e(), etc., during the build process. This makes it impossible to fully recognize and generate a .pot file containing all fields!It’s impossible to generate a .pot file containing all fields from the very first step! So what you need to address and solve is the problem in the first step, not keep telling me how to generate a translated JSON file!!
I just have a few questions for you:
- Have you checked whether the .pot file built into the Greenshift plugin that you uploaded to your WordPress repository actually contains all the translated fields? (I checked, and it only has 428 fields!)
- Are you actually using the command line I keep telling you to generate the .pot file in the client, then translate it, and then generate the .json file?
Please note: Do not use your locally developed Greenshift plugin directory to generate it. Instead, download and extract it from ww.wp.xz.cn, and then generate it in the extracted directory!
Only you can: use your repeatedly used method to generate a .pot file containing all fields and check if it contains all fields! If you confirm that it contains all fields, please share it with me!
It’s impossible to generate a POT file containing all the translated fields using any official command, because the fields are structurally corrupted in the compressed
greenshift-animation-and-page-builder-blocks\build\index.jsfile, making it impossible to recognize and generate the fields that need translation.If you say the WordPress translation library has bugs, then please provide a POT file with all the fields in the Greenshift plugin zip!
If you say Greenshift supports complete translations, then please translate it into one language and show it to us!
That’s all I wanted to say!
The fact is, we users cannot perform a complete translation using the WordPress translation library or Greenshift’s built-in Pot file!
https://pioneerroll.s2-tastewp.com/wp-content/uploads/2026/04/Video_2026-04-18_133154.mp4https://pioneerroll.s2-tastewp.com/wp-content/uploads/2026/04/2026-04-18_133301.jpg
The code snippet (your source file) you provided is not included in the plugin!
I want to reiterate: the source files you used for development were not included in the Greenshift installation package! The functionality loaded in the Gutenberger editor is implemented through your compressedgreenshift-animation-and-page-builder-blocks\build\index.jsfile! The problem lies in the fact that the code in this compressedindex.jsfile corrupts the original structure of translation fields such as__(),_e(), etc.! This causes the translation fields to be unrecognized and untranslated! That’s the crux of the problem!Everything I’ve said above is based on actual testing and has video evidence!
You say it supports translation, then you should translate a language yourselves and show us!!
Everyone can view this video. I chose the 100% translated Polish version as a test, but Greenshift fails to display Polish in almost 90% of the fields in the Gutenberger editor interface: https://pioneerroll.s2-tastewp.com/wp-content/uploads/2026/04/Video_2026-04-18_124455.mp4
Hello, the Greenshift plugin’s Gutenberger interface fields are all compressed into the
greenshift-animation-and-page-builder-blocks\build\index.jsfile. This compressed version destroys almost all fields that need translation.As a paid user, I have also submitted a support ticket on your website, which you can view in the video I recorded. You can also check the official WordPress translation library to see if it includes all the fields that need translation: https://translate.ww.wp.xz.cn/projects/wp-plugins/greenshift-animation-and-page-builder-blocks/
As developers, you should know that Greenshift cannot possibly have only 1175 fields that need translation! However, at https://translate.ww.wp.xz.cn/projects/wp-plugins/greenshift-animation-and-page-builder-blocks/, there are actually fewer than 1200 fields to translate. This indicates that the fields in your plugin’s Gutenberger interface are rendered untranslatable by the compressed
\build\index.jsfile, making it impossible for WordPress to recognize and provide translations!Please don’t be presumptuous. The true truth lies in practical application. You can try translating Greenshift into other languages yourselves, and then check in the WordPress backend to see if your plugins actually support translation!
To reiterate: the issue I’m reporting here concerns the Greenshift core plugin: https://ww.wp.xz.cn/plugins/greenshift-animation-and-page-builder-blocks/, not the addon plugins I reported a few years ago (I can accept that the addon plugins couldn’t be translated due to Gutenberg’s policies), but the problem of the core plugin not being translated must be resolved!Forum: Plugins
In reply to: [Meta Box] Can‘t get posts after update from V5.9.9I’m sorry, I may have made a mistake, but this is indeed the reason why the plug-in I use does not function properly. I may need to contact the plug-in author to deal with it. Thank you for your reply.
I have clearly told you the file and line number of the error, you can just check the plugin and fix it.
I saw the error in debug.log by turning on the debug mode.
eazydocs/includes/Frontend/Frontend.php on line 350
eazydocs 2.5.2
I have sent you a message through the contact page, thanks!
Hello, I have decided to use Greenshift in future projects, and provide Simplified Chinese translations for Greenshift (including addons), as long as you have a good translation preparation for all fields.
I will always provide a Simplified Chinese translation of the plugin and recommend it to Chinese users. If I plan to purchase All in One Pack Unlimited / Lifetime, is there a larger discount available?
The current price is indeed too high for me, sad (ಥ﹏ಥ)
Thanks!
Thank you for passing the translation.
I’m more concerned about when will all the content support translation, thank you!
Please rest assured that we have 10+ years of experience in WordPress and all translations are done manually.
