Leaderboard

Hi, Here's my first site using Processwire: Hoof is a Graphic Design studio in Melbourne I run with 2 friends/colleagues. http://www.hoof.net.au/ I've had a lot of assistance with this from everyone in the forum answering my questions, thanks so much for all the help! If you are reading Diogo - I have the PHP book you recommended its great, there's a few lightbulb moments there. I'll be able to pick apart and improve my templates a bit now. Its been said many times already… processwire is a pleasure to use. I'm looking forward to learning a lot more. Regards, Alex

Below, I'll write how you can move your site from Drupal to ProcessWire. It's quite simple. In Drupal you will need: - Views Module, - Views Data Export Module, - Views UI Module (integrated with Views), - Chaos tools Module - required by Views. Install these modules and switch them on. In ProcessWire you need only: - CSV Page Import Process (Import Pages from CSV). Install this module. When you are ready, you have to create a new View (select: "Create a page") in Drupal with all fields which you want to export. Then, add "Data export" subpage and make sure, that format is CSV file. It's a good idea, to use Pager when you have lot of nodes (pages). You have to setup an url to download your CSV files. When you are ready - download your data. Next step: In ProcessWire, you have to prepare a template with your fields. When that's finished, you can import your data from CSV files using "CSV Page Import". That's all. If you have any questions, write them below. I can also write complete scenario for my website (if there will be anyone interested in that).

I totally agree, PW is mind blowing. I've used WordPress and SilverStripe before and they were a mess. I like the simplicity that PW offers to designers - I can design a site in Photoshop, make a pure XHTML/CSS templates, think little about API functions and voila, a site is born. I haven't used full PW potential yet, but so far every site I've made came out exactly as I planned. So thanks again, Ryan

When you are dealing with API functions, you aren't dealing with markup. You are only dealing with markup when you create and output it yourself. I think this may be what you are looking for? // .. starting in the middle of your example: foreach($children as $child) { $class = $child->id == $page->rootParent->id ? " class='on'" : ''; echo "<li><a$class href='{$child->url}'>"; if($child->id == $homepage->id) echo "<img src='your image file' />"; echo $child->title . "</a></li>"; }

I've never seen a .jpe image myself. I'm guessing it comes about when another system encounters a .jpeg, only supports 3 character extensions, and truncates it to .jpe ... like in the old MS DOS days.

I've never heard of oEmbed before, but it looks like it would be a good solution to make an easy fieldtype for videos. http://oembed.com/ There are also some alternatives based on it. http://noembed.com/ http://autoembed.com (this one looks nice, but it's only free for personal use)

Yep, that would be good solution. Other thing that people do is to have more deeper structure: /1/1001/image.jpg /1/1002/another_image.jpg ... /2/2001/filedump.zip /2/2002/image.gif ... /10/10201/file2.jpg /11/11390/fileX.zip ... /23/231021/file3.jpg ... /191/1912621/scalesforovermillionpages.jpg ... etc Changing file structure might be hard thing to do, but it would prevent scaling issues with pages where you host large amount of files and use pages as containers for them. Deeper folder structure combined with "folders created when first file uploaded" would be best solution, I think.

That would be great. But I think this is still little problematic. I think image fields should always return arrays, even if you only want to keep single image. That is because I think that is probably only place where tiny change in field settings ends up with errors. Perfect solution would of course be this (not sure if this is possible): $page->imagefield // returns array of images $page->imagefield->size(200,200) // returns first image in 200x200 size So if you don't loop or specifically say that you want other than first image, methods will always take first image. This way images would just work.

Hi Ryan Hmm - as a Postgres devotee perhaps I could mention that we've had full text indexing since the early Triassic: http://www.postgresq...arch-intro.html Much more sophisticated that MyIsam too, with lexical parsing to handle plurals etc, stopwords, synonym dictionaries and highly optimised indexing. And of course you get all the other Postgres goodies such as intelligent engineering, bomb-proof data integrity (haven't lost a byte of data in 10 years), and a sensible licence. <rant>I'm having to use MySQL for a current project, and I've been dismayed by what I've found. This is the 21st century, and they are openly admitting that their query parser is so dumb that they still haven't figured out a way to offer functioning sub-queries! They're expected "some time soon". I'm sure your clients would appreciate the option of using a database built by a community who would never dream of knowingly releasing an upgrade with 300 known crashing and critical bugs: http://monty-says.bl...1-released.html :- </rant>