Soma

When I have a selector with a parent.field all other fields get ignored: title|body|parent.title%=keyword Doesn't return result that would be found in title or body anymore. Is this a limitation for the parent field?

Its in since a week or two.

I remember when there was or maybe still is a bug with when languages installed that when installing a module admin page it doesn't set the title for alternative languages just default, depending on user language who installs the module. So I just went a looked at the process admin page... Turns out the "name" of the page is correct for both languages, BUT the "active" checkbox isn't set. This is from the new Language Page Names module. Setting this checkbox active for the laternative language it starts working and the edit url is correct. This is a tricky one that will may cause some trouble in future with module developement that use techniques like this... I can already see.

My language setup is standard languages module, language fields and language page names. So the user language is the one you currently view on the front end. New language page names module does all the url and user language. This is the default link http://pwmultilang.ch/processwire/page/fredi-field-edit/?id=1001&fields=body&modal=1 this is when on alternative lang: http://pwmultilang.ch/?id=1001&fields=body&modal=1

Hey, just tested this with previous version and seen you updated. So I grabed it and I can't see a difference to before. When on default language it open modal with body and both languages to edit fine. When on alternative language of the page, the modal just loads the home page inside. It would be nice to have the modal bigger. My Images Manager or insert image modal does open inside it and it's quite claustrophobic.

Ah ok that something. But the languages are active. But I had on the home, entered "en" in both default and german language name. I corrected that and have now default "en" german "de" on home page. Now the german pages work for guest user but NOT the default language, it just shows 404. Now the url is /en/about/, but the page about shows only /about/ as the url. So somehow the language segment for default language doesn't work for default, but works on the alternative languages. So if I remove the "en" on home name it works. So there seems to be a bug.

Well, the process module doesn't have diabled install button so something is wrong.. ProcessFredi and FrediProcess are different modules, so it can't work

The body text isnt shown on the page just an edit link instead of the body text. Ah now I get iz. Think it wasnt too clear about from your example.

I'm on a other install with no languages. Still doesn't output the body text when using echo $fredi->body. Just the edit link.

I just tried on a non language install, and got same issue. Thanks, yeah it seems the process module doesn't get installed at all. Although it says it installs it, it doesn't. I installed the proces module and now the edit link works and opens field, but the text still isn't shown/rendered on page...

I also just tested with a non language field and same issue as above. I don't know what is wrong.

Yes I have scripts. I get the link only with no text and if I click it just loads the homepage in the modal. <span onclick="TINY.box.show({iframe:'http://pwmultilang.ch?id=1001&fields=body&modal=1',boxid:'frediModal',width:750,height:450,fixed:true,maskid:'bluemask',maskopacity:40})" class="fredi fredi-body">edit</span>

Not sure what about it, but when I'm logged out (guest) the language page names doesn't work at all, it just throws 404 on front-end. When I uninstall the module I can access the pages (without language url) just fine.

Does it works with language fields? Because all I get is a "edit" text instead of the body and a edit link.

Apeisa i think you have to set some track changes when modifiying repeaters. Am on mobile so cant look.

Let pw do its work and youll be fine. Just have to remember to echo it! Btw what about permissions?

Wohoo apeisa hws a new baby! Great to have this!

You can also boostrap. I often put an ajax folder in root and have check in the php if processwire is defined. So it cant be called directly. Yes you nailed it. Your example to use root var in your scripts.

The best way would be tu use a page field with autocomplete. Like you can have a lost of drink and add one directly from autocomplete search.

It means you get no empty drinks... Buahh

There's also a "lock page" page settings. And a permission for setting the lock.

You can' specify multiple roots, but you can exclude children. $options = array("selector"=>"id!=1003|1004"); echo $navTree->render($options); So the pages with those id's wont be rendered. Or you could add a checkbox custom field to the templates to only include them if checked from the navigation. $options = array("selector"=>"show_in_menu=1"); echo $navTree->render($options);

You can set your own hotkey is the modules settings. I know windows uses ctrl+s is, so you have to use something else. It's not easy to decide easy hotkeys that work on all platforms and browsers so it is configurable, backdraw is ideally it would also need to be configured per user and not as simple to do as it is now. It's appreciated if someone likes to take the challenge, I'm happy to collaborate.

Adding the style to valid elements solves the problem to not get stripped of in tinymce. Works fine here and I use it all the time. When I remove the style from valid elements tinymce strips the inline style when viewing source thus also on save even though the text is aligned when clicking align button.

You cant put php files in templates folder and directly call them via url. You have to put it in root somwhere else. Its blocked by htaccess.