Leaderboard

To start, get a fresh copy of ProcessWire and install it (with the included basic profile). Then get a fresh copy of HTML Kickstart and unzip it. You'll want to take these dirs/files from HTML Kickstart (below), and move them to the root of your ProcessWire installation (where ProcessWire's /index.php file is located): /css/ /js/ /style.css I've taken the example.html that comes with KickStart and converted it into starter ProcessWire templates for you: html-kickstart-processwire.zip Unzip the attached file to replace the files in your ProcessWire's /site/templates/ directory. This includes these files: head.inc foot.inc basic-page.php home.php Now view your site. You should see HTML Kickstart's example.html file powering your ProcessWire site. Navigation should be using HTML Kickstart's horizontal menu and both bodycopy and sidebar should populate. I've left several static elements from the HTML Kickstart example.html as well, so you've got more to experiment with here. Let me know how it goes and if it makes sense. This thread is also related.

Hey Processwire addicted, I´ve justed finished my portfolio site named misterui. Just a simple page to give me the oportunity to sell some of my work. The entire page is done with Processwire. I have coded a little eCommerce solution based on template files. Biggest need was that the page could do almost everything automatically, like creating invoice and notification mail. I came up with a front-end solution to handle orders. I could see open orders and closed orders, from the frontend I could advice the system to send the client his download link by just set the order to paid status. Orders are just pages with the data provided by the client and a attached file according to the product the customer ordered. The attached file is automatically deleted after 14 days to save some disk space. Well, pictures say more than thousand words. Just watch the attached video which shows the order process and the order handling for the superuser. https://youtu.be/Oz53MYdwtOg http://www.misterui.de

echo $wire->pages->find("author~=Sam Smith") Doing echo on a page array, this will output id's separated with a pipe. This is using a toString method that is for convenience if you use the result in a other selector it will get inserted as string as 1929|1293|1231. Which is handy. Otherwise it will be a page array you can further use. For example: $found = $wire->pages->find("somefield*=anyword"); $result = $wire->pages->find("selected_authors=$found"); Which will result behind the scenes as something like this: $result = $wire->pages->find("selected_authors=1928|1233|1234"); Where selected_pages would be a page field for example. If you just really need the count of a find you can also just use count instead. $count = $pages->count("authors*=John"); Which is more efficient than a find.

When there is a market for it, I'll be glad to have a ProcessWire VIP.

Has anyone used paymill?

I have, of course, seen Ryan's excellent "Blog Profile" for ProcessWire. As I understand it, this package serves as a replacement to the default site and assumes blogging is the main purpose of any PW site it's applied to. Great. But at our shop, blogging is almost always just a *part* of what a client site is intended to do. A blog is merely a *section* in a larger site. So, that brings me to my likely need to put together more of a drop-in addition for PW to make it easy to *add* a blog to an existing ProcessWire site. As it happens, I'd really like to do some work in the PW community to help expand PW's overall appeal. Seems to me, a drop-in blog module would be a great place to start. Has anyone else gone this route or had ideas they might want to share? I'm not so much looking for code here. This would be more of a discussion about approach, feasibility, and a wish list for such a module.

This is in fact simple to do, but it does require knowing how to put it together without a CMS first. So I would suggest getting your layout up and running as a functional mockup, outside of ProcessWire or any CMS (just HTML and CSS). You could also get by with using an existing HTML page that already does these things. Lets say you've now got that in a file called home.html. With a fresh install of ProcessWire (using the included profile, not the blog one), you'd copy your home.html file to /site/templates/home.php. Now view the homepage on your site. You should see your page. If some things are broken, then that is because the links to the CSS files and other resources have changed. Typically we place our CSS files in /site/templates/styles/ and our javascript files in /site/templates/scripts/. But you can place them wherever you want. Wherever you place them, you'll want to update your /site/templates/home.php file to reference them directly. So if you had a line at the top that said this: <link rel='stylesheet' type='text/css' href='css/style.css' /> Then you'd copy everything from that old 'css' directory into /site/templates/styles/, and then update your code to say this: <link rel='stylesheet' type='text/css' href='/site/templates/styles/style.css' /> Better yet, make it say this, so that it will continue working no matter where you happen to move your site: <link rel='stylesheet' type='text/css' href='<?=$config->urls->templates?>styles/style.css?>' /> With that line above, we're asking ProcessWire's $config variable for the URL to the templates directory. Since it determines that at runtime, it'll work whether your site is running from root or a subdirectory. Once you've got your homepage looking the same as it did outside of ProcessWire, then you are good to move forward with the next step, which is to make it dynamic. This short tutorial will get you started and give you what you need to know to proceed with your magazine style blog homepage. There are also more tutorials in the Wiki that you may want to check out after covering the basics.

