itapress
Forum Replies Created
-
Hello.
Thank you for your reply.
Unfortunately, I have to report that, even after the release of version 2.5.2, the issue on translate.ww.wp.xz.cn has not yet been resolved.
Thanks.
Also:
https://plugins.trac.ww.wp.xz.cn/browser/metform/tags/4.1.5/widgets/widget-notice.php#L32
https://plugins.trac.ww.wp.xz.cn/browser/metform/tags/4.1.5/widgets/email/email.php#L72
https://plugins.trac.ww.wp.xz.cn/browser/metform/tags/4.1.5/core/admin/views/integrations.php
On these lines: 29, 30, 33, 41, 42, 48, 49, 60, 61, 64, 71, 72, 73, 78, 79, 80, 86, 87, 90, 97, 98, 103, 104, 107, 114, 115, 116, 122, 123, 124, 130, 131, 134, 141, 142, 143, 170, 202, 220, 230, 235, 239
Thanks.
Hello.
Thank you for the changes you made in version 4.10.1.
I would like to point out, however, that I understand that strings using the
_e()function (var _e=wp.i18n.__) and__()function (var __=wp.i18n.__) in JavaScript files (such as “dashboard/build/index.js“) and those relating to filesdashboard/src/dashboard/dashboard_main.jsxanddashboard/src/dashboard/mcp_section.jsxare not added to the translatable strings on translate.ww.wp.xz.cn.I understand that JavaScript files only include strings that use this function:
le=window.wp.i18nThanks.
Hello.
I’m sorry to have to report that even after the release of version 3.8.0, some .js files still contain hard-coded strings:
placeholder:"Select..."(in setup.3.8.0.js, frontendCommon.3.8.0.js, frontendDashboard.3.8.0.js and backend.3.8.0.js)placeholder:"Select Status"(in backend.3.8.0.js)placeholder:"Sale Price"(in frontendDashboard.3.8.0.js)screenReaderStatus:function(e{var t=e.count;return"".concat(t,"result").concat(1!==t?"s":""," available")}(in frontendDashboard.3.8.0.js. backend.3.8.0.js, frontendCommon.3.8.0.js and setup.3.8.0.js)noOptionsMessage:function(){return"No options"}(in frontendDashboard.3.8.0.js. backend.3.8.0.js, frontendCommon.3.8.0.js and setup.3.8.0.js)loadingMessage:function(){return"Loading…"}(in frontendDashboard.3.8.0.js. backend.3.8.0.js, frontendCommon.3.8.0.js and setup.3.8.0.js)I would also like to point out that I noticed that in the “
/assets/build” folder there are both the .js/.asset.php files from version 3.7.4 and version 3.8.0.Thanks.
Also, please note that this string (“Save in WDesignKit”) is hard-coded and not translatable:
Thanks.
Hello.
The first problem appears to be caused by a double slash ( // ) between
WDKIT_ASSETSand the string that follows it and is fixed by modifying this line:from:
wp_enqueue_script( 'wdkit-cross-copy-paste', WDKIT_ASSETS . '/js/main/wdkit-cross-copy-paste.js', $deps, WDKIT_VERSION, true );to:
wp_enqueue_script( 'wdkit-cross-copy-paste', WDKIT_ASSETS . 'js/main/wdkit-cross-copy-paste.js', $deps, WDKIT_VERSION, true );Thanks.
Hello.
Please note that even after the release of version 2.5.1, the strings related to the “WDesignKit Copy” and “WDesignKit Paste” functionality are not displayed translated, even though they are now present in the .pot file.
Also, some strings present in different files in the “
/includes/abilities/” folder have a different text domain ('sprout-mcp') and are not included in the .pot file.Thanks.
Hello.
I’m sorry to have to report that even after the release of version 3.7.4, some .js files still contain hard-coded strings:
placeholder:"Select..."(in setup.3.7.4.js, frontendCommon.3.7.4.js, frontendDashboard.3.7.4.js and backend.3.7.4.js)placeholder:"Select Status"(in backend.3.7.4.js)placeholder:"Sale Price"(in frontendDashboard.3.7.4.js and backend.3.7.4.js)placeholder:"Enter team name"(in frontendDashboard.3.7.4.js and backend.3.7.4.js)screenReaderStatus:function(e{var t=e.count;return"".concat(t," result").concat(1!==t?"s":""," available")}(in frontendDashboard.3.7.4.js and backend.3.7.4.js)noOptionsMessage:function(){return"No options"}(in setup.3.7.4.js, frontendCommon.3.7.4.js, frontendDashboard.3.7.4.js and backend.3.7.4.js)loadingMessage:function(){return"Loading…"}(in setup.3.7.4.js, frontendCommon.3.7.4.js, frontendDashboard.3.7.4.js and backend.3.7.4.js)Thanks.
Hello.
Thank you for your reply.
Unfortunately, I have to report that the issue on translate.ww.wp.xz.cn has not yet been resolved.
Thanks.
Hello.
Yes, the strings on translate.ww.wp.xz.cn now refer to version 4.7.9.
Thanks.
Hello.
The problem appears to have returned after the release of version 4.7.8 today.
The strings on translate.ww.wp.xz.cn refer to version 4.7.7.
Thanks.
Hello.
I confirm that the problem has been resolved.
Thanks.
Hello.
Thank you for the changes you made.
Unfortunately, I still have to report the presence of this hard-coded string in this file:
onClick:()=>d({isPickerOpen:!e.isPickerOpen}),className:”nxt-add-block-button”,disabled:e.isEditMode,title:”Insert New Blocks Into The Quick Action Bar“}
Thanks.
Hello.
Thank you for the changes you made.
Unfortunately, I still have to report the presence of these hard-coded strings in this file:
className:"nxt-edit-toggle-button "+(e.isEditMode?"nxt-active":""),title:e.isEditMode?"Exit edit mode":"Enable edit mode for block reordering"}))onClick:()=>c({isPickerOpen:!e.isPickerOpen}),className:"nxt-add-block-button",disabled:e.isEditMode,title:"Insert New Blocks Into The Quick Action Bar"}Thanks.
Hello.
Thank you for your reply.
Yes, I can confirm that everything works correctly after deleting the Dutch language files in the plugin’s
/languagesfolder.Thanks again.