Leaderboard

Almost. There's also an additional check to see if the returned page contains certain traces of ProcessWire. Simply checking the return code wouldn't be enough here For the record, isit.pw includes roughly a dozen methods for checking if a site is running ProcessWire. In many (most) cases it can still identify your site, even if that one check fails. I should probably mention that isit.pw (which is my project) is both a functional tool (as Antti explained earlier) and an experiment; "can you properly identify a site running ProcessWire or not?" I'm also planning to add an info section later, including details on hiding your ProcessWire-ness from humans and services like isit.pw equally

The Background Early in December 2013, the National Geographic Traveller India team at Amar Chitra Katha, called Pigtail Pundits over to help them build their website. Till then, the NGTI site was a poorly cobbled together, pale shadow of the publication in html and css, comprising, mainly content from the offline magazine articles. It was formatted too plainly, and didn’t carry the richness of imagery, gloss and character that you’d associate with anything from the National Geographic stable. The Brief NGTI had an ambitious remit for the revamped website. It will contain the offline magazine, in full, with each issue richly illustrated with some 35 odd travel stories and encrusted with glorious pictures The past issues of the magazine, some 15 of them so far, would have to be imported into the new system gradually It will carry have articles written exclusively for the web, by a separate editorial team It must have the ability for accepting photos from amateur travel enthusiasts, every day It must showcase the images from National Geographic Traveller in all its glory through on-page galleries and sliders It must have a workflow for the editorial to schedule articles into the future It must be fitted with rich tags to describe/ cross-tag the articles, the ability for browsers to comment and search ability built into it What’s more, it must come close in feel and richness to the National Geographic mother site in the US. That site incidentally, was in Beta at that time, and used some really fancy, jaw dropping scripts and effects. We were wondering as to what technology it was built on. But, there were a lot of challenges to tackle before we even reached to the front-end effects. To Drupal, or to Processwire? The Million $$ choice. We took on the challenge of the revamp. Thinking through and rationalising the different and varying content types in the magazine was our first task. We noted 13 different types. The trick was to winnow this down to just one content type that could fit all types of articles. Then, in fitting this content type into the system, we had to take a few calls. We argued that the system must have the flexibility to allow editors to embellish their articles - with drop caps, pull quotes, captions, guides and other style ornamentation that was singular to the National Geographic Traveller. In order to do this effectively, we would have pre-styled codes in the system that could be invoked using short codes as the editors saw fit. This was a whole sight better and more flexible than putting text into pre-styled boxes that would constrain the editorial. Drupal CMS was our first choice in putting this system together. We had worked with Drupal for several years now and we knew a thing or two about customising it too. The only challenge was to get a young team at Pigtail Pundits behind Drupal. The learning curve for Drupal was always daunting and that was a concern. We started work on Drupal in early January 2014. We cobbled together an internal team that would work on the project. After about a month into Drupal, we had almost everything ready for a demo to the client, save for styling. In early February, we had a rethink. We were working on some projects and testing out Processwire, internally in parallel with the NatGeo project. We found PW to be a fast, flexible, efficient system, without either the bloat and the learning curve required of Drupal. We had to take a call. Drupal, for all its goodness, still made heavy weather of its modules. Drupal optimisation alone required a lot of modules at the application level. Plus a few on the server - memcache, ably supplemented with server processing speed and memory in fair, generous helpings. But optimisation itself was just one of the many things that troubled us about Drupal. There were a heap of other modules, each adding weight and extra lumber to the ponderous system. Besides there was image heavy content. We had serious doubts as to the conditions under which the site would run well with Drupal, both immediately, and in the long run. We had to take a call. Time for a few seditious thoughts Could we now change the NGTI project to Processwire from Drupal? What would be the implications? For us, for NGTI? We had to grapple with a whole bunch of fallouts of this. How do we come clean with the client on this? Would that decision to shift hurt us? What if the client were to say no to the shift? What about getting our internal team that was already on Drupal, come to grips with Processwire? How long would that take? The reasons to shift to Processwire were clear. Speed, flexibility and scalability given the volume of content that was going to be part of the magazine and web editorial, the features we required, and the potential traffic on the NGTI site. The decision had to be made now. We decided to make an early switch to PW. And in retrospect, it was probably the best decision we took. We had to instil confidence in the client that this switch to Processwire was the right thing to do. If we relayed the news too early, it could have worked against us. We had to prove that PW was a better decision. So we went ahead and simulated all that we’d done in Drupal into Processwire without asking the client, or giving them a whiff of what we were up to. We worked in parallel on both the systems. It took us about 15 days to get everything in Drupal into PW. Mercifully for us the client was hunting for a design team that would do justice to the Nat Geo design pedigree and that took some time. Along with the fact that the new web editorial team was still being formed. We used this lull effectively to make the switch. Remarkably, our Drupal team picked up PW twithout any issues. It took them a week to grasp it and get going. That was a record of sorts as we’d folks who struggled with Drupal even after 3 months on a project, still coming to grips with techniques and modules. But PW was a cinch. The Processwire Miracle We put together the first cut of the site in Processwire. Rationalized content types for magazine articles were in One magazine issue was fed in so that we could slap on some styling Hannah code was used generously to style the content within the editor, without getting in the way of content, or trapping this into pre-styled text-area boxes. Magazine captions, guides, block-quotes, drop caps were driven by Hannah to facilitate the editorial hoopla Gallery and slider scripts were quarried for the demo The demo date was decided in early April. We showed off the system, its speed, and ease of use, live to the client. It was only after the demo that we told them that the system was not Drupal, but Processwire. They were already sold by then. The real intensity on the NGTI project however started in June 2014 when the designer Matt Daniels was brought in by NGTI. We were privy to the early designs of the Home Page, Landing Pages and Detail Pages. But were anxious as to how things would play when the entire design was complete. After all the design was not in our control. Luckily, everything went off well. There were a few challenges, and these were taken up and resolved. Javascript for the galleries, sliders had to be rewritten from scratch to conform to the design requirements Editorial came up with a list of how they wanted articles to be featured on the Home Page in blocks and we had to program this accordingly. We managed to queue the articles and then lop the old off, when the new were published Destination page required maps by default and then of city/ country being searched. This was programmed using Google APIs. Marketing came up with the need for ads - leaderboard and sidebar and we had to fit these in An Events Calendar was programmed from ground up, as per the design for Events The import of prior issues was debated, captured into excel sheets, reviewed, and reviewed some more. Scripts were written for import. Scripts were written to test the integrity of the data input before import. And everything came together in August, 2014. 6 magazine issues were imported before the launch was announced on August 14. The NGTI team went in and styled these quickly using the tools we had built for them. The final build had 20 different templates. In retrospect, we could have rationalised these too to fewer. But these came in bit by bit for the build and there was little we could do there as we couldn’t see the whole, before it arrived. The NGTI team was trained on the backend operations as part of the build itself, so by the time we had completed the site, they were up and ready to input. The project is still in beta for a few days. Optimization using just compression of CSS & JS works fine for speed. The site works like a charm now. Thanks everyone Thanks are due to Processwire and the amazing system and set of modules that are in place. Thank you Ryan Cramer. We don’t have to tell you how much we enjoy working with this system, after coming from Drupal and WordPress. Thanks to all the lovely folks on the PW forum who had answers to niggling issues we had. Key Tools, Systems used: Processwire 2.4 CMS with Foundation 4.0 framework Hannah Code for short codes in the editor for style application Event Calendar was coded ground up Form Builder was used for front end forms CK Editor, for text area editing with Image extra for description and tags ProCache - for server level caching Video Embeds and Images used field uploads Image Captions & Tags using image extra fields Scheduler, for advanced date publishing AIOM - for compressing JS and CSS for speed improvements MailChimp Integration for Newsletter Disqus Integration for Comments Integration of Facebook, Instagram, Google Maps via API Integration and customisation of Google Search Integration of DoubleClick and Adsense for advertising

