Radek

Just installed ProcessWire 2.2.16 with default profile. Installed core module: Languages Support 1.0.0 Created new language and see problem - no options to add language files. Can somebody else test it too?

Yes you write your code outside PW admin in your favorite editor. This is way i like it too.

Hi, when i start with PW most importand things to realize was: Custom fields belong to templates. Every page have some template. Templates processing data from fields and i can thrue template files (php) and API show/process data from fields to frontend. Simple Example: You can made field with name content (textarea for example). Create file test.php in /site/templates and fill it with your html (head/body/....). In admin create new template and select test. In admin create some page and give it template test. Edit /site/templates/test.php and add API function to show content field on place where you want <?php echo $page->content ?> Now you can edit your page(content field) in admin and frontend show result. This is very basic example, in real you can made it more clever. I think you need read links posted above too and this forum is full of nice examples/tutorials/snippets.

Welcome to forum. I think you have problem with .htaccess Look here.

Updated czech localization pack (contain 85 files). Current version: 0.9.2 pw_czech_092.zip

Hi, kawaramono.cz is little presentation web for my friend made with PW. Pretty simple solution with full content administration, zurb foundation framework and colorbox.

Hi, lookig forward to tax support. For begining will be good to may option to create taxes like: Name - Value - default Basic tax - 21% - yes Lower tax - 15% - no ... And have option to select/show this custom created taxes to products. (Option price with and/or without vat). Offcourse cart need to show and count that. Dont know if this is enough, but discussion may start.

No problem and welcome to PW forum You can try dev version, because will be stable soon and any testing are welcome.

Maybe need change RewriteBase /pwdir/ in .htaccess?

One project upgraded from 2.2.9 to 2.3dev without problems. - Apache 2.2.23 - PHP 5.4.11 - MySQL 5.5.30

One more catch. /wire/modules/Fieldtype/FieldtypePage.module: 535 $select->label = 'Dereference in API as'; 536 $select->description = 537: "If your field will contain multiple pages, then you should select the first option (PageArray). " . 538 "If your field only needs to contain a single page, then select one of the single Page options " . 539 "(if you aren't sure which, select the last option)."; 540: $select->addOption(FieldtypePage::derefAsPageArray, 'Multiple pages (PageArray)'); 541 $select->addOption(FieldtypePage::derefAsPageOrFalse, 'Single page (Page) or boolean false when none selected'); 542 $select->addOption(FieldtypePage::derefAsPageOrNullPage, 'Single page (Page) or empty page (NullPage) when none selected'); Thanks

Hi all, this is first complete version of czech localization pack for ProcessWire 2.3. Almost 100% of text strings are translated. Please download and test this pack. Send me any comments to improve it. I decided that version 1.0 will be published after longer testing period. Current version: 0.9.1 pw_czech_091.zip

Version 0.8 finished and few other missing translations found. /wire/modules/Fieldtype/FieldtypeDatetime.module 443: $f->label = "Date/Time Output Format Code"; /wire/modules/Inputfield/InputfieldDatetime/InputfieldDatetime.module 255: $f->label = "Date Input Format Code"; /wire/modules/Inputfield/InputfieldDatetime/InputfieldDatetime.module 268: $f->label = "Time Input Format Code";

Thank you Ryan for great work. Issues solved and everything work fine. Total translatable files in dev branch is 84 now. Czech localization progressing fast, i think i will have version 0.8 tommorow.

Easy to reproduce, i have translated strings from Inputfield.php in wire--core--inputfield-php.json But when look on page where may display, strings are still in default en.(not translated.) For example that string from issue 153, but there are more of them on more places. And few others missing translations: /wire/core/Field.php 359: if(!$fieldgroupContext) $inputfields->head = "Input field settings"; FieldtypeText.module (/setup/field/edit?id=xx) $f->description = '' . 'If you want to apply any automatic formatting to the field when it is prepared for output, select one or more text formatters above. ' . 'If you select more than one, drag them into the order they should be applied.'; FieldtypeTextarea.module (/setup/field/edit?id=xx) $f->description = "The type of field that will be used to collect input (Textarea is the default). " . "Note that if you change this and submit, the available configuration options in " . "the 'Inputfield Settings' section below may change."; FieldtypeTextarea.module $f->label = 'Inputfield Type'; 66 $f->description = 67: "The type of field that will be used to collect input (Textarea is the default). " . 68 "Note that if you change this and submit, the available configuration options in " . 69 "the 'Inputfield Settings' section below may change."; For Soma: little weird is that TextDomainHelper.module show under this string path /wire/modules/Inputfield/InputfieldCheckbox.module but real path is /wire/core/Inputfield.php

Ok, the biggest found issue - https://github.com/ryancramerdesign/ProcessWire/issues/153 And one missing translation support, that is on the eyes. /wire/modules/Process/ProcessTemplate/ProcessTemplate.module (/setup/template/edit?id=xx) 1047: $field->label = "May pages using this template have children?"; I know how look gettext rules "Plural-Forms: nplurals=2; plural=(n != 1);" but not much about gettext implementation, so i cant help much here.

Hi Ryan, i tested new LanguageTranslator.php and everything works fine thanks! Credits for TextDomainHelper.module goes to Soma as he is author of this module. I gave him only idea. Yes i will add czech localization to processwire.com soon, looks like its not alpha anymore . Can i continuously send you somewhere my findings of missing localizations like (/processwire/access/users/ - E-MAIL ADDRESS, /processwire/access/users/ - ROLES)? Seems like they missing in PW. One more about plurals - seems like plurals in backend need update too. Example(modules/PagePaths.module): EN Singular Version(1): Updated %d path EN Plural Version(2->): Updated %d paths CS Singular Version (1): Aktualizována %d cesta CS Plural Version(2-4): Aktualizovány %d cesty CS Plural Version(5->): Aktualizováno %d cest

Nice work soma, using it alot.

Hi all, this is my first post here so i must tell that ProcessWire is the best CMF i know. Good work Ryan and others. After 14 days with PW i made two sites and alpha version of czech localization package. After hard time translating PW backend i found that i need one more tool. Tool which can find json files used on specific page. We speak about it on IRC with Soma and he made awesome new module for me TextDomainHelper.module https://gist.github.com/4520324 This module gives new posibility to Chrome PHP Debug module. In js output i can find all used strings and where are stored. Without this tool its much more dificult to translate PW! Example output: textdomain:/srv/http/pw_dev_translate/wire/templates-admin/default.php Text:Admin This module needs to have LanguageTranslator::getTranslation hookable. Ryan, can you make it hookable please?