WillMorris

Thanks, I did see that. It might be a better fit in this situation. I'm a little hesitant to use too many custom modules starting out (third-party or my own). In previous systems I've used, relying on too many external modules can quickly make it difficult to upgrade. You end up having to wait until all modules are made compatible, either by you or someone else. I've found it's better to try and max out the stock options first.

Good to know about the module system. Still trying to get a feel for when to use the stock admin tools and when to create a custom module. One problem I've encountered with other systems is when you rely on too many custom modules, upgrading becomes difficult, especially if the modules come from 3rd party sources.

Thanks for the help. I realized after the fact that it was probably too broad. Just wasn't sure how to start breaking it down. I've had too many experiences in other systems where I spent time trying to do something and finally realized it wasn't possible without massive workarounds.

I've worked through this a bit. The solution I have so far is to create wrapper page template to use within sub-sites. The wrapper template has a page field that refers to the page on the main site containing the content that needs to be pulled in and kept synchronized. The sub-site admins can then choose whether to show, hide, or reorder these wrapper-based pages. This will work as long as the original page doesn't get deleted. If that happens, I need to figure out a way to find and delete all the wrapper templates using that page as well. It looks like it would be possible to do through the API, but not the stock admin tools. Also, there's no way to automatically add new pages with this structure. Would also need to be a custom module, correct?

That's great. Right now I'm building a simple events calendar and want to allow people to enter an event's time in 15 minute increments via a dropdown menu. Something like... Choose start time: <1:00> <1:15> <1:30> <1:45> etc... In this instance you would put a "times" section under your tools section and create a page for each time you want to use in the dropdown, correct?

I'm trying to see if PW is a good fit for our project. It looks like it is, but I'm not quite sure the best way to structure and build it out. Looking for some input on best practices for setting up a system of sites in PW. Right now, we have a main site with CMS-driven content here: http://ebird.org/content/ The content follows this kind of structure: Home * News ** News Item 1 ** News Item 2 ** News Item 3 * About / Help ** Help Item 1 ** Help Item 2 ** Help Item 3 We also have sub-sites that are navigationally and structurally the same, but have different logos and sometimes different content. Home * News ** News Item 4 ** News Item 5 ** News Item 6 * About / Help ** Help Item 1 ** Help Item 2 ** Help Item 3 ** Help Item 4 Example: http://ebird.org/content/ak/ With our current CMS, when we create one of these new sub-sites, we copy the existing main site pages into a new folder, and the sub-site admins only have access to that folder. For instance, only the AK admin only has access to the /ak folder. The nice part about this setup is sub-site admins are free to add, edit, and delete pages as they see fit within their folder. They never see any of the other sub-sites or main site content. The problem with this setup is most of the content stays the same between the main site and sub-site. It quickly gets out of sync, especially help/tutorial content that pertains to using the web app. We want to see if we can set up Processwire to organize content with the following permissions: Type 1 * Written by main-site staff * Show on main-site only Type 2 * Written by main-site staff * Show on main-site and sub-site * Not editable by sub-site * Changes from main-site are reflected on sub-site * Sub-site does not have the option to hide content (always appears) Type 3 * Written by main-site staff * Show on main-site and sub-site * Not editable by sub-site * Changes from main-site are reflected on sub-site * Sub-site has the option to hide content * When main-site creates content it is initially hidden on sub-site Type 4 * Written by sub-site staff * Show on sub-site only What is the best way to structure this in PW? Is this possible within the stock PW admin screens or will parts need to be done with our own custom screens accessing the PW API? If so, how would you go about breaking it up? Thanks.

Just a suggestion -- it would be good to add this to your tutorials list. It's an important part of what a lot of people are going to want to build. Took me a long time to find the relevant posts in the forums. Your reasoning and solutions are great, just difficult to find and time consuming to sift through the threads.

Just an FYI: readme.txt and copyright.txt still say 2.1.

We're evaluating Processwire to see if it will work for our site. One of the major requirements is being able to maintain a large taxonomy . You can see our current example here: http://neotropical.birds.cornell.edu/portal/species/tree We need to be able to maintain a set of terms with key values and associated metadata (e.g. common name, scientific name, alternate name, etc.) and then associate content with those terms. Does Processwire allow us to create and maintain a taxonomy of this size? What are the upper performance limits? Thanks.