What id, and from where you got it? If you got the repeater id (which is a page behind the scenes) you just do. echo $pages->get($id)->myfield;

->getTotal() not .getTotal().

My suggestion: Start with the blog profile and build the rest of your site around. I just finished a site this way - the blog lives under a "blog" menu. The advantages: You have all the features of a blog "out of the box", in my case I didn't even need them all. Take a look at the blog profile: There's a file called "blog.inc.php" with functions for searching and listing posts, comments etc. which you can reuse also on other parts of the site. All the markup of the blog is separated in a folder "markup", should you want to change this. Cheers

I don't think this will fix all of your problems (or maybe even any!), but I found I had to set: $config->sessionFingerprint = false; Otherwise I was being asked to login again every few minutes. Might be worth trying.

I can't imagine why any such effort would be "difficult". Every other content management system with any level of adoption has at least one similar module available. Blogs almost always include a handful of standard features: 1. A holder page for a list of links to each entry. 2. A dedicated page for each entry. 3. Optional comments for each blog entry. 4. Common sidebar "widgets" for monthly and yearly archives. 5. Possibly an RSS subscription icon or text link. Pretty standard, no? Of course, it's impossible to be all things to all people. But if that was the goal, no blog module would ever get written.

Remove start=0.

you can use the pagetype field for all these relations. It's just a mater of organizing your pages accordingly. So, taking your example, you could organize your PW tree like this: -people --john --doe --xico --... -organizations --acme --corporation --lda --... -industries --candies --guns --moon trips --... -types of people --nice --bad --so so --... Then, on the template for organizations you put a page field with "industries" as parent of the selectable pages (PSP), and on the template for people you put two page fields, one with "types of people" as the PSP, and the other with organization as the PSP. You can make this system grow indefinitely Just think that any time you want a dropdown, or a selector for multiple choices in your templates, this is the way to do it in PW, even if those pages only exist to be a selectable value on other pages. Edit: And welcome to the forum

This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened. At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide https://modules.processwire.com/modules/process-changelog/ https://github.com/teppokoivula/ProcessChangelog How does it work? Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table. How do you use it? When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while. For detailed installation instructions etc. see README.md.

ProcessDateArchiver ProcessWire Date Archiver Process Automatically archives pages based on a Datetime field (e.g. /news/2013/01/03/some-news-item/). Behavior - When you add a page with a specified template, the module will automatically create year/month/day archives for it. - When you change the date in a specified Datetime field, the page is automatically moved to the correct year/month/day archive. - When moving or trashing a page, the module will automatically clean up empty year, month and day archives. How to create an archiving rule 1. Go to the Setup -> Date Archiver screen in the ProcessWire admin. 2. Click on Add New Archiving Rule. 3. Specify the template that should be archived (typically the news-item template). 4. Specify the Datetime field that should be used to determine the date to archive by. 5. Specify the template that should be used for creating year archives. 6. Optionally specify the template that should be used for creating month archives. 7. Optionally specify the template that should be used for creating day archives. 8. Click Add Rule. Tips and tricks - Configure the archive templates that will contain other archives to sort its children by name. - Configure the archive template that will contain the news items to sort its children by the specified Datetime field. - You will improve usability if you dont allow the user to create date archives manually. How to Install 1. Install the module by placing ProcessDateArchiver.module in /site/modules/. 2. Check for new modules on the Modules screen in the ProcessWire admin. 3. Click Install for the Date Archiver Process. Module download: https://github.com/u...hive/master.zip Module project: https://github.com/u...ssDateArchiver/

