Guy Verville

I am glad to present our recent website. It was made, of course, with Processwire and this is the first time we use this CMS in our company. The website (in French only) is aimed to gather ski results from four youth ski clubs (our clients). The administrators needed something easy to use and be able to import XML ski results after a race. Those results are divided between ages (four categories, girls and boys), each ski category having its own rules for distribute points and ranking. The administrators wanted also a place where representatives of each club could post photos (elite team only). Processwire was the perfect candidate for this site which is fully mobile. Race calendar and results (click on this archived season to see the whole process since the present season has not yet begun as the writing of this post.) Annual ranking Documents (use of hanna code to place and identify type of document) Photo albums Elite clubs

Obrigado, Sérgio But this doesn't help. I am with PW 3.0.42. Since the problem resides actually on the language translation panel, it is not that important. Some day, I will find. Boa noite.

Olá Sérgio, This has been already done, but the problem persists. That's why I don't understand what's going on.

I do love PW for a lot of reasons, but the language translation tool is not that easy to deal with. The site I am working on is in French and there will be no translation, so the default language has been translated into French (importing the french language pack, which is not up to date, and completing lot of stuff). However, for a reason I don't know, some buttons stay in English. I was able to find the string pattern %s + Next, and tried numerous variation. Everything is translated except Save + Next! As we say in French, PW a des croutes à manger à ce niveau. (probably not really translatable... ;-) PW has some crumbs to eat on that level). While there was a great improvement on language translation management, wouldn't it be easier to have a tabled list of all translations? And, why, for example, should we have to enter the translation for "Save" at every occurrence in modules? ListerPro (which we purchased for that site) is really great to make searches. Would be fun to have translations strings placed in the admin area as pages... Food for stuff? Any way, back to my chase of %s + Next... (or whatever I will discover)

Bingo. The code in config.php is this: $config->paths->customPaths = array( 'plugins' => $config->urls->site . 'templates/plugins/', // Web vendors path 'views' => $config->urls->site . 'templates/views/', // Web views path 'styles' => $config->urls->site . 'assets/styles/', // Web styles path 'scripts' => $config->urls->site . 'assets/scripts/', // Web scripts path 'template_dir' => $config->urls->site .'templates/', // Web scripts path ); Exactly 5. My programmer created this. We will make a workaround. Thanks.

I constantly get this warning error PHP Warning: strlen() expects parameter 1 to be string, array given in... Path.php 133 I wonder what can cause this problem. I am not sure it is related, but I use the TemplateEngineFactory module (with Twig) Tracy Debugger catches the error. Always the same number of times : 5. I have made a var_dump and I haven't seen anything suspect ($value seems ok, or null). Any idea?

but the returned json works... anyway. someday, I will be good at programming ;-)

I did checked the browser console, but nothing appeared there. It was completely silent (either in Chrome, Opera or Safari). And why removing the PW debug mode gives me the result wanted in every browser? If I had such an error in my json result, why would then the process succeed? Would it be more plausible that the debug mode blocks part of the process?

I found the culprit: debug mode. I realized that when the Tracy debugger was on, everything was fine, even not logged. This debugger reroute Processwire debug mode, I presume... So I switch off the debug mode in config.php and voilà! Remains this bug...

The strange thing being that no such ajax permission exists. I will try to investigate...

Yes, this is a normal template file. The only difference is that this template is placed in a controller folder since I use FactoryTwigEngine. If I go directly to the page requested, I can see, not logged, the content.

which permission is responsible for that?

I am wondering if my problem has a link with the previous bog I wrote about some hours ago... I have an ajax call to pages. The code is based on: The only difference is that since I use the TemplateFactoryEngine, I must add an exit() command in the code. So, in my template file (controller), I wrote this: if($config->ajax) { $json = array( 'id' => $page->id, 'title' => $page->title, 'body' => $page->body, 'photos' => $photos ); // Output your json echo json_encode($json); // halt template rendering exit(); }else{ $view->set('photos',$photos); } and the AJAX call is made by script: $('#menuAlbum li').on('click', function () { var url = $(this).find('.chemin').text(); $.getJSON(url, function (data) { if (data) { .... Now the weird part: When I am logged, everything is fine. When I am not logged, no data is returned. ($this->halt() does not work in that context) I receive no error, I checked that the script was running when not logged (the url is retrieved). How can data can be fetched when logged and not fetched when not logged?

I am experiencing something weird. I have a date fields that shows the expected format when I am logged in, but show the timestamp format when not logged... Any idea of what's happening here? I have another site where a similar coding doesn't behave like this. I work with PW 3.0.39

I should have explore this before asking. Thanks again. This is really great.

Thank you Soma, I will download it. Meanwhile, one question remains, but perhaps it has been answered elsewhere. We will have dev, staging and productions sites. How can we manage a GIT flow around the fact that those sites won't have the same adress? It's easy to keep separate databases and not having the same content, but at some point, we will have to fill the official content in staging, so every "root" addresses will have to be changed. No big deal because it's only 10 subdomains. dev, staging, prod, naming examples: dev: dev.organization.local north.dev.organization.local south.dev.organization.local staging: staging.organization.local north.staging.organization.local south.staging.organization.local etc. That's what a mapping table would be interesting. The name of the "roots" wouldn't change in the tree, but the URL would be easily changed.

Yes, it look good, Adrian. I will keep my choice to PW to present to the client ;-)

Ok, i think I got it. When setting to "Role Name", the root of the site must be select.

The title of the page is different from its path. There are now multilingual settings here. Have you tried with the multisite installed?

ok, I understand. The role must match the page. The multisite module needs the branches to be set on the url name. For our example, it's nord.pw.local. The role should be then nord.pw.local? Addendum: it seems to not work.

However, while visiting the domain and the subdomain (pw.local, and nord.pw.local), it seems to bring cookies problem. I will have to investigate this. I tried to set the restriction by Role, and it does not seem to work. I can edit everything.

No, I just played with the settings, since you can allow user to see all the branches but edit just some.

Sorry, my bad. I forgot to apply correctly the page-edit permission to the template! It works.

Well, perhaps the first time, I didn't enter the site correctly. I can see the branch, but can't edit anything. I have created a role "nord" (for north region), which has the page-edit permission. I then created a user with that role only set. When I enter the site with that user, I see only the "nord" branch.

Please see above. But I will make more tests, to be sure.