adrian

Is the category page field's "Dereference in API as" setting set to Multiple or Single?

Try: return $pages->find("template=subcategory");

This is consistent (although not intuitive) throughout PW. You need to click on the selected page and click "unselect". If you don't like this behavior, there is a new module that makes things more intuitive: http://modules.processwire.com/modules/page-list-select-unselect-button/

Actually I hadn't noticed that - thanks for pointing it out. Sorry it's taken so long to get to, but the latest version of the module now has a new config setting to optionally exclude pages outside the restricted branch from the search results of pages. Please test and let me know if you find any problems.

Looks like it might just be for 3.0 "This PW version is also the first to support ProFields Repeater Matrix" https://github.com/ryancramerdesign/ProcessWire/commit/eb8aa2f953154e34924081fcfc0f07bd748ceead

@Christophe, I am not sure about this module with repeaters, but the built-in field-level access control seems to work great with repeaters. If you have PW 2.6.2+ there is an "Access" tab for each field (in the field's settings) that controls which user roles can see and edit it. Does that take care of your needs?

Oops - I should have noticed your comments there. I actually didn't think about them not being added until the field is viewed in the editor. In reality when I have a PageTable field with the pages as children of the page, I just call the children, rather than the PageTable field, so it doesn't actually matter that they are not added until the editor is rendered. Perhaps that code could be changed to work on page save - check if the parent has a PageTable field in it and then check if the saved page belongs to the field?

Have you tried this: https://processwire.com/talk/topic/8177-page-table-howto/?p=89960 Not that I am suggesting you should use PageTables if the new repeaters work as required, but that does provide a way to have the new pages automatically added - I use it when I want separate URLS, but the client is confused about not being able to edit under the main parent page - like a list of staff for example.

Are you sure you only have Protected Mode installed? I wouldn't be surprised if there were some issues if you have both modules installed.

I think this: https://processwire.com/talk/topic/1176-hiding-uneditable-pages-from-users/?p=84916 is currently the best option for hiding specific pages from the admin tree, but I do agree that something better integrated in the core would be very useful.

Have you cleared the compiled templates? Modules > Site > Clear Compiled Files I think the error you are seeing is from a cached compiled template from before the problem was fixed in 3.0.4

You need to change the custom message on the Settings tab of the Home page. The message on the module settings page should populate newly added protected pages, but once a page has been protected, it stores its custom message separately. Let me know if you still have problems. I assume that the login template option is now working for you with the latest PW 3.x build?

Use sort in the children method like this, assuming the date field is actually "date": if($page->hasChildren) { $content .= renderNav($page->children("sort=date"), array('ul'=>'article-index list clearfix', 'li'=>'article-index__item'), 'post_date'); }

And the saving as "No" should be fixed now also! https://github.com/ryancramerdesign/ProcessWire/commit/c485972f70bc436bc203ceefb22bbf314ed826fd

The undefined variable error has been fixed in today's commits to the devns branch.

It was a bug with the File Compiler in PW 3.x - it has been fixed in today's commits to the devns branch. That does seem weird - the custom message should be between the <legend> tags. Can you provide a screenshot of the settings tab for the page in question?

Great work Bernhard! I think this should be in the core!

Fantastic writeup Ryan! Looking forward to an amazing new year with ProcessWire!

Hi @Sanyaissues - sorry you are having problems. I can replicate the problem with the custom template not working in PW 3.0, but aren't seeing the issue with the custom protected message not working - make sure you are editing the message on the Settings tab of the protected page. Now back to the custom template problem - do you have debug mode turned on in your config.php file? Do you then see this error: Notice: Undefined variable: loginForm in /pathto/site/templates/login.php on line 4 The problem seems to be passing variables using wireRenderFile. It works fine in PW 2.x, but looks like there might be a problem in PW 3.x Can you please confirm that this is the error you are getting. I am not really at my computer again fully for another a couple of weeks, but I will try to help figure this out. Anyone else out there reading this that has seen any problems with passing variables using wireRenderFile in PW 3.x?

Could you also add the new notes to the PageTable Automatic Page Name Format section on the Input tab?

Hey kixe, Thank you - this is awesome and solves one of my biggest issues with PageTable fields - getting meaningful page names without the possibility of conflicting names which I don't think the user should ever have to consider. One minor thing (but critical) - when installing with PW 3.x I get this error: Catchable fatal error: Argument 1 passed to ProcessWire\Pages::__construct() must be an instance of ProcessWire\ProcessWire, none given, called in /wire/core/Modules.php on line 481 and defined in /wire/core/Pages.php on line 128 It is easily fixed by adding an empty construct method to your module, like this: public function __construct() { // intentionally empty } I am definitely looking forward to using this with all my PageTable fields!

@FrancisChung - I am going to be offline for about a month, but please let me know how Migrator works out for you. I use it a lot in my development process for migrating new branches of content from dev to live, but I do know that there are still some issues that need to be sorted out. As I mentioned in the Migrator support thread, it's definitely not abandoned, I just need to find a good chunk of time to address some bugs. I would definitely recommend testing the migration from one dev site to another dev site first and if that goes as expected it should be safe to migrate to a live site. Also be sure to use the the inbuilt backup option just in case. Hopefully sometime in the new year this module will get some more love.

I have made the image editable as well though, so the problem is that the clicking on the top half edits the image, but on the bottom half edits the text, so not something that is acceptable - too confusing for the user. I understand the technical limitations though so not a criticism - more of an observation of a limitation.

Hey Soma, I still install this module on every site and was thinking that a nice addition would be to convert the "send_templates" pipe separated list of IDs to a comma separated list of template labels/names. Anyway, just a thought for when you're bored

I don't think that option is relevant for modes B, C & D, because they require you to manually specify the page that the field is on or they just don't work. eg, <edit field="image" page="<?php echo $other_page->id; ?>"> I am not sure about the performance issue - will wait to hear what Ryan says.