This module enables you to limit edit access (by role) to any field in the page editor. This essentially provides field level access control on top of the existing access control system. It removes access to fields within a template, which is something that the built-in access control does not currently do in ProcessWire. This gives you a nice and simple granular control of fields. For instance, you might have two users (with different roles) that have access to edit a page, but only one of them could edit a particular field you had limited access to. Another example might be if you (the superuser) wanted to keep a notes field that only you would see in the page editor. But those are just simple examples, and the possibilities are quite broad. I've been wanting to find a way to provide field-level access for awhile, so this module has been on my mind for a bit. But what motivated me to finish it was a need that came up earlier today by Raymond Geerts in this thread where he needed the ability to limit access to fields on the page's settings tab... this module would do that quite nicely. http://modules.processwire.com/modules/page-edit-field-permission/ https://github.com/ryancramerdesign/PageEditFieldPermission How it works This module hooks in to modify the behavior of Page::editable, which is used throughout ProcessWire, but most notably by Page Edit. This module looks for permissions in the system that follow the name format of page-edit-[field] where [field] is the name of an existing field in the system. When it finds such a permission during a Page::editable call, it checks to see if the roles from the current user have this permission assigned. If they do not, then permission to the relevant field is refused, thereby preventing edit access to the field. This module also hooks into the Page Edit process and simply removes fields that the user doesn't have access to edit, before the form is rendered or processed. How to use it Once the module is installed, you get a set of checkboxes on the module configuration screen. Check the boxes next to each field that you would like it to create permissions for. (Alternatively, you can create the permissions yourself, so this is just a shortcut). You should only create permissions for fields that you intend to limit access to. Once your new page-edit-[field] permissions are created, any non-superuser roles that previously had access to edit those fields will no longer have access to edit them. To give them access, you must edit a role and check the box for the relevant permission.

ProcessWire is fast. With ProCache, ProcessWire is insanely fast! ProCache provides the ultimate performance for your website by completely bypassing PHP and MySQL and enabling your web server to deliver pages of your ProcessWire site as if they were static HTML files. The performance benefits are major and visible. Using ApacheBench with the homepage of the Skyscrapers site profile, we completed 500 requests (10 concurrent) to the homepage. The amount of time occupied to complete each of these was as follows: 29 seconds: no cache enabled 6 seconds: built-in cache enabled 0.017 seconds: ProCache enabled As you can see, the performance benefits are substantial. ProCache gives you the ability to drastically reduce server resources and exponentially increase the amount of traffic your server can handle. This is especially useful for traffic spikes. Beyond measurements, ProCache makes your website feel faster to users, respond faster to search spiders (which can help with SEO), and helps to conserve server resources for requests that actually need PHP and MySQL. ProcessWire is already very fast, and not everybody necessarily needs what ProCache delivers. But regardless of whether you need it or not, there is little doubt that you can benefit greatly from ProCache. For an example of ProCache in action, visit processwire.com or the skyscrapers site. Look in the lower right corner of the page (in the footer). If it says "ProCache", it means the page was delivered via ProCache. We did this for demonstration purposes (ProCache does not put anything in your markup unless you tell it to). More information about ProCache can be found on the ProCache documentation page. Please note There is a known issue when using ProCache with the LanguageLocalizedURL module. I hope to have this figured out soon, but for the moment you should not use ProCache in combination with that module as it doesn't appear to work in full. ProCache does not yet support multi-host capability (i.e. cache and delivery of different content per hostname), but it will very soon. How to get it Like with Form Builder, ProCache was produced as a commercial module to support development of ProcessWire. It is now available for purchase here. ProCache is in a beta test period. As a result, it's being offered with introductory pricing that may increase once we're out of that period. During the beta test period, I just ask that you let me know if you run into any bugs or issues during your use of ProCache. I also recommend that you follow the usual best practices with regard to backing up your site and testing everything before assuming it's all working. Beyond the introductory pricing, you may also use coupon code PWPC-BETA for 10% off the listed prices at checkout. This code will expire as soon as we're out of beta. When you get ProCache, you'll also get 1-year of access to the ProCache-members support and upgrades board, available here in the ProcessWire forums. Upgrades to ProCache will also be posted there for download. Disclaimer: At the date/time that I'm writing this, I think that I am currently the only one using ProCache in production use. That's why I'm providing it with the lower costs and coupon. If you are running production sites where everything must always work perfectly, you will either want to: 1) wait to install on important sites till it's out of beta; or 2) test thoroughly on a staging server or localhost before taking it to production use. In either case, always make sure you have good backups anywhere you install new modules, and always test to double check everything works how you want it to. Get ProCache Now ProCache Documentation Below are a few screenshots that show the configuration screens of ProCache. Have questions about ProCache? Please reply to this topic. Thanks for your interest in ProcessWire ProCache!

