zlojkashtan

Not hard, but you need to know what you are doing . Changes will be required in both modules - FieldtypeEvents.module and InputfieldEvents.module. Changes needed in the former are slightly more tricky since Fieldtypes describe and create database schemas. Looking at the code, currently the field 'data' that is required by all Fieldtypes is currently being used to store the values of the 'date' field as a unix time stamp. This would probably have to move to another column in the database, e.g. 'date' so that 'data' can instead hold the id of the selected page in your page field type. Changes to the latter are relatively easier. You would need to add a column to the events HTML table. You could then use the API to add, for example, a select field:

$f = $this->modules->get('InputfieldSelect');
//more field properties as required...

$opts = wire('pages')->find('template=hosts');

foreach($opts as $opt) {
		$f->addOption($opt->id, $opt->title);	
}

From here it is just a matter of $f->render() in the table column you added (the <td>), to get something like this:

Does it work? Can U send me files? Thank you!

wtf with module and this page http://modules.processwire.com ? They show that there are updatetes for almost every module every day but...

Thanks this was helpful. Only change I had to make was for this section:

                <denyUrlSequences>

                    <add sequence="inc" />

                    <add sequence="info" />

                    <add sequence="module" />

                    <add sequence="sh" />

                    <add sequence="sql" />

                    <add sequence="\..*" />

                </denyUrlSequences>

 

I had to remove the  <add sequence="module" /> line. It gave me a 404 for the module section in the admin until I removed that.

After adding this piece of code I had a problem with the URLs (/information/, /show-all/ etc. ). This manifested itself even in the names of pictures.(trash.png, showreel.png) The problem is that you forgot to put the points. Right?

Oh, man. Thanks a lot. First variant solved my problem. Nice support!!!!

Can you paste in the exact text? I just want to try and see if I can duplicate locally. Though I was assisting someone else with Cyrillic text a couple weeks ago and everything worked well for me. It turned out that their PCRE version was from PHP 5.1 (even though their PHP version was 5.3), and didn't support Cyrillic. However, that doesn't appear to be the case for you as your PCRE appears to be up-to-date.

Check your PM.

I have to say that I used cyrillic titles in PW and everything worked like a sharm. I think the problem is in php or apache config, not PW.

I can't save russian text in any field. You can look on my phpinfo http://nbs.kiev.ua/test.php. PCRE ver. is 7.6 2008-01-28. field_title charset is utf8_general_ci. Thnk for your quick answer and sorry for my english.

I have the same problem on ProcessWire 2.1.0. Can you help me?

Also wanted to mention that roles can be used in combination. You can assign as many roles to a user as you want, each with different permissions. They will only receive the permissions assigned to that role on pages that are also assigned that same role.  It's powerful in that you have very fine grained control over access.

Hurrah! finally. it works well. Until then, I have never met such use of roles. I'll know. Thank you!

But multi language support is next on the roadmap followed by the user system.

For back- or frontend? My offer of help with translation into Russian is still valid!

one of my bugs are - what you must give the possibility to edit "Ноmе" page so that you could edit "News" page.

otherwise we get admin page without a list of all pages.

Also there is a discrepancy in the admin page and AdminBar. If we disable the "ProcessPageList" then in the admin page shows "You don't have permission to execute this Process: ProcessPageList" but AdminBar everything works fine.

The ideal option would be to give the user the authority to work in one section of the site, while other sections to which it does not have access to better make invisible.

I will still describe noticed if you understand my half Google translator language.  ;D

Thanks for the quick reply. Half of the necessary capabilities - implemented, but still, the system access distribution has many bugs that let you crap away the main admin.

p.s. sorry for my english.

Someone has ideas about creating additional admin site that will have access to edit only a particular section of content? For example, several editors for the section "news " and a few for "articles" etc.

Nice advice.

After global cleaning and re-installation everything work correct!!

Thanks a lot.

Does anyone have this problem with a sitemap?

I solved it only in this way -

file: /public_html/site/modules/AdminBar/AdminBar.module

220:  <li><a href='{$this->config->urls->admin}adminbar/ab-sitemap/?curPageId={$this->page->id}{$modalGet}' class='{$modalClass} pages'>View sitemap</a></li>

delete: ab-sitemap/

220: <li><a href='{$this->config->urls->admin}adminbar/?curPageId={$this->page->id}{$modalGet}' class='{$modalClass} pages'>View sitemap</a></li>

So now it works fine