destinations UNLIMITED This site is a conversion from an old Joomla site that is far better suited to processwire due to the 100s of facts and figures about the destinations. Many of the facts from each of the destinations help to form other content such as blurbs on the video content hopefully adding quality content for google to index. It's also got a growing number of features for registered users such as being able to add personal comments to destinations which collate into a personal notebook. Hope you enjoy having a look around. Although the site is now live, I don't think it will ever be finished! ..not to forget a thank you to everyone who has helped me with the project along the way!

Damn, should've known they don't call kids those simple bird names nowadays even in Ireland)) Welcome to the forums mr. Knight! Your multiple wishes are hard to address in one little topic in the Pub section. Searching for and participating in appropriate topics would be more effective and usefull to all of us. For example, there is already a topic about two column admin theme. Going there and posting something would bring it up and possibly move the discussion further.

Hey everybody, Many of us know about isit.pw, the web site that checks if you are running PW. I thought I should find out how it knows whether a web site is ProcessWire-powered. Turns out, it sends a "GET /?it=/trash/ HTTP/1.0" request, and if the response is 200, then PW it is. Next thing I did was to go to admin templates and change the default behavior such that ProcessWire would through back a 404 instead of offering to log in. Now, isit.pw does not like me for "not running" ProcessWire. However, I liked the method isit.pw uses. It can be handy if you want to run a quick check like this: http://<...>/<some_page_name/?it=/ If you get the Home page, it means you've hit a ProcessWire-powered web site. Have a good Friday and a nice week-end