Hey folks, just found etherpad lite and I'm quite liking what I'm seeing. It's a live document collaboration tool and Mozilla has a server up and running where you can start public or 'team' documents you want to work on with others. I've just started one here to play with and invite you to join in and try it out. I wonder if this might be a way that we, as a community, might be able to work on documents for the wiki or something? Anyway, give it a try and see what you think.

THis is now out of date and WILL NOT WORK with recent versions of ProcessWire This is a Bootstrap based admin theme This is a very early release and may not be up to production standards - use at your own risk, or just play around with it. UPDATE New version has lots of improvements (see screenshots) and has been updated to Bootstrap 2.3 And roll back to 2.2.2 - at least the JS. It runs into problems with the version of JQuery, I think. Important - this is developed for the DEV branch of ProcessWire and is not fully compatible with the current stable release. The Bootwire Admin theme uses the most current version of Twitter Bootstrap and should be easy to update as new versions come out. Any changes to Bootstrap are done with overrides and the bootstrap.min.css and bootstrap-responsive.min.css are left untouched. Features The theme has been kept sympathetic to the original PW admin colours and layout. The top menu features drop downs rather than linking to an intermediate page (thanks to Soma and his lovely Teflon theme for the menu). I have tried to make the theme as responsive as possible, but I was foiled on some pages by some Tables and TinyMCE - if you want a responsive edit page, make sure your TinyMCE tool buttons are over a couple of rows rather than one long one. Page list actions have been replaced with Icons so that they take up less space (useful for small viewports) Compatibility This was designed using the PW Development branch and using the Chrome browser. It has been tested on other browsers, but not extensively, so any problems, please yell! Overrides Overrides to Bootstrap are in the bootstrap-overrides.css file. Main,js has several overrides to turn elements Bootstrap compatible. There is also a commented out section which changes the page list icons to a dropdown button - however, this is not working in this version. Installation Unzip the archive and place the template-admin directory in your "/site" directory. Note: since this is not a full release, it is not available through Soma's Module Manager. Thanks Soma, for allowing me to steal bits from Teflon and helping with the menu markup Diogo for Teaching me a bit of JQuery and helping with the page list action button (still to be implemented) Ryan for making it possible to create an admin theme in a couple of days (including working on other stuff) Files Now on GitHub: https://github.com/jsanglier/Bootwire-Admin/ Download Hope you enjoy it - leave nice comments below! Joss Screenshots bootwire-admin-v0.4.1.zip

The shop system looks great. In the portfolio page the elements feel a bit lost a detached from each other, did you consider centering the Hallo and the Kontakt blocks? Also this is happening on my browser

