Relmos

Hey, I just went the route to switch the language fields manually now. Took me about an hour, so everything is fine now. I red something about scripts too that would make the switching possible but the time to set up one would take the same to just do it manually I guess. I mean in the end it was my fault not set englisch default at first place anyway. It's a .com domain so de just didn't make any sense here. So learned my lesson. PW is so great in many ways (thank you ryan!) and it already saved me such a great amount of time that this one more hour is totally fine. But yes, if there is still something to say about this topic of course I'd be very interested.

Ok now I am really at the point of just manually switch the content of every field..

Still on it... Another idea: How would a simple redirect within PW from domain.com (index.php) to domain.com/en/ work?

Hm, I tried some now. But still I haven't found a solution..any ideas left?

Soma, thank you very much for this detailed answer. I guess what Ryan did was absolut correct cause this case now is really not the usual one. So I'll tinker around a bit with you suggestion. Maybe an option would be to really have control within the settings of the guest role using LanguageSupportPageNames in the end and add this to the feature list.

Thank's for your quick reply. At least I am back on the road that I already though would take me to your statement now. Actually the default language was wisely considered due to the fact that I thought it would be difficult to change it afterwards. But now someone must have pointed the idea at me that the page should start in EN now. Well then... But while domain.com/de always redirects to domain.com how would I be able to redirect domain.com to domain.com/en then since /de would redirect to /en then?

Thank you Soma for your answer. Here are mine: PW Version 2.3.6 and I did not yet made any language manipulations except using the language switcher from the Tutorial at MultiLanguage URL. When I am speaking of "default" language in this case I mean the language that a user sees the first time he enters the domain like domain.com. For now it's DE . I assume that's the case cause I startet PW with DE as the default language using the MultiLanguage URL approach. The second language is EN. Both have a suffix in their URL Structure, like: domain.com - root DE domain.com/de/page domain.com/en/page Now I would like any new user to start with the EN version of the site like domain.com/en. I added the /de/ suffix cause I though I could them shameless redirect domain.com to domain.com/en. But of course domain.com is the root any redirect wouldn't quite work here. Besides that this redirect is really bad. Ah ok. So how would another approach look like? And what then is the real use case of setting a language for the guest user if it doesn't work here? That is actually the first thing that came to my mind and the worst I could think of right now

Hi arjen, thank's for your offer here. But I guess that's already what I did and I wouldn't know what else could be configured here. I already deleted all users just to test it, without any effect. By the way the error message I get refers to this post: http://processwire.com/talk/topic/3231-the-guest-role-is-required-error-when-saving-new-user/ So maybe I should update to the latest dev version anyway. But just to be sure (as now edited in my question) I am talking about the default language on the Front End. Not the users default language in PW as an Editor. This of course if working.

Ok, that's new to me, interesting. But then somehow it won't work here (PW 2.3.6). When I switch the language for the guest role to EN I get the a success and error message at the same time: And when I visit the site from another computer or at mine without being logged in it's still DE. Any ideas? Maybe I am missing something cause of the error here? And maybe I am not really getting the concept of the guest role here. Is it really the guest as visitor? So one that has nothing to do with the CMS itself? Cause a guest role is also defined within roles and permissions. That's a bit confusing.

Ah sorry, of course. Thought you were talking about an actual app user here. But yes, setting default languages for users within pw is possible. But that's not what I meant. Maybe I should specify my question: I am talking about the default language in the front end. So when the default lang is DE of course the site will always fallback to DE. But now EN should be the default language. So I am wondering if there is any kind of rewrite I am not aware of so that this is possible in the end?

Hi Fokke, thank you for your answer. What do you mean by guest user? - Relmos

Hi, I have started a website with default language DE. Second Language is EN. Now I would like to have EN as default. I already though about redirecting but nothing really seems to make sense/work here. Would this be possible & and how? Edit: Not to confuse here: I am talking about the default language on the Front End. Not the users default language in PW as an Editor-Role. So while now domain.com is the default language (de) I'd like to start with domain.com/en/ when you enter domain.com. Thank you. - Relmos

Ok, solved. See question.

Hi, I have two questions about the search coming with PW 2.3.6. 1. How would I be able to search word fragments? I only want titles to be searchable. If a title is "superdog" and you search for "dog" nothing will be found here. Only when you exactly search for "superdog". --> Ok found the answer here: http://processwire.com/talk/topic/168-wildcard/?p=1181 But strangely it's exactly the other way around. * will find "apple" in "applesauce" where ~ does only find results matching exactly the string. 2. I have a multilingual site. How would it be possible that the search also works in other languages? For now it always switches to the default language when previously the language was switched. --> Also found a solution here: Just have to get the language prefix as usual, for example: domain.de/es/search/, and it will search the spanish site. Thank you. - Relmos

Ok here the real scenario: Type 1 Repeater Type 2 Repeater Type 3 Repeater Since now the Types are each a fieldtype and hardcoded in the template. Now the client wants to be able to add more types and reorder them on demand. Since there's only the repeater solution now I cannot think of anything different than embed repeater B in repeater A. Or?