EC WEB-T
Forum Replies Created
-
Forum: Plugins
In reply to: [WEB-T – eTranslation Multilingual] Migrating from REST v1 to v2Hello @zlatimuud,
Thank you for reaching out!
Yes, the migration of the API from v1 to v2 will be handled automatically through the official WordPress plugin. A new plugin version will be published soon, and you will simply need to update to the latest release.
The update process will be straightforward and is not expected to have any impact on your website or existing configuration.
Best regards!
WEB-T TeamForum: Plugins
In reply to: [WEB-T – eTranslation Multilingual] Plugin MaintenanceHi @giorgosm,
Apologize for the delayed reply.
Please see the responses below:- Yes, the plugin is actively maintained, and a new release is expected soon.
- Yes, it is a legitimate fork of the TranslatePress plugin.
- You are free to fork it as well; however, any modifications must comply with the licence terms. For instance, if you distribute a modified version, it must be released under the same or a compatible licence. You should also include the following attribution:
“The WEB-T plugin was developed under the European Commission’s procurement contract as part of the Digital Europe Programme (https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/tender-details/10631).” - Yes, you are also eligible to use the API. You can obtain your API credentials at the following link:
https://language-tools.ec.europa.eu/registerApiKey?lang=en
We hope this information is helpful and remain at your disposal should you have any other question.
Hi @jordanmegg,
Thank you for reaching out!
We can confirm that the “checkout” page is translated correctly when the language differs from the default. To help us investigate this further, please send your website URL via email to [email protected].
Thank you for your cooperation.
Hello @peterteszary,
Thank you for bringing this to our attention. We’ll pass the issue along to our team so it can be addressed in the next release of the plugin.Best regards,
Web-T Team
Forum: Plugins
In reply to: [WEB-T – eTranslation Multilingual] Translation page doesn’t show up anymoreHello @rubencoolen,
This issue seems unusual since the “Translate Site” feature is functioning normally and hasn’t been affected by any recent updates. To better understand the problem, could you provide more information? A screenshot of what “Translate Site” looks like on your end would be particularly helpful. Alternatively, you can also send additional details to our support email at [email protected].
Forum: Plugins
In reply to: [WEB-T – eTranslation Multilingual] Translation page doesn’t show up anymoreHi @rubencoolen
Thank you for getting in touch!You can edit the automatic translations or add manual translations as described in the documentation below:
https://website-translation.language-tools.ec.europa.eu/instruction-information-about-wordpress-woocommerce_en#content-translation-and-editing
We hope this information is helpful to you and remain at your disposal should you have any other questions.Hello @peterteszary
The issue appears to be related to either The Events Calendar plugin or WordPress itself. Unfortunately, there’s not much we can do to assist from the WEB-T side.
We remain at your disposal should you need anything else regarding the WEB-T plugin.
Best regards,
WEB-T Team
Hello @hgeorge89 and @peterteszary,
Thank you for reaching out!
We conducted some tests and found that the WEB-T plugin successfully translates most of the content on the “The event calendar” page:
http://www.your-domain.com/events/
When a different language is selected, the plugin translates all visible text on the page. However, the abbreviated day names (e.g., MON, TUE) remain unchanged because the translation server doesn’t recognize them as translatable words. The same limitation applies to abbreviated month names (e.g., JAN, FEB).To address this, you can manually translate these abbreviations using the “Translate Page” option available at the top of the page.
As for the iframe, Web-T is unable to translate its content because an iframe essentially loads a separate website within your page. Since the plugin only processes text directly embedded in your site, anything inside the iframe falls outside its scope.
Hello @peterteszary ,
Thank you for reaching out!
We conducted some tests and found that the WEB-T plugin successfully translates most of the content on the “The event calendar” page:
http://www.your-domain.com/events/
When a different language is selected, the plugin translates all visible text on the page. However, the abbreviated day names (e.g., MON, TUE) remain unchanged because the translation server doesn’t recognize them as translatable words. The same limitation applies to abbreviated month names (e.g., JAN, FEB).To address this, you can manually translate these abbreviations using the “Translate Page” option available at the top of the page.
As for the iframe, Web-T is unable to translate its content because an iframe essentially loads a separate website within your page. Since the plugin only processes text directly embedded in your site, anything inside the iframe falls outside its scope.
Hello,
Unfortunately, the plugin does not offer a global JavaScript function. However, it automatically translates dynamic content by default.
Forum: Plugins
In reply to: [WEB-T – eTranslation Multilingual] Fatal error when activatedHello Morten,
The error indicates that the second argument passed to the array_merge() function is a string instead of an array. Specifically, the call to get_option(‘etm_advanced_settings’, $default_etm_advanced_settings) is returning a string, suggesting that the option_value for etm_advanced_settings in the wp_options table is incorrectly stored as a string.
Workaround:
To resolve this, delete the problematic row from the database:DELETE FROMwp_optionsWHERE option_name = 'etm_advanced_settings';After this, the plugin should activate successfully.
The root cause may be an outdated version of the plugin saving malformed data, or manual edits to the wp_options table. We’ve reported the issue and will include a fix in the next plugin release to handle such scenarios more gracefully.