Hi!
Looks great.
Such a stuff was badly missing.
First of all: as I’m not a coder and have no time today to look into : is this localisable (language ? utf-8? ..of course ... I’m French huh!
Is there some demo somewhere or (real site) yet ?
Thank you
Schtroumpf Grognon - Grouchy Smurf
---------------------------------
Faites pas attention.. - Don't pay attention
http://www.dzi-neo.net
We’re working on localization. We have about 85% of the tags in a lang file that we install. The two things we’re doing now are:
1. Getting the last 15% of the tags moved.
2. Preparing a patch for the MODx core developers that refines how langs are done. We want to make it easier for module developers like us to add ’additional’ langs without having to overwrite the core lang file.
Plan on this getting much better over the next few weeks.
-
MODX Staff
- 12,272 Posts
Hi Chad,
Out of curiosity why couldn’t you just include your own language file for #2 as is done with other modules and snippets?
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Let us know when localization is ok.
Is there some translation to do ?
May be I could give a hand for FR (from ENG to FR)
just ask me if needed
Schtroumpf Grognon - Grouchy Smurf
---------------------------------
Faites pas attention.. - Don't pay attention
http://www.dzi-neo.net
The patch we want to submit isn’t so much a different way to include OUR lang files as it is a way to improve the entire lang system. There are some hacks available right now but they require you to make a decision about your entire interface. What if you have a Russian, a French, and an American site admin? We get the browser’s lang preferences, but discard them today because the site can have only one lang file.
What I had envisioned was a simple mod that would change the single include to an include that went through
lang/<code>/*
and included all the files there. For example, if there was a preference for French, it would include lang/fr/*. That way module developers don’t need to invent their own storage locations for lang entries, and modules that depend on one another can share langs. It also means if the user changes their lang preference they get the new lang - administrators need not actively CHOOSE a lang for their site. It ’just works’.
Any objections? We haven’t actually written this yet, but it’s about 5-6 lines of code - we just get the lang tag from the browser, scandir an include directory, and include_once each file.
This doesn’t do much for the site content itself - there still needs to be another solution for that. But, the nice thing is, this is administrator-agnostic for terms like ’Cart’. If you want the phrase ’Products’, Kiwee can provide a lang entry to the FRONT end that says ’Products’ in English or ’Produits’ in French. That way you could put a tag on a page that used that value, instead of hard-coding it.
hello!
I am planning to develop e-shop at domain .ru
In the documentation stated that KiweeCommerce supports only Authorize.net, Google Checkout, Paypal. But in my project i need another payment methods such as Webmoney, Ru-Pay, Yandex Money, Bank cheque.
I am wondering to know, How to extend the payment methods(russian payment methods) ?
-
MODX Staff
- 2,502 Posts
From what I recall there isn’t one anymore. Just skip this step as all your settings get entered into the installer page now.
I meant to write the guys at Kiwee to update their documentation.
Cheers,
Jay
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub