Leaderboard

Had fun to create a webfont with only one single glyph: Processwire-Logo Unicode-Letter:  (Unicode Block "For Private Use") I created first an svg with inkscape and created the font-set with http://icomoon.io/app (very nice website!) Like it, use it, waste it. font-package with demo file here: attachment=1836:processwire_webfont.zip updated 23.11.13 (4 Glyphs: 'processwire', 'process', 'wire' and 'w') processwire_webfont.zip

Just finished our companies new website build with Processwire. Main site: http://www.agrio.nl/ A few branding pages: http://www.vee-en-gewas.nl/ http://www.melkvee-magazine.nl/ http://www.agriomediaplanner.nl/ fully responsive pro-cached several "one page" pages for each section / brand unique structure with templates as building blocks Our companies home page structure is shown in the attached screenshot. It contains several templates used as building blocks. The goal was to have a reproduceable structure and design to be able to easily create new landingspages without the need to code anything on the front-end level. An additional benefit from this structure is the posibility to give content editors only access to the content templates (orange coloured). Another thing to mention is the shared (green) pages, which contains content that needs to be re-used on several places in the website. For example the footer contact and google maps. But also structures for certain content.

I have KendoUI in my bookmarks for some time, but never used it, so I don't want to recommend it. But it looks like it can do everything jQueryUI can do, plus some more. And at least the colors are themeable with sass. Here is a site comparing both: http://jqueryuivskendoui.com/

