Nico Knoll

Yeah, I meant all of the modules (like Process modules or Markup modules).

What about module configuration? Is it exported/imported, too?

There is a roadmap which is open for additions.

Have you checked your file permissions? Try to give "assets" 755 or 777 (<- only for testing)

Error 500 is normally a .htaccess error. Take a look at this troubleshooting guide: http://processwire.com/docs/tutorials/troubleshooting-guide . If it shouldn't work please come back here

Have you tried updating it before uninstall? Because I made some changes in the install/uninstall routine recently.

Could you try deactivating the CKEDitor (jst got to setup->fields->body and change the textarea type to simple "textarea"). It maybe an error between the new version of CKEditor and my module.

Looks really really helpful!

Fun fact: This is the pub

I won't tell to much but I'm currently working on a theme module anyway. Website is already kind of ready: http://processthemes.com/ But I think we all should agree on at least one thing: ProcessWire should never integrate a real theme engine in it's core. never.

I think all that is needed for a theme system is a module. Combined with this default site profile.

We should keep the core together and don't have two independent versions. But that's what I like about the way I explained before. Having one default site profile containing the most important fields which you can build themes for and a clean one for developers.

This should be possible in cPanel. You should be able to choose which domain should use which folder.

@jeffro: Great that you joined this conversation over here! As far as I can see one of your main concerns is that ProcessWire doesn't offer ready-to-go themes. That's right and I think one of the points why processwire still is in the developer niche. But if you understood the ProcessWire concept (create fields, build a custom template/form and add it to pages) you should realize that it is probably not possible to create switchable themes for ProcessWire. It's like using WordPress with ACF and trying to find a theme for it which works out of the box with every custom ACF field. Our approach was to add a thing called "Site Install Profiles" which is a compilation of the template files, the needed modules and the needed fields and backend configuration. My suggestion was to offer like three default "Site Profiles": Demo Profile The Demo could include a guided tour through the CMS. Or we could build a "tutorial module" which could be in the /site/modules/ folder and would be deleted after the tour. Not sure on this point. Like the name said this would on the one hand a module do demonstrate how you build a template for designers / developers and on the other hand an template for presenting how Processwire works to your clients (with the backend tutorial stuff). Starter Profile I would rename the "default" profile to "starter". It should include all the fields an average user would use (like title, headline, body, images, files, ...) and should be the main profile which is included in your default installation. This one is a ready to go solution. This "starter profile" would be the profile we could design Themes for and stuff like that. So like I said a ready-to-go profile for the average user who don't need customized stuff. This would be the profile for my mother Clean/Air Profile The third profile should be for advanced users who like to set up their own fields and templates. Kind of how Soma's blank profile is. It would be shipped without these amount of templates and demo pages.

@marcus: +1. Maybe something like this could be added to the "Finished install" screen

Moved it

Take a look in the Troubleshooting Guide: http://processwire.com/docs/tutorials/troubleshooting-guide/page3

Isn't this a "pub" topic?

Hmm, I'll try to reconstruct it

Yeah, probably it's exact what you need. But I'm not sure how specific you can choose which pages should be exported...

I'm going to require WireMailsMTP anyway and will explain how to add mandrill SMTP to it. So my newsletter module will finally have a solid sending base. Better then php mail() and getting blocked as a spammer. @horst:I still have our conversation about this in my head I even saw the "bulk" mail option in your module which is great for this

Is bcc already implemented? Going to recode my Newsletter module and would need this functionality.

Then you need two loops inside: <?php foreach($page->nuoma as $field) { echo '<div class="small-12 columns large-6 columns bobkat-nuoma">'; foreach($field->big_img as $big_img) { echo '<a class="fancybox" rel="gallery1" href="'.$big_img->url.'">'; } foreach($field->small_img as $small_img) { echo '<img src="' .$small_img->url. '" alt=""></a>'; } echo '<h2>'.$field->bobkat_name .'</h2>'; echo $field->body; echo '<span>'.$field->price.'</span>'; echo '</div>'; } ?>

The image field is in your repeater so try this: <?php foreach($page->nuoma as $field) { echo '<div class="small-12 columns large-6 columns bobkat-nuoma">'; echo '<a class="fancybox" rel="gallery1" href="'.$field->big_img->eq($i)->url.'">'; echo '<img src="' .$field->small_img->first()->url. '" alt=""></a>'; echo '<h2>'.$field->bobkat_name .'</h2>'; echo $field->body; echo '<span>'.$field->price.'</span>'; echo '</div>'; } ?> This will show the first image of every repeater item. If you want to show every image from every repeater item you just have to add a second foreach inside the first foreach like: foreach($field->small_img as $image) {}

Well in case of ProcessDiagnostics we're using $this->modules->get('myModule') https://github.com/netcarver/PW-ProcessDiagnostics/blob/master/ProcessDiagnostics.module#L75-L83