Gabe

Thanks SO much sforsman! I really appreciate you taking the time to put this together. The process module definitely is the quick and easy way to get this done. I'm going to play around with the module though just to get a better grasp on how modules work. Thanks again to everyone help with this!

Thanks, I'm definitely willing (and excited) to learn!

There are probably others here that can probably give you much more concise advice on how to handle / correct that error, but my best suggestion would be to rename your current 'wire' folder to something like 'wire_old'. Then, upload the wire folder from 2.5.4 along with the index.php and .htaccess files. If that is what you've already done, hopefully someone else here can provide some more suggestions.

I think autoloads and hooks might be getting a bit over my head at the moment. I have a lot more to learn about PW. I might have to stick with static fields for the moment and have the client contact me to change them as needed. If anyone else has any suggestions though, I'd be happy to give them a try!

Thanks kongondo, To clarify, if the user selected the 'Towing Capacity' pagefield option for 'Car A', the value set would be for that page (Car A). If they were editing 'Car B' and selected the 'Towing Capacity' option, the value they set would be for 'Car B'. Hope that makes sense.... I've worked with dependencies a bit, but I'm certainly no expert in them. What I would like to do would look exactly like what is being done with the 'Villa Toggles' at 1:06 in the video (http://youtu.be/hqLs9YNYKMM?t=1m6s). However, the options (Villa Toggles) would be a pagefield and the individual options (Air Conditioning, Beachfront, Children Welcome, etc.) would be pages. Problem is, each time the end user adds or removes an option (page), I would have to manually create/remove a field to hold the value for that option and create/remove the dependency. Maybe I'm over-thinking this and giving the end user too much control (for reference, my other post kongondo mentioned is https://processwire.com/talk/topic/7892-situation-where-i-need-set-a-value-for-a-page-selected-from-a-pagefield/ )

You're thoughts on this come very close to a problem I've recently run into Joss. When using pages to create a set of options to be displayed on another page via the pagefield, sometimes there is the need to set a value for each selected option (page). A simple example would be a site selling cars. You might have each car for sale as a page like this: Cars -- Car A -- Car B -- Car C You would have fields in the car template like Price, Mileage, Color - things that apply to all cars. However, you might also have options that only apply to some cars like Towing Capacity, Cargo Area Volume, Max Payload, etc. You could add these options as fields and not display them if no value is set, but it would be nice to have each option be a page and display it on the car template via a pagefield. That makes it easy for the end user to add / remove these kind of options in the future. However, a value needs to be set when the option is selected from the pagefield, and there seems to be no way to do this. Maybe I'm completely missing something and there is a better way to go about the above scenario that someone more experienced can lend some advice on? Thanks!

Thanks gebeer, onjegolders & adrian. I've tried using the PageTable field. Initially I thought that would work, but that adds pages and that's not really what I need to do. I already have the pages I need. I just need to be able to assign a value to them when they are selected from a pagefield on a different page. I guess I'm not really using the pages as a 'page', but as a way to display a set of options on several other pages via a pagefield. If one of those options (pages) is selected, then a value needs to be set for it. Hope that makes sense. @gebeer - the discussion you linked to does seems related. I'll try to contribute to that.

@Horst - Thanks for the welcome. The forums have been invaluable! That makes sense Ryan. I've just been playing with PageTables and I think I have somewhat of a grasp on them now. I'll definitely give that a try. Thanks!

This topic helped me a lot when I was upgrading: https://processwire.com/talk/topic/7488-upgrading-25-dev-versions/?hl=%2Bupgrade+%2Bdev I've upgraded a couple of time with no problems and have several modules installed. However, I installed them to /site/modules not /wire/modules. I believe that is where they are supposed to go so they don't get overwritten with upgrades.

Hi, I'm fairly new to PW, but have learned a lot from this forum and working with PW over the last few weeks. I've run into what seems to be a simple problem, but can't seem to find a workable solution. Sorry if the title isn't very descriptive, I'm not sure how to describe this problem. I'm working on a site for a company that manufactures and installs countertops. They have various materials available for countertops. Each one of the materials is a page like this: Materials -- Granite -- Quartz -- Laminate On each of the material pages there are various fields for descriptions, sink-mount options (page field), etc... All of that works great and it makes it very easy for the client to add or remove materials in the future. Here is where the problem comes in. In addition to the description and sink-mount fields, each material needs to have a set of fields to describe its characteristics and that set of fields must be the same for each material. These would be things like Durability, Ease of Maintenance, Chip Resistance, Repairability, etc... Each characteristic would have a value of 1 - 100. Of course, my first thought is to just create these fields and add them to the appropriate template. However, the client would like to be able to add/remove/edit characteristics just like they can with materials, so pages seem like the ideal solution. But then... how do I make those all of those characteristic pages show up on the materials pages AND allow a value to be set for them... That doesn't seem to be possible. I've tried to think through every possible solution - repeater field, page table, repeater field with a page field, repeater field with a page table. Nothing seems to solve this problem. I feel like there is probably is really simple solution I'm overlooking or I've approached this in completely the wrong way. Thanks for any suggestions!

It seems that field permissions are not working on fields in repeaters. I'm quite new to processwire, so I could be missing something, but I've been able to get field permissions to work as expected everywhere else. Possibly a bug? Thanks!