I’m trying to translate the plugin using Loco Translate, but I’m encountering the following errors:
? “Invalid pot file: wc-variations-as-single-product.pot”
? “0 strings found in wc-variations-as-single-product.pot”
I checked the plugin directory, and the .POT file is empty (0 bytes). Could you please look into this and provide a fix?
Thank you in advance!
]]>- The theme pages have not been translated – the content is still in English. Although I encountered no issue while translating the theme or the plugins and they all came out with a 100% translated result.
- Apparently, the plugin has also translated my permalinks or slugs for every page and thus my internal menu is not currently working. Please advise on how to restore the slugs/permalinks to their initial English state (I want to keep those in English) so that my menu starts working again.
It seems that this translation is not possible.
Memberdirectry→Sortcode→View
We are sorry. We cannot find any users who match your search criteria. ]]>
I’ve tried translating the text with Loco Translate (didn’t work – so checked your support page).
The guide was indeed followed, but it still dosen’t work.
I dosen’t translate the text on the donation box and so on.
Also I found the following video for the dashboard translations (the missing ones)…
This also didn’t work. I’ve cleared cache on both browser and server – didn’t help.
I use a combination of both Loco Translate and TranslatePress since Loco Translate is not working with dynamic content (I use BuddyPress) – so the combination of the 2 normally works really well.
I’ve tried translation in both plugins – nothing works.
Need help figuring this out thanks!
]]>
I’ve been playing around with the translation for a while and debugged a lot of it today. Turns out the POT file needs and update. I found both errors and missing content.
I tried adding them in the POT manually and they also got reconized by LocoTranslate – however – the translation for the 13 new strings did not work.
Can someone please look into this?
It’s regarding the following (that I’ve found so far):
BUG: 4951: msgid "The event title slug. Leave empty to auto-generate" (ERROR)
BUG: 6037: msgid "Allow access to the dashboard from the front-end calendar" (FUZZY)
BUG: 4331: msgid "Every 48th week" (MONTH)
NEW: msgid "All day"
NEW: msgid "Hide end date"
NEW: msgid "Category display name"
NEW: msgid "Name"
NEW: msgid "Guest display name"
NEW: msgid "Coordinates"
NEW: msgid "Location coordinates in decimal format"
NEW: msgid "Calendar display name"
NEW: msgid "In calendar dashboard"
NEW: msgid "RRULE"
FUZZY: Location name
FUZZY: SlugI’m using LocoTranslate to translate my site and I recently noticed that there is a lot of errors within the LocoTranslate panel regarding the CleanTalk plugin. It claims to have a lot of missing MO-files?
How do I fix this issue? – Thanks!
https://ibb.co/s6XbjnW
https://ibb.co/1G2bQny
WordPress: v. 6.7.1
CleanTalk: v. 6.46
One of the aspects that continues to frustrate me is the client registration experience. The process doesn’t allow clients to input their information until after completing the purchase, when they receive an activation email with a link. This flow feels clunky, and the checkout screen isn’t clear enough in guiding users on what to do next—whether they should go to their dashboard to schedule appointments for packages, or follow through with creating a password. It’s messy, and although we’ve managed to work around it, there’s definitely room for major improvements here.
Another major issue I’ve encountered is the integration with WooCommerce. Amelia simply redirects the client to the WooCommerce checkout page, and while WooCommerce has a robust API, there is a clear lack of a more organic integration for the payment process. For countries that don’t use international payment methods, you’re left with no choice but to rely on WooCommerce, and the transition between Amelia and WooCommerce feels abrupt and disjointed. There’s a significant opportunity here to make the integration smoother.
Additionally, everything seems to require some form of page loading, saving, and refreshing. This makes me wonder if it’s worth building such a system on a platform like WordPress, which relies on PHP servers. This inevitably depends on the client’s budget, but it’s something to keep in mind.
The main challenge I’ve encountered is that configuring Amelia requires heavy reliance on the documentation and tutorial videos. However, the documentation isn’t always titled in a way that makes things easy to find, which led to some confusion on my part.
That said, the support team has been absolutely incredible. They’ve been there every step of the way to help configure everything I needed. However, Amelia still feels like it’s in its early stages, and there’s a lot of room for improvement—especially from a UX perspective in 2024.
]]>I use LocoTranslate + This plugin but It doesn’t work. The form is still in English. Could you please double check this? Especially the Espanol language.
Thank you,
Cuong Tran aka withemes
]]>The translations files for payment gateway: Stripe (e.g. “Card Holder Name”) are available (Loco / WPML), but the translations are not displaying front end. IN GENERAL, it’s not possible to translate admin fields, which is not at all satisfactory. If not fixed promptly, I will need to go for another plugin.
]]>I have a site with WooCommerce called?asnorformazione.com. In checkout, there are two fields (As you can see in this link) that are in English and the rest of the checkout is correctly in Italian. Before, I contacted the WooCommerce support that suggest me to download LocoTranslate plugin, but it didn’t work.
The WordPress language setting is Italian.
How i can translate these 2 fields?
]]>