adrian

Glad that helped, but I think I will defer to one of the multi-language experts for the other part of your question - it's not something I use, so I am not very familiar with it.

Hi @Karl_T I think this screenshot should get you going - the "Name Format for Children" option allows skipping the manual naming of the page:

I can confirm that adding the ProcessWire namespace to a module and trying to run it on PW 2.x results in an error.

Have you tried again recently - that looks like it might simply be an access to Github error. The feed is certainly running right now so I would try again and if you still get the error, please check the URL directly to see if there is a problem at your end: https://api.github.com/repos/ryancramerdesign/Processwire/branches

Ok, here you go: http://modules.processwire.com/authors/mikerockett/ I am pretty sure you just have those two modules, correct? I have deleted the account author except for "mike", just in case it wasn't you.

Beta release is now available via the modules directory: http://modules.processwire.com/modules/admin-restrict-branch/ Contains a few bug fixes, adherence to Add New permissions, and the ability to restrict the name matching to the restricted branch to a master parent to reduce potential for incorrect matches and also improve matching selector efficiency. Despite it being released, please still carefully check that your affected users have the permissions and access that you expect and let me know if you have any problems!

There is really only the roadmap: https://processwire.com/about/roadmap/ I have asked Ryan for this functionality outside of the forum and his response was positive, but you won't see it mentioned anywhere official.

Hey Mike - looks like you have a lot of aliases in the modules directory. Are all these you? What do you want them all merged to?

I do believe this is on the todo list for repeaters, along with the ability to name each one (which is pretty important if they are initially collapsed).

Why don't you try adding them to children like: $children->add($this->pages->get(1088));

You can use insertBefore, eg: $newField = $fields->get("your_new_field"); $t = $templates->get("your_template_name"); $existingField = $t->fields->get("sitemap_ignore_END"); $fg = $t->fieldgroup; $fg->insertBefore($newField, $existingField); $fg->save();

Any module that is a textformatter needs to be applied to each of the required fields via the Text Formatters dropdown on the Details tab of the field's config.

Sorry, I am on a bit of a roll - I really do love this module I don't really understand the "Select the inputfields where the extra fields should be attached." option in the config settings. It lists all the different inputfield types, but the module only works with image field types. I actually tried to see if it works with InputfieldFile, but it didn't even work there. Am I missing something about this setting? I think a more useful setting would be to control which image fields (the actual fields, not field types) that imageextra is attached to. At the moment the "Image Extra Fields" fieldset is added to the Input tab of all image fields, which I expect most developers don't need - they probably only want them for certain image fields. Does that make sense and sound like a good idea? Thanks again

I don't know what to say about the issue with removing extra fields - I am continuing to get that error on different PW installs. But now I have another issue for you. With ImageExtra installed and Maximum Files Allowed set to "1" when I go to upload a second image, the editor actually shows both images. After save, the first one disappears, but without ImageExtra, the second one instantly overwrites the first one. This has been confusing for our users - they think a second image has been uploaded rather than overwriting the first one. I hope you can reproduce at your end. I wonder if it's a simple matter of incorporating some of the new code in: https://github.com/ryancramerdesign/ProcessWire/blob/980ce4f0be2054dfbad4a7b334d35bdca42da7da/wire/modules/Inputfield/InputfieldFile/InputfieldFile.module#L438 into your module at: https://github.com/justonestep/processwire-imageextra/blob/master/ImageExtra.module#L540 Thanks!

You can filter like this: foreach($page->fields->find("type=FieldtypeImage") as $f){ or you can create a new field array with: $myFields = new FieldsArray(); foreach(xxxx as $f){ $myFields->add($f); }

Just to add to this thread - I needed the check to run during init() and the best option I could think of was: if( wire("process") != 'ProcessPageView' ) { //in the admin } Can anyone think of any situation where this would fail? Perhaps some modules may run ProcessPageView in the admin? Maybe Nico's check for the admin path in the URL is a better option. Anyone have any more recent thoughts on this?

The latest version of PW has built-in hide/unhide and pub/unpub action buttons, so I don't actually think there is a need for this module anymore.

It's working fine here - are you saying it never returns any results from image descriptions, or are there inconsistent results returned?

As far as I know it's been around for a long time - certainly since 2.3

Thanks teppo - I do think it makes sense to keep this module a little more focused on single branch functionality. I haven't actually used UserGroups yet so didn't realize it could do that - thanks for the heads up. @BernardB - if you try out Dynamic Roles, please be aware of this bug: https://github.com/ryancramerdesign/DynamicRoles/issues/14 - I assume I am not the only one that is being affected by this - I provide a simple fix in that first post that you can implement.

I just added a couple of new options to this module that allow for automatic protection of unpublished and hidden pages and their children. I am finding the unpublished protection very handy as I can set the parent of a branch to unpublished while it is being developed. With this option enabled, I can send the link to this page direct to clients and they will be presented with the custom login form so they login and then immediately view the page - no need to go via the backend admin panel (just like the normal way this module works), and they won't get the 404 page if they attempt to visit when logged out. Because children can also be protected there is no worry about someone guessing the URL to subpages, the entire branch is protected based on the publication status of the parent. Once the branch is ready to be published, simply publish and it will be live and the protection is removed - no need to give clients access to the control of this module on the settings tab and explain how they work. Hope you all find it useful!

As far as I know, the only option is to do it with the buildFormContent hook. Have a look here: https://github.com/adrianbj/BatchChildEditor/blob/master/BatchChildEditor.module#L371 See the commented code of the old way I did this using the BuildForm hook and then the new way by creating a new InputfieldFieldsetTabOpen with buildFormContent. Hope that helps.

@BernhardB - just thinking about this a little - what method for matching users to the parents of multiple branches would you want? I think that likely the only option that would work would be the 'Specified Branch Parent' option. I guess you could assign multiple roles with names that match branch parent names, or perhaps the custom php code option could match branch parent names with partial name matching or something, but these two are sounding a bit more convoluted. Would you mind having a think about how'd like to see this matching work. I am a little worried about overcomplicating this module, but I think the Specified Branch Parent might be an OK option - what would best fit into your workflow / requirements?

Well if that is acceptable in some cases then I could probably make it possible to limit edit access to more than one branch - would just need to disable the visibility restriction to that use case. I'll take a look sometime in the next couple of days to see what I can do.