owzim

You are right, my request might be beyond/off the scope of your module. Thank you for the other suggestions, will definitely check them out.

Hi Wanze, great module. Wouldn't it be great if in the creation tab, the input fields would reflect the chosen template? That way one could batch create page content with all the custom fields too. This however could get messy when it comes to Repeaters or FieldSetTabs. Perhaps one should be able to chose fields in a comma separated manner?

The simple PHP OR comparison solution is very common. The in_array solution is more flexible. The PW solution owns them all =)

I normally don't like page changes on scroll thingy sites, but this surely is a pleasant experience. The music is key in this wonderful presentation. edit: and the photos +1

Had closer look at grunt yesterday, might even be a better solution for my needs, and the community seems more vivid, development more rapid. Let's see ...

Ok, here we go again. After I tried to do the same thing, same behaviour, with a seemingly broken DB as a result. Here the exact steps: Created new repeater field after first creation process added title and body field set to global and autojoin after save, error [edit1] I was able to narrow it down to the global option, which caused the error. Saving everything else but global was fine. Perhaps installed modules interesting as well: Batcher Custom Page List jQuery Data Table Ajax Page Delete Pagination Markup (Core) Repeater (Core) Site Profile Exporter Thumbnails Wordpress like Shortcodes Modules Mananger [/edit1] [edit2] I was able to reproduce this error with a fresh PW installation installed Modules Repeater (Core) Modules Mananger It might be of interest that the field was named "sections" [/edit2] [edit3] I was able to reproduce this error with a fresh PW installation with only repeater module installed and nothing else. The field name "sections" was not relevant. MySQL 5.5.9 PHP 5.3.6 [/edit3] with the latest stable release of PW 2.3 As stated before, deleting cache and session files did not help. Don't know which additional details I could serve.

Deleted all session an cache files after the error, with no luck.

I was able to restore everything to a state with which I can work. I restored from TimeMachine to MAMP/db/mysql (dbfolder being the name of the db): dbfolder/ ibdata1 b_logfile0 b_logfile1 and switched to the lated dev-version of wire/ still don't know what caused the error.

I moved to the current dev version of PW because of the new $page->render(); options Everything worked fine. I created a repeater field with a title and a body, and after save this happened: Fatal error: Exception: Could not execute User::__construct() (in /path-to-pw/wire/core/Pages.php line 323) #0 /path-to-pw/wire/core/Pages.php(0): mysqli_result->fetch_object() #1 /path-to-pw/wire/core/PagesType.php(109): Pages->getById(Array, Object(Template), 29) #2 /path-to-pw/wire/core/Users.php(60): PagesType->get(40) #3 /path-to-pw/wire/core/Session.php(82): Users->getGuestUser() #4 /path-to-pw/wire/core/ProcessWire.php(138): Session->__construct() #5 /path-to-pw/wire/core/ProcessWire.php(45): ProcessWire->load(Object(Config)) #6 /path-to-pw/index.php(184): ProcessWire->__construct(Object(Config)) #7 {main} in /path-to-pw/index.php on line 215 This error message was shown because site is in debug mode ($config->debug = true; in /site/config.php). Error has been logged. since then I can't access neither the site nor the admin area, it always shows this error. I tried to recover the db via TimeMachine I copied over the needed files, then: Fatal error: Exception: Table 'dbname.modules' doesn't exist SELECT id, class, flags, data FROM modules ORDER BY class (in /path-to-pw/wire/core/Database.php line 118) #0 /path-to-pw/wire/core/Modules.php(167): Database->query('SELECT id, clas...') #1 /path-to-pw/wire/core/Modules.php(85): Modules->load('/path-to...') #2 /path-to-pw/wire/core/ProcessWire.php(99): Modules->__construct('/path-to...', '/path-to...') #3 /path-to-pw/wire/core/ProcessWire.php(45): ProcessWire->load(Object(Config)) #4 /path-to-pw/index.php(184): ProcessWire->__construct(Object(Config)) #5 {main} in /path-to-pw/index.php on line 215 This error message was shown because site is in debug mode ($config->debug = true; in /site/config.php). Error has been logged. I guess some schema was altered after the switch to the current dev branch? I somehow need to recover the installation or ... =(

