Luis
-
Posts
306 -
Joined
-
Last visited
Posts posted by Luis
-
-
3 hours ago, Seb said:
Should now be working fine 🙂
Nice! Tested it.
Thank you
-
1 hour ago, Luis L said:
I agree with you @Luis. Just to point out in Spanish from Spain we use the number before the month, that would be "5 de septiembre de 2022".
The agency that regulates Spanish language has some information about the use of dates (source: https://www.fundeu.es/recomendacion/como-se-escriben-las-fechas/). I would say that it would be the same in American English as this is the only organism that regulates Spanish in the whole world, but I can't say how dates are used in Latin America currently. It explicitly states that the use of the month before the day is discouraged as it comes from US English.
To summarize the info in that link, dates should be used as "[day] de [month] de [year]" and "de" can't be avoided. It can also be used with numbers without leading zeros (ex: 5/9/2022), although the use of the leading zero is simply discorauged and it is normally used to avoid legal issues.
So, I would use "5 de septiembre de 2022" or "05/09/2022" for dates in Spanish from Spain
We use that format too.
"5 de septiembre de 2022" long format
"05/09/2022" or as you said "5/9/2022" would also be fine (for short format).
The issue with this: "5/9/2022" is that for us it means September 5th., but for the US it would mean May, 9th. I don't know if Upmind differentiates between formats according to the region or to the language. Considering currently there's only Spanish (Spain), and English (UK) on the system.
-
1
-
-
Hi.
I noticed that too in my panel but it's better than before, and months and days are localized now. Thanks for that! Also, I see that those strings are gone from the Localazy's translation project (maybe for the best).
@Seb I see in this case one of the issues is that the English format is "MMM Do, YYYY", being the "o" after the D the ordinal placeholder for the number. But we don't use ordinal numbers in dates (at least not in Latin America). I believe it should be just "sep. 5, 2022" or "MMM D, YYYY" in this particular case.
Regards.
-
1
-
-
Hi, would you consider this request?
Thanks.
-
1
-
-
10 hours ago, Seb said:
I don't think this is something we would develop ourselves as it's outside the scope really of what we'd like to focus on - we'll do the integrations with domain providers but we don't really want to touch your payment relationship with them. Almost everyone would want to be using account funds if reselling domains.
However when this integration is open sourced you'll be able to add enhancements to the integration (or have a developer do this)
I see, I'll be looking into using account funds instead of the current method I'm using.
And I can definitely take a look on the open sourced integration when the time comes.
Thanks!
-
2 hours ago, Luis L said:
I can also confirm a wrong behaviour with dates wirh Spanish from Spain.
Also some dates are missing:
I believe those date formats were auto translated in the beginning and the translations were a little off.
I'm working on the Spanish and LA translations and I think I fixed this, but we need to wait for those to go live.
I don't know how to change those short month and day of the week translations I posted originally though.
-
1
-
-
Hi. Is there any possibility for this to be implemented?
Regards.
-
Would you have any insights about this?
Basically, how to manually manage unsupported registrars or very country specific ones.
Maybe with an offline registrar functionality or is there something right now I can use?
-
I see this issue is solved now!
A new set of translations were enabled in localazy and I now finished updating American English, Latin American Spanish and Spanish.
But there are some translations that are not showing up right because they need revision, I think, and I don't have access to do it. Would you be able to make a mass revision?
Also, are there plans to implement American English and Latin American Spanish?
Thanks!
-
1
-
-
I believe you're already working on more import paths for upmind. Please consider creating a migration path for Blesta's billing software.
If not for Blesta itself, maybe a manual way via CSV or database imports for pricing, invoices, clients, services, domains and so on.
Regards.
-
1
-
-
Hi.
I have some buttons and options showing with their internal tag instead of their translations.
Language is Spanish. In english, they show fine.
-
1
-
-
Great news, thanks!
-
It would be nice if options can be searched by their original english name + the language you're on.
For instance, to be able to put "payment gateways" and that option to appear.
-
1
-
-
Hi
I updated my admin panel's language to test some translations and I'm seeing this behavior.
It's like some of the dates don't change to the selected regional language and instead show in english.
I'm seeing that here: admin/upmind/overview, I can't check other places since I don't have any invoice generated yet for clients.
-
Finished translation for latin american spanish on the back end too.
I also updated some translations in spanish (spain) that where way off. For example the word Lead was translated as lead (the metal). Please update those translations at your earliest convenience.
Thanks!
-
1
-
-
Hi.
Finished working on these languages:
American English
- Back End and Front End
Latin American Spanish
- Front End
- Back end still in progress.
I tried my best to make this as neutral as possible for Latin America, and to maintain consistency.
Please consider integrating them to the app.
Thanks.
-
1
-
-
-
2
-
-
6 hours ago, Viswanath VB said:
Thank you, I think I need to take a look into de docs deeper 😅
-
1
-
-
5 hours ago, Seb said:
Ah ok - so something to clarify
*Everything* that happens in Upmind is an API call. We're API first, so the entire admin area and client area is just you interfacing with our API
If you lock down the IP restriction you therefore lock down both the admin area, and any API calls
We will be changing the API setup and making API tokens, and those we will allow to be individually locked down to IPs also.
Thank you, I understand more now.
Sorry for the trouble.
-
Just to add a little more info about this.
I see you released a resellerclub integration already (amazing rate of releases!)
Now, it asks for an API key, which I already have. But my API console requires me to whitelist the IP addreses from where API calls will be made, and doesn't allow me to save without one.
Are there some fixed IP addreses we can use for these cases?
Thanks!
-
1
-
-
Please make this field translatable for payment gateways
Thanks.
-
2
-
-
7 minutes ago, Seb said:
Yes, but it's not that exactly.
For example, the following is a screenshot from namesilo, when you create an api key, you can lock that key usage by IP. There are also some other providers (like resellerclub) that makes this mandatory
Are the IP addresses we add as an A record to the domain, the IP's from where the provisioning requests are coming from?
-
1
-
-
Some (if not most) providers have some sort of security for their API keys which includes whitelisting IP addresses, so no bad actors can access those accounts.
I'm assuming that all data in upmind is encrypted and protected, but it would sill be good if had the ability to lock those APIs by IP.
Considering upmind is a SaaS platform, would it be possible to get a functionality like this?
thanks.
-
1
-
-
Thanks
I finished american english in both BE and FE if you'd like to take a look sometime.
I'm still confused with the date/time thing. Because the source english language doesn't conform to the php standard. So maybe there's something wrong in my translations, considering spanish has for example DD/MM/YYYY HH:mm:ss but the php format would be d/m/Y g:i:s or something like that.
Nevertheless, I tried to conform every tag with the php format.
-
1
-
User Interface page is not localized
in Translations
Posted
Hi. This page is not showing in the brand's language: admin/settings/ui
I believe there are no strings related to this in localazy's project.