doolak

title*=j%FC (searched for "jü") response: {"selector":null,"total":0,"limit":50,"start":0,"matches":[]}

So the database collation seems to be ok, the page itself is set to UTF-8, too. No idea, what could be the reason...

Thanks, great - so no need to change it in the module itself.

But this does not make any difference - of course not, because it just sets the replacements for the page name (but nice to know, btw - i always thought that it would be better to have "ue" than "u" in the page name).

public static $defaultReplacements = array( 'ä' => 'a', 'ö' => 'o', 'ü' => 'u', 'đ' => 'dj', 'ж' => 'zh', LOL - weird that here it's different. Thanks, guys!

Thanks for checking, Wanze! The collation is set to utf8_general_ci - this should work fine, shouldn't it?

Yes, the problem was the field concat. Switched to title and it works now! Thanks, Ryan! Strange that the german umlauts are not found here - i have to enter "u" for "ü", then it finds the name with the umlaut "ü"...

The setting, which i had first when using checkboxes were: 1.) Parent of selectable page(s): /einstellungen/Mitglieder 2. label field: mitglied_vorname_name_geburtsdatum (concat field) 3. Dereference in API as: Multiple pages (PageArray) When switching to PageAutocomplete i used this settings: 1.) Parent of selectable page(s): /einstellungen/Mitglieder 2. label field: mitglied_vorname_name_geburtsdatum (concat field) 3. autocomplete advanced options: Contains phrase or partial word (but tried the others as well) 4. fields to query: mitglied_name mitglied_vorname 5. Dereference in API as: Multiple pages (PageArray) I am using a dev version of PW 2.3 which i downloaded few days ago.

Just found out that PageAutocomplete seem not support German "umlauts" - would it be hard to implement this? Don't know which other "special chars" are affected.

Yes, of course i have different options and i have to choose the search operator and the query when i have switched to PageAutocomplete - but the problem is that the field which is switched from Checkboxes to PageAutocomplete does not show any results then. As i mentioned i have tested if a new added field works fine and it does, with the same settings for the search.

I did not recognize until now this fantastic Input Field - saw it yesterday in the Repeater video and want to use it now instead of a Page field where i am using Checkboxes now. If i switch from Checkboxes to Page Autocomplete the new field does not show up any results - when i create a new field with the same settings it works just fine. But as there are already values set i have to switch... Can anybody confirm that problem or tell me how to solve it?

As i said, i really don't like to give the costumers too much possibilities and try to avoid the WYSIWYG as much as possible - guess you all know why: ( Source: http://kopozky.net )

Great idea to build that site, Nico! Christian Schindler mediakreativ.de (very old homepage - no time to build a new one... )

Perfect - thanks a lot, Soma!

Yes, but it is stripped out, too...

Thanks Soma, works perfect now for setting the table or table cell width and works for "justify left, right, center", too. Do you have any idea for the fontsize?

Again im am stuck somehow with this table width problem... How should one use TinyMCE if it is not more supported to set the width of a table or table cell? The different cells have no different CSS classes and even if they had, the person who edits the website cannot set the width in the CSS style sheet. It would be easy possible to use CSS classes e.g. for text align - but e.g. for font size or table width it is not possible. Of course i prefer to give the client just a very few options, no font size etc. - but there are some costumers who already worked with WYSIWYG and they want to have the same possibilities... I still cannot imagine that the newest TinyMCE versions do not support this anymore - in the editor it shows the preview for setting tect left, right, center and it sets the width of the table and table cells. So it has to be stripped somehow through the InputField, or not? Even if i use all the valid elements which are provided in TinyMCE it will not work. Any idea how this could be solved?

I have the following problem: The editor role has this permission: - delete pages - edit pages - move pages - sort child pages - view pages - user can update profile/password I have a template "teams"with the following access rules for the editor: - view pages - add children The children of the page are using the template "teams" and have this rules for the editor: - view pages - edit pages - create pages But although it usually should work, the editor cannot moce the child parents - he gets an error message which says that he has not the right to move a page with the parent "team". If I add "edit" to the editors access rules of the "team" template, than it works. But i don't want the editor to have the right to edit the parent page... Any body else who can confirm this problem? Or do i just have a mistake in thinking?

Forget the second question, please! That sorting is fine as it is - i forgot that if i want to display the recent years items under "Recent news" that can be easily done through the API... ;-)