Hi guys. Just wanted to properly say "hi" and thank everyone for all the help lately. I'd been posting as "sparrow" for many months while I got started and many of the regulars here have been a great help. I'm an independent web designer from Dublin, Ireland, and my primary CMS is MODX. A while ago I decided that 3 CMS would be a good number to settle on and I began to evaluate Craft and PW. What attracted me to PW specifically has been all the good stuff I'm sure you already appreciate but in particular, I really like: PW fields and especially how powerful the Profields set are Lister (not released yet) Image management (native and CropImage etc. Image control is brilliant in PW) Fields control (allowing me to specify exactly which field(s) to display per template) How friendly the community is How communicative Ryan is re. the product and the fact that there is a roadmap and that roadmap is largely followed and updated The array of great Modules available etc etc. But basically, PW has been impossible to ignore with the recent adittions of Profields and Lister. I'm very much at the beginnings of my PW journey so to be balanced, these are the areas that I've found challenging: Speed. I find *just* having a tree slows my editing down a lot. Would love to see a tree on the left and the page edit on the right. Obviously, I'm coming to this from a MODX perspective Right-click Again, probably baggage from MODX but it's very useful to be able to right-click a page and duplicate, delete, move, hide from menu, quick-edit etc etc. I can't do this on PW. But mayeb there's not such a need. User control The user control and permissions look very basic. I'm used to much more fine grained control over which elements of the admin a client can see Manager appearance When I first installed PW I found the box-iness and colors a bit hard to settle into. Some of that may have just been TinyMCE which I replaced and I believe made a huge difference. I know there are lots of themes available so that's not an issue now but was definitely a "first impressions" thing. PHP That's not PWs fault. I've gotten used to working with tags so being pushed into a bit more PHP has been a challenge. I'm enjoying it though and feel my skills are slowly but surely coming on. So that's my 2cent. Thanks again for all the help so far and it's great to be part of yet another very friendly CMS community. On a side note, I have started a mini blog based on PW, Craft and MODX as I think they really are 3 of the best CMS available. Will update soon when I have a little more content.

I think i'm going to make a page not of 'FAQs', but 'My Most Common Errors'

jtherczeg, I clicked on this thread to propose exactly that — using Transifex. As far as I know Transifex works best with typical gettext files but I wonder how/if this could be adapted to work with PW's JSON files.

Thanks Ryan! That's very appreciated. I value your work on PW a lot and think you really deserve the money you put into modules. Good to know I'm not crossing any line there!

Pierre-Luc it's nice of you to ask, but also unnecessary. That's always your choice if you want to release something you've created. There aren't any restrictions on what can be released as free modules (so long as they don't use code from commercial ones).

As some of you might have noticed recently there has been a large "Frontend Performance Talks Offensive" (not only) by Google Engineers. Here are some high quality (regarding content) Videos which i enjoyed very much and thought you also might be interested in. A Rendering Performance Guide for Developers by Paul Lewis: Performance Tooling by Paul Irish Your browser is talking behind your back by Jake Archibald Gone In 60fps – Making A Site Jank-Free by Addy Osmani http://addyosmani.com/blog/making-a-site-jank-free/ Any suggestions for more interesting performance related stuff are welcome!

1) a) I think the best approach is to store all the content pages under one hidden parent using the Details > Select a Parent for Items b) Not really an issue if you do a) c) Make use of Input > Automatic Page Name Format, and then go to the template context settings for the title field and make it invisible and not required. 2) This can be handled by setting the allowed parents for these content block templates. Hope that helps.

<?php echo $member->get($page->name)->title; ?>

I think it will happen less from now on

Here's a starting point: https://processwire.com/talk/topic/960-comment-spam-filtering-alternatives/?p=8097 But there are other links on how to do this in the forum as well.

It would be an interesting statistic to see how many times the 'problem' about single/multiple image and file fields has come up on the forum

Is your profile_image field a single image field? If not, you can either change this in the admin area by setting the maximum of files for this field to 1. If not, you could access the "first" image with the first() method. $thumb_contest = $contestant->profile_image->first()->size(50,50); If this doesn't work you might have to check if you have the right pages in the PageArray $contestants.

Hello, I've just really enjoyed reading this case study ! Just for information, mailerlite is another interesting email newsletter solution ("Email Marketing Software, Services and Newsletters"). Edit: a "Forever Free Plan" and affordable "Small Business Plans" now -> www.mailerlite.com/pricing And tinyletter.com and sendy.co

By now the slider expands always to full width, just the images are to small. To fix it I would suggest the usual way: max-width the slider to the image width and center from there. Same with the twitterbar.