Lately there have been lots of people that are not enjoying the default admin theme, so we've been working on making something new. Not trying to solve all issues or add every new feature we'd like, but just trying to come up with something to have as an interim replacement for the default admin theme until we can afford the time to do something broader in scope (like Phillip Reiner's great admin theme design for example). So this theme doesn't necessarily break a lot of new ground, but hopefully has some of the improvements that people are looking for. Visually, the goal here was to find a lighter, more modern look and reduce the boxes-in-boxes feel of the current admin theme. I've opted to commit it to the dev branch because it requires the latest version of ProcessWire on the dev branch, and likely will continue to with updates. Meaning, I can't distribute this one as a 3rd party theme very easily. This is because I'm making core updates related to the admin theme at the same time. So if you want to help test this new theme, you'll need to grab the dev branch of ProcessWire. The new admin theme is in /site-default/templates-admin/. That means you'll see it as the default theme if you are installing a new copy of PW. But if upgrading an existing copy, you'll continue to get the old theme. If you want the new theme, then just copy the /site-default/templates-admin/ directory to your /site/templates-admin/ directory on your existing PW install. This would be in addition to replacing your /wire/ directory with the latest one from dev, as usual for PW upgrades. The existing default admin theme also remains in place in /wire/templates-admin/. So if you want to stick with the existing/stable admin theme, then just make sure you don't have a /site/templates-admin/ dir in place (unless you are using a 3rd party admin theme). This admin theme is probably not production ready, as it's not been tested in many browsers yet. I personally haven't yet tested it in anything but Chrome and Firefox in OS X. Please let me know if you experience issues in other browsers. I fully expect things won't be pretty in IE... but they never are. To start, this comes with 3 color schemes (though we'll be adding more too): Warm: Modern (similar to processwire.com site colors): Classic (similar to existing admin theme colors): To switch to one color theme or the other, specify a GET variable of 'colors' in any URL you are accessing in the admin: /processwire/?colors=warm /processwire/?colors=modern /processwire/?colors=classic To specify a default, edit your /site/config.php and set to one of the following: $config->adminThemeColors = 'warm'; $config->adminThemeColors = 'modern'; $config->adminThemeColors = 'classic'; We'll probably make this switchable in the user profile at some point, but that comes later. This theme also comes with some new features (most of which have been copied/inspired from the work of others here, whether in other admin themes, modules or designs): It now uses Font-Awesome icons rather than jQuery UI icons. We now only use jQuery UI icons for actual jQuery UI widgets. Note that asmSelect and our file/image inputfields are built as jQuery UI widgets, but I don't think anything else is. Basically, the majority of icons in the system are now Font-Awesome icons. You can associate Font Awesome icons with templates. When associated with a template, the icons will appear in the page list, in front of the page title. To use this, edit any template and go to the Advanced tab. In the "List of fields to show in admin page list", you can type in any Font Awesome icon name (in addition to the field names you could before). For example, in the Page List screenshots above, I have my "search" template configured with the value: "icon-search title". You can associate Font Awesome icons with fields. When associated with a field, the icon will appear at the beginning of the input. For example, I associated a coffee icon with my "title" field in the screenshot below. To do this, edit the field, click on the Advanced tab, and enter the icon name in the new field provided for it. The top navigation now supports simple dropdowns. A new "user" dropdown has also been added that contains profile and logout links. The main Pages screen contains an "add new..." button, that is itself a dropdown to a list of templates that are configured adequately for us to know where they would be added. To use this, you have to configure your template "family" settings. The search box is now ajax powered, though this was introduced a couple weeks ago in the existing admin theme too. The theme is responsive too, of course. This is all kind of preliminary and open to changes. I'm trying to keep the scope of the project fairly small since I don't have much time to work on it. But just wanted something to quiet the haters a bit for a little while, so that we can take our time on the bigger admin theme project for longer term. We'd appreciate your feedback if anyone has time to help test.

Hi i would like to share with you guys, a website i made thx to Processwire. Im super happy with processwire and this community. Ty for help everyone. here is the site: chemik-police.com

Thank you, this works for me: $ptrashed = $pages->find("template=page_events"); foreach($ptrashed as $ptrash) { if(time() > $ptrash->getUnformatted("publish_until")) { $pages->trash($ptrash); } }

had the same issue. it works if you make following change in ProcessEmailToPage.php on line 271: //$message['html'] = str_replace(' ', '', $message['html']); // change to $message['html'] = str_replace(' ', '', $message['text']);

I'm not sure I understand fully: With your qp_enqueue_script function, how do you solve the problem of loading a script only for a specific page? I think you still need an additional if? // Only load script for Page with name 'pw-rocks' if ($page->name == 'pw-rocks') $config->scripts->add('blub.js');

Agree with Ryan. If it is an article consider a custum date field in your template, default to current date. ( so editors don't have to do anything, unless they want to) Then the sort can use that date. That date is manipulatable.

Thanks Ryan. Yup, you're right it's *sort of* coming from the Thumbnails module because the module is extending FieldtypeImage. As @apeisa as getThumb() inits InputfieldImage via call to _getInputFieldInstance() and InputfieldImage has this in it's init() function: $this->modules->get("JqueryFancybox");

It was the InputfieldImage module which is extended by the Thumbnails module. See the rest of the discussion here http://processwire.com/talk/topic/4742-bug-maybe-thumbnails-module-using-getthumb-loads-jqueryfancybox-script/

I'm not sure what the value of sorting by "id" is, but if it's for chronological reasons, consider using "created" instead as your sort field. That's going to be more reliable to achieve the same purpose.

This is great, thanks Teppo! This is something I have wanted but just didn't know how to do. I will definitely be using this.

Adrian, the Pagefile::install hook should be triggered so long as the file doesn't already exist in the destination. Is it possible that the files are already in /site/assets/files/.../? If so, the file doesn't technically need to be installed, so the hook is never called. As for getting the field belong to a Pagefile, this morning I've committed an update (to dev) that makes that possible. You can now retrieve the Field object that is part of the Pagefiles/Pagefile in the same way you can retrieve the $pagefile->page, by accessing $pagefile->field (accessible from the pagefile or from the pagefiles array).

Hey guys! Another tiny little PW site we have built in the last few weeks. Really really reaaaaaally small budget, so nothing is really perfect on this website. But the client (a friend of mine, he is a teacher and a hobby author) is happy to now have more control about his content, speaking of his short stories and novels. See for yourself - feedback welcome: http://www.peterhohmann.net

This is one thing I love about PW. Many heads thinking and suggesting, one head deciding and acting quickly

yeah, no doubt. PW isn't a hard sell to a dev. I've had both types of clients. Ones who are more concerned about the results and not the platform and ones that specifically want to use a platform like Drupal or WP. I've never had one flip though. I'm not "selling" them PW. I don't even mention PW to a low tech client, I just tell them I'm building them a custom website with the features they are requesting and give them a price as Willy C mentioned. I will mention PW to a client who's more tech savvy. In that case I usually give them a 2-3 choices with a quick pro/con list and ballpark prices along with my personal recommendation. Then I let them choose. If price is a concern and it usually is, they will choose the cheapest platform that meets their needs, which is PW in most cases. Matthew, I'm sure you've tried these approaches and found your current approach to be the most beneficial to you. It just seems like such a struggle to me. I can tell you are a smart person though, and in this case, I think you would know best. I'm not trying to hassle you and i'll shut up now.

PW is defintely more a CMF than a CMS. As a marketing strategy it is difficult to say which way is better. For technical people I have explained that PW is Django of PHP world.

That's a good point. There's no point to wasting time or trying to sell something to someone who already has their mind set on WP. If you are dead set on only using PW, then focus on identifying the type of client who will appreciate why you have chosen to work with PW exclusively (put this philosophy on your about page, but don't get too techy). I would look into providing services to developers, agencies, CTOs, and entrepreneurs, (I fall into three of those category's hint, hint). Folks who have already been through the process of building a website may also be a better fit for your model. That being said, what's the reasoning behind this approach? Seems to me you are choosing a difficult path and your client acquisition costs will increase while your profit (if any) will go down. I can't imagine this model generating more than $65k per year for a sole proprietor. You'll be lowering your client lifetime value too, because you won't be able to retain your clients as long (they will need a service you don't provide and will eventually leave). This is a problem, because a profitable services business is built off compounding revenue from existing clients who need ongoing services, not individual gigs from new clients or one off gigs/clients. That time you spent and were not compensated for gets added into your client acquisition costs. Letting just two clients slip through your fingers, because you didn't want to provide them a WP site, probably cost you $10-$30K over a period of 3 years (just a guess, it's probably higher). I'm not any happier about coding in WP or Drupal, which is why I'm willing to hire a developer for this task (and no task is beneath me so I'll still use WP and Drupal). In that scenario I get paid to be a project manager and interface with the client, some money goes back into the business and the rest goes to my developer. I know the amount of money I'll make on the job is much less when I hire out, but I'd rather have a smaller percentage of something than 100% of nothing (and let's not forget about the additional services the client will purchase throughout the years). Are your clients paying you to educate them? If not, limit the amount of time you spend with a potential client until you have a signed agreement. Put some educational material on your website that you can steer them too (maybe also include a two minute video where you explain what PW is why people should care). Not only will this build up your SEO, but you will save time by not having to educate every new client over and over again. That gets expensive and as you have recently experienced. It's also deflating when you spend your time providing value to someone and they ditch you just before go time. Chalking it up to a bad week is commendable. Sometimes I really beat myself up over things like this, when in fact it was just that, a bad week. Don't forget to consider your client's experience. The better their experience the more likely they will hire you, refer their friends, and come back for repeat business. Make it easy for them. Sometimes low tech clients are overwhelmed by the tech talk. Even if you think you are dumbing it down, you are probably assuming they have some at least some tech knowledge that they do not. Sometimes they are too embarrassed to tell you they don't know what you are talking about (they don't want to sound dumb). Other times, perhaps more often than not, they may be afraid you'll take advantage of them. With new clients not enough trust has been established and they have no way to validate the information you are giving them. When they try to do so, they use google or talk to their friends and in this case, you are right, they are going to find a lot of info on WP and feel much more comfortable going that route. Here's a good resource that I review often: http://freelanceswitch.com/clients/12-breeds-of-client-and-how-to-work-with-them/ Another thing to consider when reading my responses. They are tailored for today. In the years to come PW will gain traction and the word will get out there. You won't have some of the issues you are having now, because the work you do will be in demand. In the meantime, if you want to convert clients to PW incentivize them, but don't use manipulation, fear, coercion, pushiness, etc. I just sold a PW site to someone for $1,200. The actual cost was $5,700, but the client was rewarded for taking a risk and putting their trust in me. You may try offering a 100% satisfaction guarantee or a substantial discount.

Hi Matthew, gosh that's rough isn't it. I've been there before (as I share below). However I don't believe you lost the gigs to WP or Drupal. I think you lost the gigs, because you didn't provide a service that your clients wanted. And... You assumed you knew what was best for your client, when they specifically told you what they felt was best. You were probably correct in your assessment of their technical needs, but I can't imagine you would have a good understanding of their needs from a larger business perspective without having worked for/in that business for a few years. Last Jan. I had a 12 month contract for $48K to build/upgrade an existing Drupal site and to help build a foundation that would help them bring in more revenue. While I was doing a great job for them, I was focused on the bigger picture, the needs and demands of the business. I should have been focused on the "wants" of the clients, because they terminated the contract and I took a $35K hit to my income this year. They canned me for the same reason you didn't get those gigs, I wasn't providing them what they wanted. They couldn't understand their "needs", because they didn't have the experience of growing an online business. So from their perspective, they were paying good money and not getting what they wanted. They had no idea what I was actually doing for them. Imagine going to a fast food restaurant for a burger and having the cashier say, sir, your overweight, I know you really want this burger, but trust me I know what's best for you and what you "need" is a salad. You can buy the salad, but the burger is not on the menu. This is essentially why we both lost our gigs. I'd guess over 85% of the websites are powered by WP or Drupal. That means 85% of the people who need web work need Drupal or Wordpress services. You can choose to only support PW, but now you are trying to sell services to a fraction of the remaining 15% which is going to be difficult. PW is new, we are early adopters, it will take at least five more years before PW gains traction (and much longer to start taking market share away from Drupal & WP, though I'm confident this will happen). Right now, you should be supporting WP and Drupal, but start positioning yourself to offer PW services when the demand is greater. I'm only selling PW to people who trust my judgement implicitly. They are sold on me, they really don't care what platform they use, because they trust me so it's an easy sell. I'm not selling PW to new clients unless I can show them a side by side price comparison between WP/Drupal and PW. That's an easier sell. They don't want to understand how the technology is better, they want to know what features they will be getting and at what cost (e.g. contact form, blog, fb integration, etc.). If they can get more bang for their buck with PW, they may go for it. The key to selling services... don't "sell" people anything they don't want or aren't asking for (I'd change my strategy for products). It really couldn't be easier. If you are "convincing" someone, you aren't selling. Just listen to what they want and give them a price. If you don't provide the service, this is your opportunity to provide something of value to them, find a qualified person who does and connect them. They will leave the experience with a good impression of you and will tell others about you or come back later when their needs change. You can also take on the project and hire someone else to do the work (if you don't have the skills, or if you are like me and don't want to use Drupal anymore). If you do this, you'll need to take a percentage for your salary (now as a project manager) and a percentage needs to go back into your business to help you grow the biz. The rest goes to your developer. I also do passive selling. So back to your scenario, in that case I would have sold them the Drupal or WP site and I would also mention to them that I provide other services that they may be interested in utilizing. I don't do this with any expectation of actually selling them something "today". I just let them know what I offer, so that when the time comes, they think of me. For example, after the successful launch of their website and when my client is ecstatic with my work, I may mention that I provide ongoing SEO and marketing strategies to help grow traffic and revenue. I don't even ask if they are interested, I simply say, "Keep me in mind if you ever need SEO". You'd be surprised. SEO may be not be on their list of priorities, but when it is, they think... "I need SEO, and I already know and have a relationship with someone who's offering these services". I do like your strategy about positioning PW against PHP Frameworks, because it's a product best suited for developers (right now). This tagline is very similar, but would do just that. ProcessWire is a RAD PHP content management framework that helps developers build better custom websites and applications faster and more securely. That being said though, I trust Ryan, I don't know where he wants to take PW or who his target demographic is. I can't even begin to know if this is a good idea without getting the full picture from Ryan. Same offer I made to pwired goes for everyone here. You are welcome to send me your skills and work examples and when I have a client that needs your skills, I'll reach out. I'm here to help and we can all be more successful by working together. If you have questions, get in touch.

Nope, not luck. I've never handed out a single business card. I work harder, longer, smarter. Where others give up, I keep going. There's a fine line between doing good work and great, and I put forth the effort that others don't to produce great work. I'm also very careful not to think about what I don't want, but rather what I do want. For example, while you are thinking about prices in the supermarket, elec, gas, rent, etc. your perception shifts to fear and scarcity. Afraid you can't pay rent, afraid you don't have enough work, afraid you'll be in debt. You attract what you think about. I'm an entrepreneur, and yes, I have the same concerns, but instead of worrying I'm thinking about solving problems for others, growing my business and how I can provide value to others. Which thought pattens do you think will serve you? If you want to build websites, how does thinking about supermarket prices help you do that? Money and success is a natural bi-product of correct thinking and providing value to others. So that's one aspect, and it takes practice to correct thought patterns that aren't serving you (limiting beliefs, e.g. the market sucks, there's no jobs. Some of my most successful times were during my nations worst economic recessions). Looking at this from another perspective... If you aren't getting work, asses your skills and talents. If you are skillful and have the talent, then you may need to just get out there more. Do more networking, ask family and friends if they know anyone needing a website, talk to local businesses, reach out to design agencies, reply to tons of classified ads frequently. Make unsolicited call, send emails, stand in front of a supermarket and embarrass your self with a cardboard sign that advertises your services (if that's what it takes). It's a numbers game. In e-commerce there's something called a conversion rate. Converts are the website visitors that actually buy something from the website, not just a site visitor who stops by to look. A good conversion ratio is between .5% and 1%. That means that for every 200 site visitors only 2 of them will buy something. The same idea applies to getting paying gigs. Have you offered your services to 200 people this week? If so, maybe you'll pick up a gig or two. If not, hustle. Reply to 20 classified ads a day, five days a week. That's 100 people who know you now. Go out into your community and find another 100. Maybe that means sending unsolicited emails and making phone calls, maybe it means stoping by the shops that you like. Go to book stores and libraries and slip your biz card into the how to build website books. If you want some help, send me a list of your skills and some examples of your work. I'll keep you in mind when I or a client needs someone with your skills. If you have any questions, I'm happy answer them over skype, email, this forum, etc. Some good resources to consider: Marketing Without Advertising: Easy Ways to Build a Business Your Customers Will Love and Recommend 177 Mental Toughness Secrets of the World Class Business Lessons for Entrepreneurs Change Anything: The New Science of Personal Success Mind Performance Hacks: Tips & Tools for Overclocking Your Brain http://fundersandfounders.com

I have just finished and uploaded new layout of the MSSOOnline website. http://mssoonline.org/ I used latest ProcessWire and HTMK Kickstart to develop this website for not-for-profit organization. This is another not-for-profit website I developed with ProcessWire CMS as volunteering work. I love ProcessWire so much that I keep creating website for free for charities!!! Please provide your feedback for improvement or to fix any issues.

You'd want to hook after $pages->save(); If you want your function to execute on every page save, any time, then you'd want to create an autoload module. http://wiki.processwire.com/index.php/Module_Creation If you want to capture newly added pages separately, then you'd also want to hook $pages->added(), which is called after a new page has been added. This example shows both: /site/modules/HelloWorld.module class HelloWorld extends WireData implements Module { public static function getModuleInfo() { return array( 'title' => 'Hello World', 'summary' => 'Just an example module class.', 'version' => 1 'autoload' => true, ); } public function init() { $this->pages->addHookAfter('save', $this, 'hookSave'); $this->pages->addHookAfter('added', $this, 'hookAdded'); } public function hookSave(HookEvent $event) { // this function called any time a page is saved (whether new or not) $page = $event->object; // now you can access anything from the $page } public function hookAdded(HookEvent $event) { // this function only called after a new page added $page = $event->object; } }