alexcapes

Thanks Ivan for pointing me in the right direction - I'll see how I get on! Just out of interest do you think the other route is possible? ie. once an editor on the translated version has selected the English version from the pagefieldtype, using the English versions page slug for the translated version in the templates?

Hi, I've been creating a site that has multiple languages but crucially does not use Processwire's awesome inbuilt multi-language support (some background here). My site tree looks something like this... Home - Articles (English) -- Article title -- Article title -- Article title - French -- Articles --- Article title --- Article title --- Article title - German -- Articles --- Article title --- Article title --- Article title etc Now the client want the page slugs to be the same on all languages, so for example an article will have a url like domain.com/articles/name-of-article/ domain.com/fr/articles/name-of-article/ domain.com/de/articles/name-of-article/ etc. The problem... To make life easier for the translators they want the translated articles to auto-generate that page slug. Processwire can't really do that when a translator adds it as it doesn't know which article it is a translation of. Once on the edit screen I have a PageFieldType so the translator has to explicitly select the English version that their post is a translation of. This makes it easy for me in the templates to share content that doesn't need translation such as main image etc. So... I either need a way to extract the slug from the English version and use it for translated versions auotmatically (once the PageFieldType connection is made) overiding any slug that the translators have used. or even better.... I thought a module that automatically creates an unpublished page under /articles/ in all 12 languages with the same page slug when a new English article is added under /articles/. Would this be possible with Processwire? I'm not sure where to start (I'm very much dipping my toes in modules but have used Processwire extensively for projects previously). Any help/guidance would be massively appreciated, thanks!

I've been having multiple issues with my Grid Server databases over the last few days. After about 6 years I'm now considering moving away from Mediatemple (also considering it's now owned by GoDaddy) .

I'll definitely flag that this functionailty is on the horizon but sadly I think it may be too late for this current project. I've already put together a prototype, using multiple languages in separate posts, then utilising URL segments and also page fields to connect the translations to the 'master' English version. Translators are then only allowed permission to edit on the templates of their language. The downside here is it's a very fiddly and time-consuming setup, with more templates/fields than I'd normally like to create. However I've got it working well and Processwire as always is flexible enough to be able to cope.

This is great news!

Definitely take your point on this. I'm dealing with a large corporation that have 12x teams dealing in 12x languages and established processes that I may just have to work around. Hopefully I can persuade them that writing outside of PW then having one editor to paste in place is a good route to go. Really great to see this on the roadmap! I wonder if there's anyone who knows more details on this?

I'm working on a site that has 12x languages (and 12x translators) and following on from working out how to create roles that only allow editing of one language, the client have requested that these translators be able to edit at the same time. What are the possibilities here with Processwire? I'm thinking (potentially) 12x users editing the same page is a nightmare of overwritten changes etc. Has anyone had any similar requests from clients for multiple users editing at the same time? I think the solution may need to be 12x languages manually added so the page tree is: Home - English -- Articles --- Article title --- Article title - Spanish -- Articles --- Article title --- Article title - French -- Articles --- Article title --- Article title etc However I'd prefer not to do this as it's *a lot* of duplication and also not using the inbuilt language options of Processwire. Any help/thoughts on the best way to tackle this much appreciated.

haha yes but it's a solution, all the client cares

Ok so I got what I think is a workable solution... Installed Ryan's Page Edit Field Permission module Created 'language alternate field values' for each of my languages for each field, rather than using the multi-language fields. Added these fields as permissions using Ryan's module. Created roles for each language, so for example 'german_translator' role can only access the German alternate fields. It all seems to work well, and hopefully is pretty much exactly what the client was looking for in my first post.

Agreed, it's sort of a tantilising glimpse that something may be possible with the correct knowhow. It would be a really cool module - the flexibility of Processwire continues to amaze me.

Maybe it's not really supported - I just saw if you select a Tecxtarealanguage field you are then presented with IDs in the second dropdown in the 'What can they view?' 'What can they edit?' options (and only when you add them as 'subfields') see image below:

Thanks very much for this - I'll have a play with this but I fear it may be too fragile solution for the site I'm working on.

All on one page - I'm using the TextareaLanguage and TextLanguage fields and have the tabs for 12x languages on each field.

I've come across this module Dynamic Roles from Ryan that after some playing round with I notice let's you make roles specifically to do with a language. So for example, on the field 'article_body' I am actually presented with multiple IDs on the dropdown for viewing/editing options. These IDs are listed named in the format 'data1017', 'data1018' and so on and seem to refer to the language tabs on the field. So I wonder is there some way to combine roles and dynamic roles to let specific users only view/edit specific languages on fields? It feels like there are some clues here?!

Hi all, A client needs 12x languages on Processwire - I've set this up and it works beautifully out of the box. Again Processwire is wonderful thing. One thing they've asked for a way that languages are shown on fields on a per-user basis. This is so translators won't be able to accidentally edit the wrong language. So for example: A German translator will only be able to edit the German version of the fields. Is this be possible? I know that you can set a default language for each user, but could there be a way to set this and therefore restrict their access to one language only. Any help here would be massively appreciated as always. Thanks!

foreach($pages->find("template=area_page") as $a) { if($pages->get("template=artist, areas=$a")->id){ // Found a page with this area so it's used } } ^ this worked perfectly. The one-way connection of a PageTable field was the thing that threw me, I was trying to work a way back but couldn't do it. Thank you!

Hi, Working on a festival site which has artists pages and area pages. On the artist page you can associate area pages with that particular artist by way of a PageTable field. On the line up page you can then filter the artists by area. As shown below: <select name="area" onchange="this.form.submit()"> <option value="">All Areas</option> <?php foreach($pages->find("template=area_page") as $a) { $select = $a->name == $input->get->area ? " selected=\"selected\"" : ""; echo "<option$select value=\"{$a->name}\">{$a->title}</option>"; } ?> </select> All working fine but I'd like to be able to only show the areas that actually have artists associated with them. ie. currently some areas are empty so shouldn't appear in the dropdown. I'm sure there must be an easy way to check if the areas have artists but I can't think how to do it. Any help would be hugely appreciated as always.

Thank you very much for those links, will investigate (+ also look at searching better!)

**Sorry for clipped post title!** Hi, I standard have pagination setup on a 'news' section of a site I'm working on. I've noticed that Google has picked up the /page2/ etc pages. I've looked into excluding these paginated pages from Google's index and found that rel=next + rel=previous HTML link elements is the way to go. So I need to add this on the first page: <link rel="next" href="http://www.example.com/article/page2" /> And then on subsequent paginated pages... <link rel="prev" href="http://www.example.com/article/page2" /> <link rel="next" href="http://www.example.com/article/page4" /> And one previous link on the last page, for example: <link rel="prev" href="http://www.example.com/article/page6" /> I've dug around and can't seem to work out how this might be possible with Processwire (I'm sure it's simple as all these things seem to be with Processwire). Can anyone help?

Swopping out... $page->children for $page->pagetable throws up errors Error: Exception: Method Page::pagetable does not exist or is not callable in this context I can't find reference for "$page->pagetable" anywhere in the docs/forums? **UPDATE** I got this working by using the name of the pagetable field not 'pagetable' doh!

Ah starting to get my head round it. Is there a way to pull out the pages in a PageTable field in a template in the given 'drag n drop' sort order?