Thank you. I'm not a great designer so bootstrap 3 serves me very well. Applying bootstrap 3 styles to the form builder forms is something I'd also like to achieve. I believe this can be done but will require slow more learning and reading for me. Changing the styles to one of the pre mades is easy. It also looks easy to create new ones from theme roller, but a little more complicated to use bootstrap; but possible I understand.

I have registered to Transifex and found Ryan's & Apeisa's ProcessWire project. As I can see, there is only some sample data there. Russian language has been requested but the request has not been accepted. @Ryan & @Apeisa: Could you please write about have you found transifex suitable to generate processwire-style translation files. Do you plan on using this service to maintain translations? If so, could you please import all the strings necessary or delegate this to someone from us, the community.

.hi stop and. enjoy trees two take.moment observed listens trees they listens.u 2

Hey Zahari, In a bit of a rush, but PHP's strstr might be what you are looking for. Not sure that you really need a Hanna Code in this situation. Just parse the content of the field in your template. $introtext = strstr($page->body, '[[readmore]]', true); Then when you echo out the body on the full version, just: echo str_replace("[[readmore]]", "", $page->body); Hope that helps to get you started. I am sure there are lots of other ways to approach this. I usually go with automatic truncation because editors usually forget to add things like a [[readmore]] tag.

I just tried Valery's first method of editing the admin template to give a 404 to unprivileged users and could then no longer access the login page from a second machine even when using the correct login page url. Fortunately I was still logged in as superuser on my dev box and changed it back. Looks like editing the .htaccess or nginx config might be a safer way to go.

(Javascript) Memory Management Masterclass with Addy OsmaniEfficient JavaScript webapps need to be fluid and fast. Any app with significant user interaction needs to consider how to effectively keep memory usage down because if too much is consumed, a page might be killed, forcing the user to reload it and cry in a corner. Automatic garbage collection isn't a substitute for effective memory management, especially in large, long-running web apps. In this talk we'll walk through how to master the Chrome DevTools for effective memory management. Learn how to tackle performance issues like memory leaks, frequent garbage collection pauses, and overall memory bloat that can really drag you down.

done. https://github.com/ryancramerdesign/ProcessWire/issues/641

Thank you all. If you have something else on your "wishlist" for development let us know. We spent the last week working on a super boring SAP shop for a university project so progress slowed down a little bit. However, I've made a new video to show the latest features we've been working on. Beside the new "Create site" page and the workflow for new users, we build backend features like the version change and a backup system. The service always has the latest ProcessWire files from github and it's possible to schedule sites for deletion now. Some bugs are still open and the Help page was just started. Our plan is to launch the service to the public in the next week.

Thanks @Nicholas for the comments. We are working on ProCache tweaks and this should be sorted by Monday.

Sorry about that - I have just committed a fix that I think should take care of it. Please let me know if it works for you now. Not sure why you got that error, but I have never seen it - maybe a PHP version difference? Also, note that it requires PW dev due to the way I set up the module info in a separate file.

I see Processwire as an open system and don't see any reason why not. I don't think there are any rules saying that if there is a paid module that someone else can't also release a free module that is similar. If that was the case I would start to feel a little worried about how open processwire is. I think there can be benefits to having both free and paid modules. For example Ryans modules have full support and updates from him which can be seen as a huge benefit over a free module so a free module might not always be the first choice over a paid module. Also some of the more richer users of Processwire will want to pay up the money for a paid module to support Processwire on top of the advantages of paying for a fully supported module from Ryan. I understand why you asked the question and I have wondered before what the reaction of Ryan and the community would be to free modules that do a similar task to any paid modules. My opinion is that it is only healthy for the community to have free and paid options even if they do similar things. Of course it would be interesting to hear Ryan's personal feelings on this.

I would prefer to move the translation process to an online collaborative tool, like Transifex. Anyway, in the upcoming version 2.5, available in the dev branch on GitHub, many language translation and localization enhancements were made, see recent blog posts Language Translation Updates and More Language Updates. Besides this, in the case of languages using accented characters and diacritical marks, not so easy to translate such language file side by side in a diff tool, like WinMerge, because the accented characters are encoded to hexadecimal Unicode characters, e.g. ä is displayed as u00e4.

See it in action:

Hi everyone, I'm pleased to announce a new website built on Processwire just went live : http://optimum-events.eu. It's my first multilingual site with Processwire and all in all the experience has been really pleasant. The website use Bootstrap 3.1.1, AIOM module and Maintenance module. Any comments is welcome as there's still room from improvements ;-) Regards, Nicolas

I also think that recaptcha is too difficult to read. But not only the text - also the audio is not understandable. So my solution which works perfect so far is the same as yellowled said: //HTML <input type="text" name="email2" id="email2"> //CSS #email2 { display: none; } //PW / PHP if (trim($input->post->email2) != '') echo 'hi spam'; For larger sites with lot of traffic, a combination of mulitiple approches is better