wheelmaker24

I think the fields themselves don't need to be updated – the standard behaviour should be fine. I just meant that fields you've added to the original template are automatically added to the "child" template as well.

What about enhancing the "Add field" select in the template editing window to not only feature fields but also existing templates? When choosing a template as a field, all of its fields are added to the new template and updated in case the original template is edited.

Hey guys, I'm trying to build a submit form with the ProcessWire API. After the form is submitted its data should be saved into different pages. I've followed Soma's great tutorial and wanted to improve it for my use case: Instead of adding every field manually to the form I already managed to automatically read out the fields that belong to a specific template like this: // Build form $form = $modules->get("InputfieldForm"); $form->action = "./"; $form->method = "post"; $form->attr("id+name",'$page->name'); // Build fieldset $fieldset = $modules->get('InputfieldFieldset'); $fieldset->label = 'Personal Data'; // Read out template fields and append them to the fieldset $registration = $templates->get("registration"); foreach ( $registration->fields as $field ) { $field = $field->getInputfield($page); $fieldset->append($field); } $form->append($fieldset); // more fieldsets... // Submit $submit = $modules->get("InputfieldSubmit"); $submit->attr("value","Anmelden"); $submit->attr("id+name","submit"); $form->append($submit); This seems to work great – with just one little restriction: Instead of the global field labels I would love to get the template specific settings for each field (defined within the template). E.g. in this template I'm using a body-Field not labeled as "Body" but as "Description". Same would be great for things like field's columnWidth, required properties and Co. Is this possible? Thanks a lot for your help! Nik

Hi there, the ProcessWire page layout functions perfectly for something like a hierarchical post structure, e.g.: - Post 1 - - Answer 1 - - Answer 2 - Post 3 - - Answer 1 I think from an API point of view this is the best solution. But what if the post type itself could make use for children? For example if the post type was a simple poll: - Poll 1 - - Poll Option 1 - - Poll Option 2 - - Poll Option 3 It's getting confusing when you've got polls that can be answered. Is there any better solution than throwing together poll options and post answers? A similar question: I would love to have a news page, whose children are the news items. Adding something like poll items to the news page would of course be possible but IMO a bit "messy": - News Page - - News Item 1 - - Poll Item 1 - - News Item 2 - - ... Is it? Is it not? I'm not sure … How would you design the page structure? Thanks!

Hi again, in this case we would need a user-based counter. I just realized that I therefore only need to create a page reference field named "likes" that refers to the user pages (multi-select, not editable via the editor). Great!

Wow, thanks a lot for your responses so far! I've dropped Tom Reno a note as I think the Shibboleth integration would work quite smooth (concerning auto login capabilities and so on). Although I will definitely have a look at the LDAP module. I pretty much like the idea being able to build nearly everything with the core features of ProcessWire. On last question: We might be able to integrate the company's social features (there is a Facebook like application which can be partially included). But actually they are not very quick in adapting it to different environments and have performance problems. So I'm thinking about using the ProcessWire comment module by Ryan instead. This of course would make the Shibboleth integration necessary. Is there anything like a "like module" as well? We would love to use it for the news posts on our starting page. So far the ProcessWire community seems to be the most active community I've met! I pretty much appreciate your efforts and would love to contribute in anyway

Hello there, I've already realized many projects with ProcessWire and would love to use it for a bigger project now. Maybe you can help and allay my doubts Enterprise Single Sign-On? We are currently using Microsoft SharePoint (2003…) as a publishing tool for our intranet web pages. This of course is no good solution concerning responsive design, flexibility and scalability. Because we are talking of a big company (about 9000 employees) it is important to protect the ProcessWire installation with an Enterprise Single Sign On (SSO). It seems like Shibboleth is a good solution to handle the communication between the Microsoft Server from the company and the Linux Apache for the intranet web page. Has anyone already used ProcessWire in an environment like this? It would be great to use the employees IDs and hand them viewing / editing rights for single pages. Permission Management for 9k users? Of course most of the employees should only get viewing rights. But it would be great being able to give editing restrictions for specific pages. As I understand this is something ProcessWire does not support with its core features – even though there are modules for this particular case. The question is: Is it responsible to build a big system based on many modules in consideration of future upgrading, scalability and co.? Looking forward to your comments on this Happy coding! wheelmaker24