I've been seriously researching the options for digital products (e-goods) since we have several record label clients running stores that sell music downloads, and we're attempting to migrate away from Joomla, where we have been using a component for this. So far my experience with Ecwid has been great - the pricing is very reasonable, they have a free plan, and everything seems to work well; For e-goods, you get 100 products, unlimited storage and bandwidth for $15/month. The only issue is the 100MB max on the filesize, but there are ways around that, such as splitting large files into multi-part archives, however this can be less than convenient for the end user than just getting the complete file. Ecwid integration with processwire is nothing; the only thing that could get tricky involves the SEO with ajax, and they have instructions for how to get this setup right; Most people would have a separate page for each product in PW anyway, so that wouldn't be an issue. the other e-goods options I have looked at include: http://www.fetchapp.com https://gumroad.com/ http://quixly.com/ http://pulleyapp.com/ Fetchapp's pricing (http://www.fetchapp.com/pages/plans) can't really compete with Ecwid, unless you use the $10 "use your own server" plan, and then host the files on s3. I think one advantage of fetchapp is that it can host larger files without breaking them up; The only other thing is that Fetchapp is digital goods only, while Ecwid can do both digital and physical.. Gumroad looks cool- there is no monthly fee, and you don't need to have a payment gateway, like PayPal... this article was kind of helpful... http://www.smashingmagazine.com/2012/03/29/selling-digital-goods-online-e-commerce-services-compared/ -marc

poor antti yeah but I agree with you, very annoying.

Thanks I was able to duplicate with the example you posted on one server and not on another. The htaccess file shouldn't send the request on to PW if it contains anything other than "-_.a-z0-9/". But it looks like on some servers, Apache itself doesn't accept the other characters and just removes them, sending the URL on to ProcessWire. The result of something like "/*/" is double slashes, like "//". That's an unexpected condition--we don't expect this from Apache. So I updated ProcessPageView.module to expect it, so that it throws a 404 rather than a fatal 500 error.

Rebooting has fixed more problems in more computers than any other solution ever. I suppose the same could apply to things like restarting APC. I'm guessing that made it clear the cache that was holding it up. But keep an eye out for it. What turns up once might again.

Why not just use $session? Of course, that's represented by a cookie behind the scenes, but the actual data stored in it remains server side and not manipulatable by the user. So it's safer than a cookie from that standpoint. Nearly the only time I use cookies is from Javascript/jQuery, as $session tends to accomplish anything I might use a cookie for on the PHP side.

Hi again. This is my first project on processwire, by now i think its a whole lot more professional than wordpress (the cms i used before). I want to make a magazine style blog, with featured articles, a slideshow or a featured article's tab in the homepage. Im looking around and dont seem to find a module that makes this possible. If anyone knows a "simple" way to do this, ill be more than glad to read

As I told, I'm not an expert, but for this I will stick to my answer

You could accomplish the above in various ways. I'll cover two: Option 1: Structure -people --john ---organization 1, ceo, 2010-2012 ---organization 2, board member, 2009-current --mike --etc. The above would have child pages of each person that represents their organization connections. The fields on that template would be: organization (single page select to /organizations/) position or title (text, their position at the organization) start_year (integer) end_year (integer) Option 2: Repeater This is the option I would use, and it's perfect for this sort of thing. It's basically doing the same thing as option 1, but making it simpler and disconnecting it from the structure. You'd create a new field using ProcessWire's repeater fieldtype, perhaps naming it 'organizations' or 'person_organizations'. Then add the same fields mentioned in the bulleted list above. Add this new 'person_organizations' field to your 'person' template. Now you can define as much meta information for that person<->organization relationship as you want to. More on how to use ProcessWire's Repeater fieldtype

The RSS feed module as it is now, is designed to cover the most common scenarios. But it's by no means limited to just common scenarios. Like many things in ProcessWire, it's something that you can copy from /wire/modules/ into /site/modules/ and then modify to cover your specific need. In this case, you'd copy: /wire/modules/Markup/MarkupRSS.module to here: /site/modules/MarkupRSSCustom.module Then edit the /site/modules/MarkupRSSCustom.module file and change this line at the top: class MarkupRSS extends WireData implements Module, ConfigurableModule { To this: class MarkupRSSCustom extends WireData implements Module, ConfigurableModule { And this line: 'title' => 'Markup RSS Feed', to this: 'title' => 'Markup RSS Feed (Customized by Lauri)', Then install the new module from your admin by clicking to: Modules > Check for new modules. Click "Install" for your new Markup RSS Custom module. In your site templates, you will pull in the module using it's new name rather than the old one, i.e. $rss = $modules->get('MarkupRSSCustom'); You can modify your custom RSS module to add any additional fields or capabilities that you want. And you don't have to worry about losing them during ProcessWire upgrades, because everything under /site/ is protected through upgrades. Let me know if you have any questions or need help getting any part of it to work.

Not sure I understand much of that, but try editing /site/config.php and setting: $config->sessionFingerprint = false;

Thanks a lot! Im new here and eventhough i have a simple knowledge of html and php i still need to figure out how it is implemented in PW. I hope i dont annoy people in the forum, but im sure other people that come to PW will have similar doubts

Really all you need is a few template files and a module would simply serve to create the relevant fields and install the comments module for you. Technically that's pretty simple to achieve, but on a brand new site you could just start with the blog profile and add other pages. It's no different than a normal install except it has blog functionality out of the box - it's really easy to add other pages to it as there's nothing preventing anyone from doing that. I can't remember the layout of the blog profile off the top of my head, bit assuming the homepage template lists blog posts you would just set up a /blog page with it's own template, move the code from the homepage template into it and you have successfully moved the blog into its own section.

There are one or two session security based settings on config.php that might help here.

Hi FuturShoc, There was this from Nico you might have seen: http://processwire.com/talk/topic/899-bundleblog/?hl=blog I'm in the process of adding blog sections to some existing PW sites and creating a couple of new dedicated blogs from scratch. What I'm finding is that each one will be different in terms of the functionality required. It's be nice to have something 'drop in' but I think it'd be difficult to cater for every need. Cheers Marty

Ok, so i got the header with a logo image Tried to work around imitating other processwire installation i have with a common site and ended up with this at the main.inc file around line 60: <div id="masthead" class="sixteen columns"> <div id="site-headline" class="twelve columns alpha"> <a href='<?php echo $config->urls->root; ?>'><p id='logo'>ProcessWire</p></a> </div> Then added a logo tag to the CSS in the main css like this in the masterhead section: #logo { position: relative; left: 0; padding-bottom: 0; padding-top: 0; margin: 0; background: url(images/logo.png); width: 392px; height: 100px; text-indent: -9999px; } I dont know if i did it right, but it worked out for me

Hi guys! Working on a 17inch-MacBook Pro - so glad i got the last generation of the big fella, now that Apple got rid of the 17ers... In the office there is a 27inch TFT from NEC. Since we are three people in our small design office, there is an old MacPro working as a server. Why Mac? Well, got into print in 1996 and never looked back. Actually looked back from time to time, but not long enough to switch to windows or linux. Although I really like Win8-Style and the great karma of Linux.

@soma- I said invite. I really should have said "could". I did more additional research on this and G say's it won't and Matt Cutts debunked this a while back. I had seen googlebot on some dev sites and was sure they had not been shared. Could have been a tweet or some other crawled resource that shared it. I stand corrected. Note that they do collect URL's in chrome if you have Google as the default search engine (for typeahead or missing URL's), and in the Google Toolbar when "page rank" is enabled the URL's are phoned home. Just not shared . Yet

