Martijn Geerts

@horst, I do understand what Ryan said, wise words, and I agree. ( aside, more likely to expect an interview with Ryan Trash over there ) The kickstarter thing is in essence not about earning money. It's about sharing ideas, make plans and work it out, together. Let the kickstarter feel like they're part of the community an let them help to create useful modules/apps. In the end the community will benefit from it.

I don't want to limit the audience. The social aspect is important. But if someone pays, he should deserve something extra. I love to see the source will be open after 3 months or so.

Welcome, Read some documentation here & you're good to go. Not to difficult from what I read from your post. Search the forum, all scripts you need are already written and posted.

kickstarter There are several developers here that contribute a lot, working for fun and sharing knowledge giving us wonderful modules. But next to the respect they get, it would be nice we pay for the Cola & Pizza's they need while programming. ( Can hungry programmers code to ? ) For me as individual I won't/can't pay a decent price for good software, but with 10 members things change. Say: If an developer needs $750,- before starting the write. (I'ts only €56,-- per person, not reached, money back ) Then: Every person who paid, can download the finished module. After 3 months: The module becomes normal opensource, available for everyone. Maybe Ryan can choose some privileged developers that are capable of building quality modules. What do you think ?

But I thought about http://www.kickstarter.com/ for processwire modules. Maybe Ryan can choose some privileged developers that are capable of building quality modules. If There's enough interest (money wise) a module can be build. I will start a new Topic !

An other guess: $student = $pages->get((int) $student); $student->setOutputFormatting(false); $new_s->setOutputFormatting(false); $new_s->student_feedback = $student; $new_s->save();

$current_s = $pages->get("template=student, student_feedback=$page"); <-- here student_feedback it is a page object $new_s->set("student_feedback", $student); <-- and here it is a string Maybe this matters....

(I mean: am I the only one having this?) Having no problems with images in 2.3.3 (with additions from @horst)

@horst, tnx for the image options (now in dev branch), sharpening look more then great !

Have you enabled template caching ? Something tells me it works till 999.. Make it stop at 999 then. Most likely people are not interested in the 999 page or 100. I think it's better if result are that high to tell the user to narrow the search. (Youtube api is doing the same, stops at 999)

@Hani, I used this module in 2 of my lasts projects I I must say I love it. TNX for creating!

@arjan, I really don't know if it is a "fix". The field I use is almost completely stripped. I only allow, <strong> <em> and <link> ( the CKEditor one, not the pw ) But so far, no issue anymore.

I think you're thinking to complex. For slideshows (just to have one) you can put those in your homepage. Or if you want to slide products, upload those images on an actual product page. Or create a settings page, etc., etc.

What I ment, There's no CMS better/easier in assets management then ProcessWire. You can make it your self very hard to build sliders without taking the PW way. ps, you don't need a dropdown. $imagePages = $pages->find("template=basic-page, slideimages.count>3, limit=3"); <- assumed that your image field is called slideimages foreach($imagePages as $p) { echo "<ul>"; foreach($p->slideimages as $image) { echo "<li><img src='{$image->url}'></li>"; } echo "</ul>"; }

That has indeed nothing to do with proccesswire. Use php or something to make some magic. ( i don't know why you don't like the easier pw way)

@Willy: Just reminds me.

You're more then welcome.

@adamspruijt Have the same issue, but when I ad a link to an external js file. ( Custom Editor JS Styles Set ) Then the issue is gone, even if the file is empty. (weird)

@MrED, nope Welcome to PW.

Thank you Apeisa & Ryan. More then awsome.

The web is full of good ProcessWire tutorials. But for the basics you need just a bit PHP. ( not more difficult then a template language ) As a by product, PHP throws good errors.

With FastCGI I don't have good experience. But maybe thats just me.

I don't know if I understand you correctly. I think you can add HTML by adding an InputfieldMarkup to your template with the api (I never have tried it and not possible through the admin) If you want to have instructions or whatsoever (is that a good word?) You can use Markup style links [instructions](http://lmgtfy.com/?q=instructions) in your descriptions.

If a customer want a Drupal or a Wordpress site, it's up to them. We try to convince them for ProcessWire. If they don't want ProcessWire we help him to find an other company who delivers Wordpress or Drupal. Building a site in Drupal & Wordpress is 1 but maintain it is a whole other story. It would take me ages to find out how those structures/template-languages work & i won't remember it after a year or so. Customers are better of with an external company making those Wordpress/Drupal sites. It's not unthinkable that Wordpress or Drupal looses interest for the big public. Maybe some other player will show up on the market or a huge security hog will be all over the news. Popularity can drop very quickly and then you're sitting there with your template-tag knowhow. Lots of time spend in ProcessWire is PHP time. PHP will not out of the picture soon and if it does, you learned a proper scripting language, not a template language. I can ask a PHP developer to build a site using PW, give him the cheatsheet, and let him start right away. ( That's unthinkable with the other 2 ) I want to gain valuable knowledge while working having fun, ProcessWire let me do this.

Say you have a max of 20 images per page, I would say take a repeater with a image field allowing 1 image and an url field. (what do I say repeater ) If there are more images, I should make a template with an url field and a image field allowing 1 image. structure it like: [ images ] <- page used as folder \ [ image ] <- page with 1 image & url field. [ image ] <- page with 1 image & url field. [ image ] <- page with 1 image & url field. [ image ] <- etc. [ image ] <- You can insert other fields to, those fields can be used as meta data. [ image ] <- Say you add a select dropdown with "brands", then you can "tag" your photo's: Select: Microsoft or Google (if they are in the select) then you can query your photo's on those tags to.