apeisa

Django does it well too: syncing models from code to database. https://docs.djangoproject.com/en/dev/topics/db/models/

Single page designs are hard in ProcessWire. You either go with RTE-solution (like TinyMCE templates etc) or then with pages/repeaters solution. Neither of those solutions is close to ideal. I think currently best solution can be found in newsletter-systems like MailChimp and MadMimi. Drag and drop different kind of components (like header, images, images & text etc) to build your content. There is of course obvious drawbacks in that kind of content building: you are mixing content and styling together. Sometimes that doesn't matter though (mostly small marketing sites or campaign pages etc).

Usage is dead simple: <?php // any check where you see if user has posted form and you start processing the form if ($input->post) { $username = $sanitizer->username($input->post->username); $u = $users->get("name=$username"); // Of course you could get the user by email or any other information $u->of(false); $u->send_password = 1; // send_password = whatever you have named your new field $u->save(); }

Sorry, not sure I understand what you mean?

Template caching and ProCache are pretty similar. Procache is more effective, since it works on .htaccess rewrites. Cached pageviews doesn't even touch PHP or MySQL, just pure HTML served by Apache directly. Template caching makes one simple check (PHP & MySQL) to see whether to serve cached or noncached content. Some simple speed comparison is available here: http://processwire.com/api/modules/procache/

Nope, it is enough to set it on home-template, it will be inherited from there (unless you restrict it on some other template).

Welcome to the forums Guy! There isn't assets manager in pw (although Soma is building one: http://processwire.com/talk/topic/3219-images-manager-alpha/). PW way is to attach images to pages and reference to those pages instead. So one way to solve your need might be to have template called "image", which would have single image field and other metadata related to image (like tags and description). Then you would reference to those image-pages instead of image directly. This would definitely keep things DRY, but it might not be the best solution in usability wise. I haven't yet used Soma's images manager, but it might offer even better UI here. If I have understood it correctly, it works just about the same under the hood.

I would go with ProCache and some MarkupCache here and there (forms with dynamic options, categories lists etc). And of course enough horsepower on server.

There is not much to see. It adds dropdown for rating in comments form (you can define those selections through inputfield settings).

It's render($field), not render([ ]). So jmartsch example is little off.

And if Diogo's solution gives you too much pages (admin pages, users, roles etc), then try these: $pages->find("include=hidden"); // or $pages->find();

Yep, I think $page->save() is what is missing. Soma, yep, $page->product_comments->averageRating comes from my customized module.

Your browser has cache.

Try wire('page'). (On mobile)

I have made that mistake several times myself

He mentioned 5.2.17 which is greater than 5.2.4

I'd say that if you know for sure that there won't be more than is usable considering the repeaters UI. My "limit" would be around 20-30 items. Technically it scales for more (especially with simple items).

Looks and reads great on mobile! Also - is this first blog with more than one pw related posts? Great posts Teppo, enjoyed reading them!

Welcome to the forums. Those problems with XP computer seems to be network problems. Does all other sites work ok from that computer? Also one possible solution (probably not in this case but might be worth trying) is to modify /site/config.php and set $config->sessionFingerprint = false; This will keep you logged in even if you have dynamic IP address.

I would love to see more abstracted way to handle payments. Payment Methods in shopping cart are nice, but too tied to shopping cart. I actually build one abstract class for payments few months back (and implemented one payment method using that class), but didn't get time to finish that. It's not that simple to find good balance on what to abstract, since there are different kind of methods for payments (processors where all the payment information are collected on payment processors site and then ones where processor just process the payment on background - and anything between).

Looks great on mobile. I would probably hide the content bg on mobile, it shows so little that it looks strange. Site loaded very fast for me!

For content you should not use this method, but multilang fields instead. On front end tokens are fine for some mostly static stuff like button labels ie. "search" etc.

For some reason your field_value is regular php array instead of PageArray or Page object. Ah, you are getting that directly from post, of course it cannot be page or pagearray then.

That sounds strange. Try changing this line: https://github.com/apeisa/ProcessRedirects/blob/master/ProcessRedirects.module#L94 from InputfieldUrl to InputfieldText.

It must come from your template files. Try grepping your /site/ folder for "smart-devices".