Just had a look at the modules and found this one - great addition, thanks! I was about to build an news-archive and this module seems to do exactly what i need. Just one question... Before I found this module I already had prepared this pagetree: News (not-viewable) - Recent News (template = news_overview) - Lorem Ipsum (template = news_article) - Dolor Sit (template = news_article) - Archive (template = news_overview) The whole pagetree is shon on the page as dropdown - one can just klick "Recent News" and "Archive". In the archive i planned to have an overview of the passed years. Now i installed the module, choose the template "news_article" to be archived and the template "news_overview" as year archive template. After i saved an article the page "2013" was added under "News", the page "Archive" was deleted. Should this be like this? I guess the module works in the way it will place the archive pages under the same parent where the template exists, which is chosen to be archived - but should an existing page be deleted? One more question: Is it possible to have the actual year news items listed under a defined page, e.g. "Recent News" and just the items of the passed years listed under a page which is named like the year?

Wow, that offers new possibilities! Would this have the effect that the original ProcessPageAdd.module will not be used anymore or could i verify in the ProcessPageAddDoolak.module the parent of the added page and just then use the new module?

Yes, i am using it as a label for a Page Field - works fantastico now, thanks again!

Hm, it does not work here. I have updated the module, I have even emptied the assets cache, but the concat field still shows the unformatted date.

Yes, I want to manipulate something on the admin interface side: Each member of a sports club is saved as page, i don't want the website editor to have put in name and first name as title when adding a new member, maybe with a number if there are two members having the same first and last name - and then entereing first name and last name again when editing the member page to have both values seperatley. So i first had the idea to populate the title field of a new added page during ProcessPageEdit dynamically, e.g. with a increasing number. As i couldn't manage it to check the template of the new added page or the number of existing pages using this template - at least i was not able to check any parameters of the pages. I found some information in this post, but this did not work for ProcessPageEdit (or i just made something wrong). So i began to use just Jquery (as described above in my second post) and made a little module which populates the title dynamically with the name and the date of birth after they are entered in the edit page: <?php class PopulateTitle extends WireData implements Module { public static function getModuleInfo() { return array( 'title' => 'Populate Title', 'version' => 101, 'summary' => 'Populate the title field dynamically', 'singular' => true, 'autoload' => true, ); } public function init() { $this->addHookAfter('ProcessPageAdd::execute', $this, 'addScript'); $this->addHookAfter('ProcessPageEdit::execute', $this, 'addScript2'); } public function addScript(HookEvent $event) { $this->config->scripts->add($this->config->urls->PopulateTitle . "populate_title.js"); } public function addScript2(HookEvent $event) { $this->config->scripts->add($this->config->urls->PopulateTitle . "populate_title2.js"); } } populate_title.js: During ProcessPageAdd this script checks if the page which will be added is in a child of the "Members" page, if it is, the timestamp is added as title to keep it individual. Same for the page name. It hides both fields and triggers a submit, so the page is added automatically. jQuery(document).ready(function() { if($('input[name=parent_id]').val() == '1015') { $('input[name=title]').val(new Date().getTime()); $('input[name=_pw_page_name]').val(new Date().getTime()); $('#wrap_Inputfield_title').hide(); $('#wrap_Inputfield_name').hide(); $('#submit_save').trigger('click'); } }); populate_title2.js: When editing a page it checks again if the page is a child of the "Members" page, empties the title, checks if the members name is already entered (mitglied_name) and displays "Neues Mitglied" (New member) as title if it is not. If there is a members name entered (which is a required field) it concenates name, first name and date of birth (all required fields) and uses them as page title and, a filtered version as page name: jQuery(document).ready(function() { if($('input[name=parent_id]').val() == '1015') { $('#title').empty(); if($('input[name=mitglied_name]').val() == '') { $('#title').append('Neues Mitglied'); } else { $unfiltered = $('input[name=mitglied_name]').val() + ", " + $('input[name=mitglied_vorname]').val() + ", " + $('input[name=mitglied_geburtsdatum]').val(); $('#title').append($unfiltered); $filtered = $unfiltered.toLowerCase().replace(/[\*\^\'\!\,]/g, '').replace(/[\.]/g, '-').split(' ').join('-'); $('input[name=title]').val($unfiltered); $('input[name=_pw_page_name]').val($filtered); } } }); So this does exactly what i want, even more (as it corrects the page name dynamically after name, first name or date of birth are changed later). But i am sure that one could have done the same with PW API - without using just jQuery and that would make it possible to write a module which offers the possibility to choose the fields which should be used as title dynamically. Hmm... Maybe one could use a modified Fieldtype Concatenate for this?

Wow, great! Thanks ryan! (Do you ever sleep?)