Grunt.js seems too complicated for me, haven't got the hang of it yet. Though, it might be very powerful. I'll for now stick with Guard and might check out Grunt in a month or two =) And Grunt.js is not preprocessing, right? It's a build tool, so how would you use Grunt for compiling Sass, Less and CoffeeScript while developing?

Keep in mind that Guard is a command line tool, so if you haven't yet tried js/css preprocessors this might be overkill. CodeKit is great for getting started with that the easy way. And for Windows there is at least Scout (http://mhs.github.io/scout-app/) for Sass/Compass.

It would be great if imageSizerOptions like in $image->size() would be available as well: http://processwire.com/talk/topic/1531-image-crop-and-resize-wishes/?p=16560 $image->getThumb('thumbnail', $options); Might that be a feature in the future?

I just switched form CodeKit to Guard. I have more control over how things work, it’s cross platform and more team friendly, and it's free. Might be worth a look for you guys as well: "Guard is a command line tool to easily handle events on file system modifications." https://github.com/guard/guard Here's a nice intro by Jeffrey Way on Nettuts+ http://net.tutsplus.com/tutorials/tools-and-tips/guard-is-your-best-friend/ Cheers

I think we'd rather not fragment the PW knowledge base, right? I am not a g+ user so someone tell me what might be better there than here?

Poor kids might suffer from eye cancer soon.

Hope this is the right place for this. Following scenario: PW is running on my localhost: http://localhost/mysite when I insert an image into the textarea the path is like this: "/mysite/site/assets/files/1028/berlin.jpg" Then I changed to a development host name, which point to the same directory: http://mysite.dev Then all the inserted images do no work anymore, because obviously "/mysite/site/assets/" does not exists, it then should be "/site/assets/" Since the image path is written in this plain form into the db, this kind of inflexible. Any solution to this? Edit: It sure could be done easily with a .htacces rewrite: RewriteRule ^mysite/(.*) $1 but I'd consider this hacky then.

Sites in Internet Explorer 8 (and perhaps older) are totally unstyled when minify HTML is active. I don't know if it's an actual issue yet. Seems like the elements cannot be styled when there are no spaces at all.

I guess Soma was TELLING you to stick to english in an english forum! ;D

Of course $firstimage has no title because it's an image, but $selectedthumbs is the actual containing page so it has a title, my bad.

$selectedthumbs->title is not the page's title but the title of the image and by default images of the images field type don't have a title, so you should use the description as well.

The channel is not crowded enough! Let's take on #jquery =)

You are not doing anything with the image, you are just applying the size method without assigning it to anything. The method actually returns that thumbnail, so use it like that: <?php if ($page->children) { foreach($page->children as $selectedthumbs) { $firstimage = $selectedthumbs->selectedimages->first(); $thumb = $firstimage->size(100, 100); echo "<a href='{$selectedthumbs->url}'><img src='{$thumb->url}' alt='{$firstimage->description}'></a>"; } } ?>

either $firstimage->size(200, 100); or if you're using the Thumbnail Module $firstimage->getThumb('yourthumbnailname'); And here's a thourough explanation of everything around core images in PW: http://processwire.com/api/fieldtypes/images/

I agree that repeaters should have a limit option. And it would be great if one could set up a field, set all the options which are specific to that field and then on a template to template basis use that field (with its specific characteristics) multiple times and name it in the template creation process, but I guess that would throw over some of core mantras of PW.

I am frequent nettuts+ reader, so I read this article about PyroCMS and because I was looking for a better CMS solution than all the semi ideal ones out there, it got me interestend. But then I read the comment by Viktor: http://net.tutsplus.com/tutorials/php/whats-pyrocms/#comment-810229080 Never heard about PW before. I came here and instantly had the feeling this might be MY CMS ... so it happened.