I think Ryan should start thinking about ProcessWire VIP to make some money out of his this awesome CMS/CMF. He can be millionaire in no time!

Welcome to the forums siulynot. If you are talking about replacing the H1 tag used to display the homepage headline with an image on the blog profile pages, then you would need to modify /site/templates/main.inc include file starting at line 60. <div id="site-headline" class="twelve columns alpha"> <?php echo "<a href='{$config->urls->root}'><h1>{$homepage->headline}</h1></a>"; ?> <?php if($homepage->summary) echo "<h5>{$homepage->summary}</h5>"; ?> </div> Example: You could add a span tag in the H1 containing the $homepage->headline , use css to move it out of the flow, and add a background image to the H1 tag in your css. Or get rid of the text and just use an image. Hope that helps.

Another ProcessWire site is online: http://www.christophkunz.ch I'm using the awesome blog profile as base. Today I showed christoph the Pw-Admin – so simple and easy to use, I think he'll love it. (The previous site was running on modx). Credits to ProcessWire here: http://www.christophkunz.ch/impressum/ Any feedback is appreciated, it's not 100% finished yet Cheers

You might find the attached LazyCronTest.module helpful. This basically just demonstrates LazyCron in action. Install this module after LazyCron is installed, and it'll record a log entry every 5 minutes (or so) to /site/assets/logs/lazytest.txt. That's assuming the site is getting non-cached pageviews so that LazyCron gets a chance to run. LazyCronTest.module <?php class LazyCronTest extends WireData implements Module { public static function getModuleInfo() { return array( 'title' => 'Lazy Cron Test', 'version' => 100, 'summary' => 'Tests lazy cron by writing to a log file in /site/assets/logs/lazytest.txt', 'singular' => true, 'autoload' => true, ); } public function init() { $this->addHookAfter('LazyCron::every5Minutes', $this, 'lazyTest'); } public function lazyTest($event) { $seconds = $event->arguments[0]; $log = new FileLog($this->config->paths->logs . 'lazytest.txt'); $log->save('LazyCron 5 minute test - ' . date('Y-m-d H:i:s') . " - $seconds seconds"); } } Here's an example of the log file it generates: 2013-02-02 11:19:02:LazyCron 5 minute test - 2013-02-02 11:19:02 - 356 seconds 2013-02-02 11:24:04:LazyCron 5 minute test - 2013-02-02 11:24:04 - 302 seconds 2013-02-02 11:31:52:LazyCron 5 minute test - 2013-02-02 11:31:52 - 468 seconds 2013-02-02 11:37:22:LazyCron 5 minute test - 2013-02-02 11:37:22 - 330 seconds 2013-02-02 11:43:14:LazyCron 5 minute test - 2013-02-02 11:43:14 - 352 seconds 2013-02-02 11:49:13:LazyCron 5 minute test - 2013-02-02 11:49:13 - 359 seconds 2013-02-02 11:54:37:LazyCron 5 minute test - 2013-02-02 11:54:37 - 324 seconds 2013-02-02 12:00:07:LazyCron 5 minute test - 2013-02-02 12:00:07 - 330 seconds 2013-02-02 12:05:07:LazyCron 5 minute test - 2013-02-02 12:05:07 - 300 seconds 2013-02-02 12:12:42:LazyCron 5 minute test - 2013-02-02 12:12:42 - 455 seconds 2013-02-02 12:18:35:LazyCron 5 minute test - 2013-02-02 12:18:35 - 353 seconds 2013-02-02 12:23:37:LazyCron 5 minute test - 2013-02-02 12:23:37 - 302 seconds 2013-02-02 12:30:54:LazyCron 5 minute test - 2013-02-02 12:30:54 - 437 seconds 2013-02-02 12:36:22:LazyCron 5 minute test - 2013-02-02 12:36:22 - 328 seconds 2013-02-02 12:41:57:LazyCron 5 minute test - 2013-02-02 12:41:57 - 335 seconds 2013-02-02 12:50:48:LazyCron 5 minute test - 2013-02-02 12:50:48 - 531 seconds 2013-02-02 12:56:58:LazyCron 5 minute test - 2013-02-02 12:56:58 - 370 seconds 2013-02-02 13:03:03:LazyCron 5 minute test - 2013-02-02 13:03:03 - 365 seconds 2013-02-02 13:15:03:LazyCron 5 minute test - 2013-02-02 13:15:03 - 720 seconds 2013-02-02 13:26:03:LazyCron 5 minute test - 2013-02-02 13:26:03 - 660 seconds 2013-02-02 13:31:46:LazyCron 5 minute test - 2013-02-02 13:31:46 - 343 seconds 2013-02-02 13:37:37:LazyCron 5 minute test - 2013-02-02 13:37:37 - 351 seconds Notice how the number of elapsed seconds is always more than 5 minutes (and sometimes a lot more). That's just because it has to be triggered by a PageView. In most cases, this is okay because a lack of pageviews usually means there's nobody there to see what was updated anyway.

