Leaderboard

Hi Everyone! I'm glad to show you guys my first Processwire project: http://www.ihera.com.br/ It's a simple yet tailor made website I did for a clinic specialized in women health in Brazil. We've designed/coded several templates for the backend, used the Skeleton CSS Framework (http://www.getskeleton.com/) to help making it responsive adn some some minor javascript to some pages - and of course, made it very SEO friendly with custom titles and meta description for each page. I'd like to thank Ryan again for this amazing tool! I've never done such a tailor made CMS (Wordpress, Joomla, Drupal, CMS - I've been there) that's so easy to use that my client didn't need more than 10 minutes of "training" and is super happy about the outcome and the ease of maintaining it. Simple, amazing and beautiful. Best of all: the code is clean and since you code the templates from scratch, you know exactly what is what and speed and great clean markup is an obvious result of it... Let me know what you think! Tks a lot! jw

It's my first post in this area and this barely validates as a "showcase case", but: I've finally managed to update my own Web presence, resulting in flamingruby.com. It's primarily a blog, but some of my projects are on display there too. This site has actually been up for months already -- wasn't going to post it here, but thought it'd be nice to prove that I've actually built something with PW after all.. Being responsive is fairly standard stuff these days. In this case no frameworks were involved, though; it's all hand-made, built from mobile first perspective and based on content alone, instead of predefined breakpoints. Some details I'm still not happy about, so it'll probably get tweaked every now and then, but at the moment things are pretty much in a stable state. Since it's a personal project, I've been slowly adding small tricks here and there, none of which really count as anything "special." One addition made just today, mostly as a proof-of-concept, is a combination of a simple module and new subdomain (static.flamingruby.com) to automatically serve assets from (at least in theory) cookie-free location. This is described in more detail here. For home page I built an importer module (with AngularJS GUI, which was actually quite fun) that periodically pulls content from various feeds.. a bit like what Nico did with his social timeline, but nowhere as cool as that. At the moment content is being pulled from GitHub (for which I had to put together MarkupLoadAtom) and Twitter (which kindly killed it's RSS support just in time, so I'm using rssitfor.me instead.. although that site interestingly spits out Atom and not RSS like one would expect.) That's just about it.

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).

You can also use "subfields" like template.name, template.id ... maybe not a good example but you get the idea, most or all that can be also used in selectors like created_users_id etc.

Short answer: if it has to scale without a known limit use pages. Let's say a log module which saves pages with user login info you use pages since this might scale up to a large number. If you are creating a slider/carousel with a couple slides you can use a repeater. Also if you have to use the API extensively you better use pages since you can use selectors or PageArray to sort and filter data.

The first one is more reusable. If for some reason you would want to render the posts on another page, or simply use a different array then children, you wouldn't be able to do it with the second option. But, if you do this: function renderBlogPosts(PageArray $items = $page->children) { You can call the function with renderBlogPosts() on the original page, but be able to pass a parameter on any other page: renderBlogPosts($pages->find("template=post"))

I like it! I personally prefer single-column layouts or maybe 1+sidebar for this sort of information, because my lazy brain tries to gain a sense of hierarchy really fast. But I think the color scheme is great and you're on the right track for a fun personal site-type logo. *ahem* I have at least three. I would write more but I'm afraid you'll realize I'm stealing all your secrets you'll steal all my secrets.

Have you tried adding "template" there? Works for me already. Doesn't look exactly like what you posted above, though, more like this: About us, template-a 3 | edit | view | new | move Our Board, template-b | edit | view | new | move (etc.)

Hello all, So I've been asking way too many stupid questions on forum to turn an idea into reality. I've finally launched a basic version of the drama booking website. Still many important things like Payment & sms gateway are remaining but that too will be added soon. Allow me to present you Ticketees.com (Credits: http://ticketees.com/humans.txt) It's been out & being tested and used by drama producers for almost a week now. We've got some very positive response. It wouldn't have been possible if I hadn't learnt so much from Ryan & ProcessWire's community and ofcourse, ProcessWire itself. I've very very thankful to each & everyone who made it possible. There's a long way to go, many many things are left to be done. I'd like you all to see and give me your honest feedback, good or bad, help me improve it. Thank you all once again.

I'll take that as a yes . Пожалуйста!

Russian is my native language. I understand each word in first message, but hardly understand the whole message. So Like from WillyC has made my day =)

Sorry for that -- for some reason I simply copied your original (non-working) selectors and didn't fix them for my examples..

I think I got it, lin 1009 of the php.ini is commented out: ;extension=php_openssl.dll I'm assuming, that line beginning with the ; means it's commented out. Was unaware of that commenting method, so here's a link to the parsing the INI file for php: http://php.net/manual/en/function.parse-ini-file.php Attempting to rerun then here in a few. thanks, again. [Hint: Don't forget to restart your xampp server, after making the php,ini file change, found at xampp/php/php.ini]

keep stink.away siphon do . be.happy yous should two.have siphon inmy country.when i was young.man .we poop in ground hole when you look.at dark hole.careful must u be dark ground hole.look back consumes you it will no flush no.siphon=stinkers no girlfriend cloud every thing impossble to see.light love siphon.you shuld flush take all.mush

anything with a happy ending?