Leaderboard

Hijacking this post somewhat but have to say Apeisa that this is the sort of feedback which makes people want to commit to a piece of software! The community here seems very strong and thoughtful and not at all arrogant. I have to say it bears some resemblance to the support from EE, from which I'm coming from and for an open-source product I think that's very impressive. I was put off another similar open-source system because the founder was anything but helpful or polite or forthcoming with help. The documentation here is incredibly thorough and the people seem 'nice' (amazing how much of a difference that makes). Anyway back to the post, am also coming from EE so anything that can help me get my head around the differences in the way things works is very welcome!

Hi digitex, I am on v 2.2.0.1 and I just tried to emulate what you did, I created four pages, two I created and didn't even click publish (just left them as titles) and two I created, added content, saved, edited to untick-published. Then I left them a few minutes to make tea, then I returned and published all four. No problem. I have no idea if it's more likely to be your version not being as late as mine or something and I am sure Ryan/others more knowledgeable will comment more.

My suspicions were correct, there's no need to do anything crazy. The API handles it fine - $page->images->add() was what I was looking for. Part of the frustration was that I mislabeled the switch case, it should have been 'FieldtypeImage' as opposed to 'ImageFieldtype'. Now if I could only control the name of the phpRANDOM.tmp filename being created, but that's a different matter. For anyone looking for a solution, here's an updated snippet: foreach($page->template->fields as $template_field){ $field_name = $template_field->name; $field_class = $template_field->type->className; $update_value = $this->input->post($field_name); switch($field_class){ case 'TitleFieldtype': case 'TextareaFieldtype': $page->{$field_name} = $update_value; break; case 'FieldtypeImage': if (array_key_exists($field_name,$_FILES)){ $img_path = $_FILES[$field_name]['tmp_name']; $img_name = $_FILES[$field_name]['name']; // $_FILES array singular vs. multiple // normalize by converting single to array prior to looping. // http://php.net/manual/en/reserved.variables.files.php if (!(is_array($img_path))){ $img_path = array($img_path); $img_name = array($img_name); } for($i=0; $i < count($img_path); $i++){ $page->images->add($img_path[$i]); // TODO, change image name from phpXYZ.tmp } } break; ... } ... }

I totally agree it would be great to have a modal dialog that then creates pages and all their fields. But there is a rather large difference in development time between that and what I've added. I added what I could afford to in the short term. Down the road, I'm sure we'll expand the capability to take the modal route when dealing with creating pages that have more than just a title field. But since I could add the title-only page additions in the short term, I figured that's a good place to start. Even when we expand with the modal dialog, I do want to keep the current method for when the template has just a title field. The reason is that this is a very convenient way to create large selects. Lets say you need a "country" select -- you can paste all 196 countries into that field and create all your select options in one shot.

WillMorris, Very likely ProcessWire will be a good fit for your need. That bird site would be an excellent example of where ProcessWire does well. When it comes time to build your "taxonomy" post the full scenario here and we'll guide you through the best approach. ProcessWire tends to be very flexible in this regard, and that means that some ways to approach something are better than another. For instance, it would be possible to build this taxonomy in a way that's not very efficient, and likewise possible to build it in a way that's highly efficient. When it comes to building for the large scale, you have to be more careful with approach in order to ensure you aren't accidentally loading 6k pages in 1 API call (as Adam mentioned). Taxonomy is such an unfortunate term. It has a strong resemblance to the term "Taxidermy", which in English means the "art" of creating life-like stuffed animals out of dead animals. Not a mental picture I like. This is why you don't see me use the term taxonomy very often.

@apeisa, great question, I'm definitely interested to hear more about this too. @Diogo, that sounds like exactly the same way I would read documentation too. That's interesting to hear about it being too-personal. I had never made a video of this sort before so didn't really know what I was doing (and still don't) but am learning. This is good feedback and perhaps i should try another room next time. The room I work in (and did the video in) is a large loft-type room with wood floors and it tends to echo a lot in here when talking. So I briefly considered recording the narration in the bathroom for less echo. Glad I didn't do that–that would have definitely been too personal. ;D @formmailer do you recall what words you were searching for? I've not really been sure what to target from an SEO standpoint. But as we do major upgrades to the site in the near future, we'll probably want to start considering more strongly the words that people search for to find us.