Hi roelof, Welcome to the forums. ProcessWire is a very flexible and extremely powerful CMS, and I firmly believe it can be used to build all kinds of websites, from simple portfolio sites to highly complex news sites. In my experience, when it comes to PW, sky is the limit! As netcarver mentions, you need to be a little bit familiar with PHP to make the most out of it, but that doesn't necessarily mean you need to learn PHP before starting to use PW. In fact, I've found that using PW is in and of itself a great way of learning PHP. As long as you're able to understand the most basic PHP concepts, I think you can pretty much learn all the rest as you go. If you get stuck somewhere and need help, the community is here to help. So, my advice would be to give PW a try and see first hand what you can do with it. Best of luck. Claudio

Hi Matthew, sorry for the delay in replying. I have little experience with off-the-shelf solutions but know some people who like things like the drobo but I've never used it. Actually, it sounds like you are doing about 200% better with your current backup strategy than most people, probably myself included (currently I do a regular backup to an external, removable HDD and most of my development work goes onto github, if public, or bitbucket if private.) In the past I have setup RAID-1 arrays using FreeNAS on cheap-and-cheerful old boxes. I'd have the OS (which is FreeBSD based) running off a memory stick on an internal USB port and 2 matching sata drives hooked up directly to the motherboard. These boxes actually serve as a file server with backups handled onto external drives. There are, however, plenty of other products in the same arena (like UnRaid and NAS4Free.) FreeNAS works great and is pretty easy to configure, supporting many network storage options and even allowing ZFS if the box is powerful enough. There's always the possibility of failures in RAID but it comes down to managing risk vs the costs of not doing so. If you want to look at things like distributed storage then there are products like Gluster which allows having different storage nodes (one of multiple How-Tos courtesy of HowToForge.) For off-site storage there are multiple services to choose from starting off with a roll-your-own solution (like rsync to your own off-site server somewhere) to more bespoke products like Carbonite, JungleDisk and, more up my street, Tarsnap. You could even use dropbox if you didn't care a hoot about security.

