Gideon So

Hi @oflcad, Welcome to the forum and the world of Processwire. Do you mean that you need to move the development site to a production server?? If so, there are several ways to do it. 1. Export the datebase and import it to the production server then upload the whole site to the production server. Please amend the site/config.php file as needed if database name, database username and password are different from your development server. You also need to amend the $config->httpHost in the config.php file to the production domain. 2. Use the miration module. and there is a blog post about it. Hope this helps. Gideon

A quick thought: make a subdirectory within the old site and develop the new site there. Delete all the old stuff (remember to leave the new site directory). Then move everything in the new site directory to the main directory. Done. Gideon

Hi, 1. PHP notice is not error. Your code still valid. 2. Try change the line if displaying image to the following: <?php echo $member->images->first()->url; ?> Gideon

It is very hard to tell because I don't know your template settings and page structure. Gideon

Hi @mattcohen, I see. But I think the title=$item_title selector may just return 1 page. This is the reason the found page is not sorted. Please provide more info, for exampe , your template settings, page structure and what you want to achieve. Gideon

Hi @Matt Cohen Deleted Gideon

Hi @benbyf, Put setlocale(LC_ALL, "fr_FR.UTF-8"); into ready.php. Gideon

Have to tried to read the source code of the page to see if the field values are properly propagated? Gideon

Hi @adamspruijt @Torsten BaldesBaldes, Please add comment here https://github.com/processwire/processwire-issues/issues/724 And let see if we can raise some attention from @ryan Gideon

Hi @ryan, Can you look into this issue again: https://github.com/processwire/processwire-issues/issues/724 The fix is good for single language environment but there is error show in the backend under multi-language settings: https://github.com/processwire/processwire-issues/issues/724#issuecomment-443126270 Gideon

Hi @MateThemes, Welcome to the forum. There is no build-in function as far as I know. But I think it is feasible with some custom code in the template. Gideon

Give page table a look. I made a single page site with it. Gideon

What is your database collation??

After upgrade to 3.0.118. The AdminUiKit become a mess. It losses all the CSS styles. Chrome gives me this error: By the way, this happens with botm Chrome and Firefox. Gideon edit: upgrade to 3.0.119 solved this problem.

Hi, Welcome to the forum. The graphql module doesn't support repeater or repeater matrix as far as I know but Processwire is definitely able to be a headless CMS. Gideon

I am not very familiar with url segment. Any hints??

Hi, i have two branches in the page tree as the following: home -branch 1 --page 1 --page 2 -branch 2 --page 3 --page 4 I have two languages enabled in the home page "lang1 and lang2" The url generated is http://mysite.com/lang1/branch1/page1/ I want to have the url generated as http://mysite.com/branch1/lang1/page1/ Any hints are welcome. Gideon

@szabesz I tested @BitPoet solution and it works well. Thanks BitPoet for the work around but hope that @ryan will make this change to the core. Gideon

This is a blocking bug that prevent non-ascii user upgrade the core beyond 3.0.110. @ryan any chance to take a look at it?? Gideon

me too here. I was totally sold by this video and this https://processwire.com/docs/tutorials/hello-worlds/ help me to get start with Porcesswire. Gideon

I would suggest you to go for option A. It is flexible and extensible if you want to add more content type later. Gideon

Please help to bump this issue in github. I think this bug is quite critical. https://github.com/processwire/processwire-issues/issues/724 Gideon

Hi, After testing with different version of the core. I found that the creation of page in page field function normally up to 3.0.110. It doesn't work anymore from 3.0.111. I will file a bug report to github. Gideon

Hi, I think this is a bug in the Page Reference field which was introduced after core version 3.0.106. I tested it with both multi-language and single language setting. Both of them give the same error when trying to create a page with non ASCII page name in the page edit page. Should I report this to the github bug issue? Gideon

I create a page reference field that allows user to create new page in the page edit page. I got this error: Error adding page "一二三" - SQLSTATE[HY000]: General error: 1267 Illegal mix of collations (ascii_general_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' think it worked fine before I upgraded to 3.0.115. Any idea? Gideon