..and just under four months later the wizard himself has over 2k likes! Didn't say it aloud myself when he hit the first thousand, so here goes: thanks Ryan! There hasn't been a moment of "nothing to do" for ages for me .

It's good to see the jobs board is working as intended

Hi Ryan, just saw this now. We're working with someone now who found out about the job from this post. We're excited to be working with someone who's got solid PW skills. Thanks for the offer anyway. Should we ever come across any PW work that mere mortals can't solve, we'll be sure to reach out

Aarrgghh! So frustrated that I need to build some functionality into another ecommerce system that would take 20 seconds in ProcessWire. I need to add a related products feature to a blog section - in the other software this means I likely won't be able to do it or will spend a week working it out. In ProcessWire it would be soooo easy. I'm going to make an effort this year to use ProcessWire for every type if site that comes my way - that way if I need to do some customisation I know it will be easy! I've now changed the title of this thread so I can vent my frustrations about whatever system I have to wrestle with to do what I need it to

Exactly. There are some words which (at least in my opinion) are a. very "established" in German, althought they are actually English b. don't really have a proper and common German translation Some of those might be "translated" anyway because they are spelled differently in German, though. For instance, most English people tend to write "email", the proper German form is "E-Mail".

Jeez, I just saw the paragraph stripper! Sorry to waste the bandwidth More senior moments. Chatting away to myself like this is the first sign of madness. I blame RoR.