Leaderboard

I said: I formulated this wrong, sorry. What I really meant is that this is easy to accomplice with the ProcessWire API. Examples: 'Redirect to the first child'. In MODX you need a module 'FirstChildRedirect', the ProcessWire way: $session->redirect($page->child->url); To get the highest parent of an page in the tree. In MODX, you could make it yourself difficult with code or install UltimateParent. The processWire way: $page->rootParent; Create a Gallery of images: In MODX you can install 'Gallery' and study the documentation. The ProcessWire way: echo "<ul>"; foreach ($page->images as $image) { $thumb = $image->size(100,100); // create thumbnail echo "<li>"; echo "<a href='$image->url'>"; echo "<img src='$thumb->url' alt='$thumb->description'>"; echo "</a>"; echo "</li>"; } echo "</ul>"; The template language of MODX is MODX only, outside of MDX this knowledge is almost useless. You don't need to know much PHP to get the 'same' results in ProcessWire. But if you drop ProcessWire for some reason, you've build some experience with PHP. And that is valuable.

Hi dupalski I think the problem is that whichever system you use, the minute you want to change the layout a bit you are still looking at code of one sort or another. Whether you're editing a snippet that comes with a MODx module (I forget exactly how it works) or you're writing one of Martijn's simple examples above you will see some form of code at some point. The thing is to not be afraid of the fact that in MODx it's abstracted away behind {{curly braces}} or [!other things]] whilst ProcessWire throws real PHP your way - they're both equally as simple to break, but it's infinitely easier in ProcessWire to do what you want out of the box (with a little learning - there's a learning curve with both so why not learn some actual PHP rather than abstract code ). I would recommend downloading and installing ProcessWire, and then looking at some of the tutorials - this is probably the most concise example that gets you going quickly with a guides through templates, fields and pages and if you understand those basics by the end then you'll have begun to unlock some of the power of ProcessWire and hopefully be eager for more! Some of the docs can look a little scary, but honestly if you know HTML and CSS then that's half of the battle - the tutorials can help you with a lot of the rest and doing it in ProcessWire you're not restricted to what the modules output for you in terms of HTML - as you can see in Martijn's example above of outputting images from a page that's pretty simple and you can apply whatever HTML and CSS you like around it without worrying about modules not getting update by their authors or things like that (disclaimer: they're all pretty up to date here, but I'd wager that not all of Wordpress' 1,355 gallery plugins are up to date - just an extreme example from another system there ). Following on from that disclaimer in the paragraph above, that example actually highlights how the number of modules doesn't necessarily mean much either if there are lots of the same thing or, as Martijn says, they are things that can be done in so little code in ProcessWire that they're not worth writing a whole module for. Every plugin/module in any system actually adds some overhead, whether it's parsing CMS-specific tags in other systems or getting basic information - it all adds a little to the server load or page load times. That said, using plain HTML will always be faster than using any CMS so there is always a trade-off no matter what you do. I think I might need to take a breath now Anyway, my suggestion would be to follow a tutorial, have a play and ask on the forums if you still have questions after that.

@Jan Romero: What version of PHP and MySQL are you running? You also mentioned 3rd party modules–which modules? (If not Textareas ProField?). The ProFields have been developed in tandem with the dev branch, so I'm fairly sure that wouldn't be it. But the commit you indicated did change the way module information is cached. I found one other instance of a similar upgrade error and we traced it to a bug in a specific PHP Version. That's why I'm curious about the versions of software you are running. I think this is largely the inclusion of CKEditor. The Iridium profile does take up some space since it has a lot of photos, so I may leave that one as an external install. Overall though, I think we're being pretty safe with file size. I can still download a ZIP from GitHub in less than 3 seconds, and we've never had any complaints that file size was preventing someone from trying or using PW. As a result, I think we're better off using file space where we can to make sure PW really impresses people when they download and try it out. On the other hand, we should also be safe and not include multiple RTEs, etc. For example, we removed TinyMCE when we bundled in CKEditor. There has been little demand for this, that's why it keeps getting pushed back. How many threads do you see posted of people asking for this capability? I agree it's a nice capability, and I would like it too. But I try and focus my efforts on what will get used the most. At least the non-sponsored new additions you see in 2.5 are largely based on what's been asked for repeatedly in the forums (as well as what I would personally find useful). So we'll count your request here as momentum for drafts. The funny thing is that PW1 had full drafts capability, had a huge amount of work behind it, and it worked well. The unfunny thing is that clients rarely used it. The primary time that clients (my clients at least) wanted a draft of something was when creating a page. That's why we've already got that in PW2. I ended up feeling that all the work behind drafts in PW1 was kind of a waste of time. Of course the PW2 user base is much larger and the potential audience for such a feature is much larger now. I personally would like to have drafts for already published pages too, but the reality is there's only a small segment that will actually take advantage of it. It's a feature that sounds good, but few use. Still, we may have the critical mass now for it to be worthwhile. And it's also on the checklist of many, even if they won't use it. I even have it mostly built already, and have been occasionally working on it, but it's been kept in the background as more popular features have gotten attention. I appreciate the interest of course, but I don't think this is necessary. We've already got commercial modules funding developing of ProcessWire. The focus on what gets added is also largely based on what are the most common needs people have around here, within the limits of feasibility and schedule.

Eheh, what a mess... I will try to answer anyway. I think no one said that all the modules are in the core, what was said is that what is on the core (there are modules on the core, but that's not the point here) is more than enough to build a site easily. Besides that, the few modules that exist (not so few anymore) are in average of high quality and mostly useful, comparing to other systems that have lots of modules that are unusable or of poor quality.

You can't compare mudule count between MODX and ProcessWire. ProcessWire is in first place a framework, while MODX is in first place a CMS. (MODX is called a CMF content management framework, but after working with it for more than a year, I don't know why they call it that way) With ProcessWire, we don't need gallery modules, modules to get the first child, modules to generate thumbnails, modules to find pages. These are all core in ProcessWire. This lack in the MODX core will automatically result in a much larger scale of modules. And if Module development was easier in MODX, I think the amount of modules in MODX was at least double in size. So counting Modules is not a fair comparison. The freedom in MODX is locked in chunks and snippets. These methods make it relative save for editors to use them in content fields. But it has huge drawbacks: - Snippet can only receive variables of the type string for example. - Logic in snippets etc is stored in database, this logic needs to be entered in the browser. (you could link in this snippet to an external file, but it still needs a page save to regenerate the cache. In MODX, it's the cache that get parsed by PHP, and if a parse error occurs, the line number of the error is not the same as the line number of the 'file' editted ) In the end the slogan 'creative freedom' fit's better for ProcessWire then for MODX.

Hello, So I'm working on a PW project in a shared hosting like Hostgator. For this to work you need ssh access, and of course git. I always have problems working with FTP, I feel my productivity decreases when using them, also you have no control over changes that are made. So a single file deletion could cause a big catastrophe. The first thing you have to do is cloning the PW repo, and checkout to dev branch Here we clone the repo, use the dev branch. Delete the entire PW git directory and initialize a new one $ git clone https://github.com/ryancramerdesign/ProcessWire/ $ cd ProcessWire $ git checkout dev $ rm -rf .git $ rm .gitignore $ git init $ git add . $ git commit -m "Initial Commit" Note: The file .gitignore from the dev branch have some files that you want to be commited, like /sites. I recommend deleting that file and create a new one. Ok, now we need to configure our remote repo inside the shared hosting. You need to login using a terminal. Linux and Mac have ssh already installed, if you are in Windows you can use Putty. ssh username@domain.com -p 2222 ... Enter your password: ********* Now we need to authorize our computer in the hosting, so we can push the commits. We need the contents of ~/.ssh/id_rsa.pub located our computer. A more complete guide for generating such keys is available here. Then we will copy the contents to ~/.ssh/authorized_keys. create the authorized_keys in the hosting if not exists using touch ~/.ssh/authorized_keys The next step is creating a new repo and configure some hooks in our server. $ mkdir www/processwire $ cd www/processwire $ git init $ git config receive.denyCurrentBranch ignore $ cd .git $ cd hooks $ touch post-receive The contents of post-receive hook should be. (this is a ruby script, but could be any language available on the server) #!/usr/bin/env ruby # post-receive # 1. Read STDIN (Format: "from_commit to_commit branch_name") from, to, branch = ARGF.read.split " " # 2. Only deploy if master branch was pushed if (branch =~ /master$/) == nil puts "Received branch #{branch}, not deploying." exit end # 3. Copy files to deploy directory deploy_to_dir = File.expand_path('../') `GIT_WORK_TREE="#{deploy_to_dir}" git checkout -f master` puts "DEPLOY: master(#{to}) copied to '#{deploy_to_dir}'" # 4.TODO: Deployment Tasks # i.e.: Run Puppet Apply, Restart Daemons, etc Now we make it executable using chmod $ chmod +x post-receive With all that done, we should enable a passwordless login so we can push without a password prompt on every push. In our local machine look for this file ~/.ssh/config And add this text (Change your-domain.com and port as needed) Host your-domain.com Port 2222 PreferredAuthentications publickey Now we should go to our project directory and add the remote host with $ git remote add hosting user@domain.com:www/processwire $ git push --set-upstream hosting master This should do the trick for commiting changes and upload files without ftp. Now we must install Processwire and then pull the changes. Go to your domain and start PW setup. once you are ready installing processwire, you need to pull changes that PW installer made. Login to your hosting via ssh and commit the changes that installer made. $ ssh user@domain.com $ cd www/processwire $ git rm $(git ls-files --deleted) $ git add . -f $ git commit -m "Initial PW Setup" When that is ready go back to your local machine and pull the repo. $ cd Processwire $ git fetch $ git reset --hard hosting/master Now we are finally ready to start working with PW in shared hosts or other machines that have ssh enabled. simply makes changes like $ touch site/templates/welcome.php $ git add . $ git commit -m "Added welcome.php" $ git push Now if you have some problems you can zip the setup using $ git tag -a v0.0.1 -m "Initial PW Setup" $ git archive --format=zip --output=pw.zip v0.0.1 And download the file and work from there Thats all References: http://www.arlocarreon.com/blog/git/push-git-repo-into-shared-hosting-account-like-hostgator/ http://ahmadassaf.com/blog/miscellaneous/how-to-use-git-to-host-and-push-projects-on-shared-hosting-services/ http://motorscript.com/setting-up-a-remote-git-repo-on-shared-server-like-hostgator/ http://krisjordan.com/essays/setting-up-push-to-deploy-with-git http://git-scm.com/book/en/Customizing-Git-Git-Hooks

Hey dupalski Just out of interest, what kind of features on your site do you think might need either Modules or Extras? I'm a long time MODX user who has just started using ProcessWire so I understand your question. To be fair to both systems, they're both terrific and you really can't go wrong by choosing either. Particularly with a site as small as you mention. You're not going to make a bad decision so just get stuck in. The only thing I would say is to eventually give each CMS a proper go. I know time restrictions mean you have to choose between either CMS right now and roll with it, but I've found each CMS works a little differently and has different strengths. Knowing both can only make you grow as a designer/developer and it makes no sense to me how some people choose *a* CMS and stick with it at the exclusion of everything else. I haven't replaced MODX as my CMS but am simply broadening my toolset. What I will say about PW is that since "joining", I've found the community to be incredibly helpful. MODX community is very helpful too. But what I particularly like about PW is how communicative Ryan (main developer) is about roadmap, features, the upcoming release etc etc. Good luck with the site.

https://processwire.com/talk/topic/6472-charleswuorinencom/#entry63522 https://processwire.com/talk/topic/6538-using-procache-with-wilcox-adaptive-images-plugin/page-2#entry64304

I'm glad to inform you that today I completed the rough translation for the latest PW dev branch, so the process turned to the correcting and testing phase.

The great thing about PW's reliance on real PHP for templating and everything else is that there are loads of really helpful resources to help learners and improvers - This forum and the PW main site PW-related resources by community members Teppo's FlamingRuby & Kongondo's site - and others And if you get really stuck/interested http://php.net/ and the myriad of other PHP resources out there. I would go as far as to say that there isn't a templating language/system that is anywhere near as well supported. <edit>Man, it's hard to post a link in here these days!</edit>

Such a line just makes me wonder a few things: "have you been looking in this forum about modx" ? "how long have you been on the modx forum" ? "history of modx evo" - "modx revo compared to processwire" - how many cms'es have you worked with ? You have not been working long enough with processwire. But hey being an ex modx-er my self I`ve been there exactly as you and I know very well it takes more time for a less experienced coder to grow into something like processwire. There is only one way and that is work a lot more with processwire and you will see it all for your self.

What I'm really missing and waiting in PW since the beginning are draft/live versions of pages, basicly more advanced workflow/publishing options. I feel this would be a lot more needed than all the new features we got. Not saying they're bad. I hope we get that with 2.5!

Not specifically about retina images, but rather responsive images in general and the polyfill for the new standard: http://css-tricks.com/video-screencasts/133-figuring-responsive-images/ Includes mention of providing a specific 2x version of images.

;) the same time i'll did my first module with your code and the hellowourld.module.......i like PW really!!! Did touch no line OOP Code before but in this case i've trust nothing to mess because all is logical!! Renamed my file to your suggested name and added as a zip file. other questions in the other topic now i wann learn how to add a textfield as option in the backend (now i'm hungry) i will post this on the second threat, too. Many thanks adrian for the hint and the example. ChangeImageSelectParent.zip

_func, _init and _main.php are files from the dev branch, in 2.4 there is the older structure with head.inc and foot.inc: https://github.com/ryancramerdesign/ProcessWire/blob/master/site-default/templates/home.php @dupalski the css reference is on line 24: https://github.com/ryancramerdesign/ProcessWire/blob/master/site-default/templates/head.inc#L24 are you familiar with browser debugging tools? they will help you a lot inspecting your code:

Separate things. One thing is to do a website with bootstrap, the other is to do a website with PW. What I mean is, you can do both in the same, but they are not dependent. My advice is, do the site in bootstrap (well, not all the website, but the main pages) and then apply PW to it (for this part we have more than enough tutorials)

http://processwire.com/docs/tutorials/ The only way to learn (that I know of) is to download, read up, and try out some code. Honestly, until you do this the amount of help anyone can offer is limited. Jump in the deep end bro.

#2 is correct. You do have to create modules (additional functionality) yourself. But you do not do it from ground up. ProcessWire provides you with capability to create custom content types, which consist of fields. Those fields are accessible via API. Those two features combined make possible the creation of functionalities usually provided by third-party modules elsewhere with a couple lines of code in the template file on the fly. You could build modules with admin interface, but it is not necessary in most cases. If you never coded a line in PHP it may seem hard (though it is not), but if you have not, MODx is probably not a right choice for you anyway. Just give it a try, go through a tutorial or two and then make a decision. If you do not want to code at all, go for something like Wordpress or Joomla or any of the other million CMS' out there.

I used modX heavily for 2-3 years and thought it was the bomb. When I found PW I realised modx was good but was not the holy grail I originally thought. Modules in PW seem to be a lot tighter than in modX - they just seem to work. But to be honest, I hardly ever reach for a module in PW - the core and brilliant API provide so much functionality that modules are often completely unnecessary for lesser complex sites. Community in both platforms is great, the difference is there is a core of extremely knowledgable people here at PW, and they are always willing to help. The willingness to provide assistance at the modX forum is also good and the users I found to be very friendly, but I found many users were not so knowledgeable and so the information provided was not of such a high standard. Sometimes actually just plain incorrect. These are just my observations, I hope they help. For the record, I really rate modX and it's developers, it's leagues ahead of many similar CMS/CMFs, but having now experienced PW for about a year I would not go back. No way. It's be like going back to using a 56k modem, so sad!

You can go for Language-Alternate fields.

In the roadmap I can see all the cool features are sponsored by someone. I just guess we could crowd-sponsor our own desires )) If it was possible to estimate, how much will it take to complete those "draft and live versions of any page" functionality, we could try to collect the money and get the common good. Just recently I took part in such an endevour related to Joomla. I can't say I got too much money to spend, but I'll surely find 5 to 10 bucks at least . It would be cool to see stated "this feature is sponsored by community". To not break Ryan's open source spirit down we could decide to sponsor definite amount of new functions per semester or so. We could also make some kind of voting on that, so we really take part in deciding, in which direction should this software develop. What do you think?

Thanks for all the replies guys, been a bit of an eye-opener for me. Some wonderful replies and perspectives. I'm definitely lagging behind developers in Europe/US in regards to design for mobile devices (and other screen sizes, thanks Teppo). Pete, I think you are right, New Zealand is certainly "laid-back" and probably a bit behind the times as a result. Most developers here still develop for IE7 (and some even IE6), which I suspect you guys don't stress over these days. Tablets etc are common here but certainly not to the extent of the US etc. Sinnut, Martijn etc, agree with your comments regarding CSS and frameworks and bloat. I've got some thinking to do regarding this subject. I'm now looking forward to attacking RWD, something I was always happy to avoid. It's great to hear what other developers are up to. I live in a small town in a country at the other end of the globe and as a result I don't get to mix with others in my field (other than in forums like this) so it's bloody good to get others perspectives on these thing. Cheers all

UPDATE: 14.09.2014 We've launched lightning.pw! Create a new ProcessWire site in under 30 seconds with lightning.pw . Our new service will help developers to work together on a new site, enable new ProcessWire users to explore the CMS and you can now easily test a feature or module. Our goal was to replace the long localhost setups so that you can instantly start developing. Features Current launch features: Create new ProcessWire sites Choose between ProcessWire 2.4 and 2.5 or the latest dev version Choose a profile on installation We setup a custom subdomain and will provide you a FTP login for file access ProcessWire works as expected. Every feature (except PHP sendmail) works. Install modules, write templates and create new sites as you wish Dashboard to manage multiple sites Upgrade (or downgrade) ProcessWire with a single click Free Hosting for module developers. Planned features: Save and use your own installation profiles Custom subdomain names github/bitbucket integration Create snapshots of your site Free integration of minimize.pw for image compression Pricing lightning.pw is free to use. You can buy credits to expand a site after the free usage timeframe of seven days. Credits start at 3€ per month but get cheaper the more you buy. If you develop a customer site for an average of 6 months, you would pay 15€ for the whole development setup. If you think the price is high, please notice that we don't want to oversell our servers and that we want to build further features. If you have developed a free module for ProcessWire, you can contact us to get free hosting for your showcase or development site. Bonus: You can use the coupon code PROCESSWIRE to get a free month. Just enter the code under the Payment section on the dasboard. About The first intention for this project was our own need for a simple development solution. lightning.pw is build with Ruby on Rails and uses a custom written ProcessWire installer. We worked hard to maximize security and stability of the service. We create a backup of every site every 12h and can scale within minutes if server load increases. You can ask questions here on the forum or follow us on Twitter for updates (and maybe coupon codes ) Try lightning.pw and tell us what you think. We appreciate every form of feedback! --- original post --- I will keep this short. We worked on a new project for the last couple of days. Instant ProcessWire hosting for development, testing and as a showcase for ProcessWire. The idea was on our mind for over a year, rested when the community won the bitnami contest but was finally started when we needed a better tool for our internal development. Excuse my bad mix of Englisch and German and watch the short video that explains and shows the basics: The features includeInstallation of any ProcessWire version in under 60 seconds Complete setup of a profile for ProcessWire, you can select the profile FTP access to the /site/ directory Login to ProcessWire with your lightning.pw account Own and custom subdomains Complete ProcessWire where everything works as expected Secured and fast server, restricted access and daily backups. Every site is free for seven days and will be deleted afterwards, except if you choose to extend the site with credits you bought. Module developers can host a showcase/demo for free. Our plan is to get the best experience for PW developers and small teams. Maybe it will help ProcessWire grow or maybe it will just stay a tool we use for our own sites. We have a github/bitbucket integration, custom profiles and an export workflow on our roadmap. We would be glad to hear your opinions and your feedback on this idea and the current execution. What feature would really make this attractive for you?

Thanks for posting this. Work flows like this are looked for by many. I think FTP is still ok when you map it as a drive in windows or mac.

Remember though that srcset is not available that widely available just yet: http://caniuse.com/#search=srcset So that link I sent you to mentions the picturefill polyfill that you'll need to get going with it now: http://scottjehl.github.io/picturefill/#getting-started

Here is a configurable version. Choose the desired parent page from the module settings: https://gist.github.com/adrianbj/437e3945e9d774f5a67e

So solutiion comes from adrian! her the code: https://processwire.com/talk/topic/3023-module-ckeditor/page-10#entry71664 and here a small module (Parent ID could changed in the modulefile) https://processwire.com/talk/topic/3023-module-ckeditor/page-10#entry71672 next step i will try and import from other modules is to get the setting of the ID in the backend.... PW is great and the people that drives this bus are greater!

I think you added the solution to the wrong post By the way, I updated my post to make it a complete working module for you! Of course this module could be extended to make the parent page selectable via the module's config settings.

This draft capability, would it work that way that when you edit (add/remove and /or rearrange) images on a page that is already published that these changes are not directly visible at the frontpage? This one is really odd and need some better handling IMO.

Thanks for the replies guys. really appreciate the help and the community of PW. currently youtubing bootsrap now, found a 2 hour long tutorial, gonna get deep into this now.

no way

Pressure huh? Have you thought perhaps it's time for a new GF? ;-)

I never used MODX, but based on the talks we had here in the forum I'm strongly convinced that this is not true. We have some heavy MODX ex-users here that may confirm—or not—this.As Martijn said, don't count the modules. I think one of the reasons PW doesn't have more modules is because people don't feel the need for them as much as in other system. You can do so much only with the core...

Hi guys For some reason I wasn't getting the latest dev version. I do now and all is well. I can add multiple tags now. Thanks a lot Kongondo & Adrian. You guys rock!

project_categories defalt referer to ID mabe.u meandet project_categories.title=123 or project_categories.name ?

if anybody stumbles over this thread, here is the correct function (also gebeer's version has got a $text/$summary bug): function truncateText($text, $maxlength = 200) { // truncate to max length $text = substr(strip_tags($text), 0, $maxlength); // check if we've truncated to a spot that needs further truncation if(strlen(rtrim($text, ' .!?,;')) == $maxlength) { // truncate to last word $text = substr($text, 0, strrpos($text, ' ')); } return trim($text); } thank you ryan

Can't get much simpler than this http://simplecartjs.org

As hdesigns said, NETWORKING is crucial to your survival! Everyone does things differently. Something may work well for YOU, but not well for ME. There will be lots of suggestions and recommendations from many people here that have been doing this job. Some of us have worked with established firms, others do it as a hobby. So the answers you get will be wild and various. With that said. I'll tell you how I operate. NETWORK If you are serious about this business, get some GOOD business cards made. Don't go cheap. Spend good money on some good high quality printed business cards. You should even go further and design them yourself! Show off your design skills with your first step! Hand someone your card, explain what you do AND mention that you designed your own card! Talk to friends and family. Let them all know your intentions. I have "scouts" all over town. Lots of my friends and family know what I do. To give them an incentive to send me clients, I give them a gift (to my friends/family) if they send me someone and I get them to sign a contract. Nothing big ya know. But something to show them I appreciate them helping me find work. I also give incentives to existing and past clients. I'll give them a discount on existing or future work if they send me a new client. It's a small price to pay to keep them happy AND not forget about me when the job is done. HAVE A CONTRACT!!! This can not be overstated! This will save your butt some day! It does not have to be full of legalese and dramatic courtroom jargon. Keep it simple but detailed enough to explain what your client expects from you. What you expect from your client. Estimated dates if possible. Outline the various milestones that lead to project completion. Define the payment schedule. Whether it be 50% deposit and the rest payable in time. Or one lump sum. Or your hourly billing fee. I have a small NDA clause in mine. NDA = Non Disclosure Agreement. There are times that I've charged a small fee. Other times I've billed higher. I don't want a past client to tell someone else how much they paid. Each client and website is different. Therefore their prices are different. You know: complexity, duration, etc. Also because you'll be conducting business with someone, there will be times you will be privvy to private business information that your client doesn't want others to know. You should know enough to get the job done. No more. No less. Well. That's how I've done things. COMMUNICATE As a part of my contract, I state that I will reply to all emails within 24 hours. I like to maintain ALL communication via email. I am strict about that. No colored bold or italic fonts with hearts and smiley faces. They are NOT to call me. Nor text me (unless it is an emergency). I like to have a trail that can be followed between all involved parties. That way, IF things should go poorly, I have something to protect ME, with peoples names, times and dates. Who said what, etc. WORKSTATION You probably won't have anyone mention this. You may have the idea of working from home. If so, invest in a comfortable chair, nothing too expensive. But you'll spend hours in this seat. Set your monitor at the proper height and distance to minimize eye strain. Eliminate distractions. Stop browsing Facebook. Set your phone to silent. Set your desk/station against a wall instead of a window. Avoid that distraction. Follow an agreeable work schedule. For every 25 minutes of straight work, reward yourself with a 5 minute break. Or 50 minutes of work and break for 10. Do what feels best. Make sure you stretch your arms, back, wrists, etc. Carpel tunnel is a terrible terrible pain. Just because you'll work from home. Avoid the tendency to work in your pajamas. SUIT UP! Work for yourself like you are working for someone else. Start at the same time every day. End at the same time every day. I used to take my kids to school. On the way home, I would stop for a cup of coffee and a danish at my favorite little place. And take my cup of coffee and danish to my work station at home. I was at my desk at the same time every day. It sounds silly, but it enforces good work habits. Best of luck to you!

Greetings, I don't doubt that the three choices are the result of a legitimate nomination process. I'm saying that if that process leads to only three choices for "Best Free CMS" it's not a very useful contest. In general, one of the problems I see in the CMS world is that systems like ProcessWire and Joomla/Drupal/WordPress are constantly put into the same category, when they are essentially different types of systems. And since CMS Critic has a mission of exploring the complexities of the CMS world, I think they should embrace their role as an analyst of CMS choices, and focus on articles exploring the dimensions of the CMS world. Contests like this just add confusion and misunderstanding. EDIT: I don't see how grouping CMSs based on whether they are "free" is generally useful. Why not group them according to logo color theme? Thanks, Matthew

Just had nice session with new installer (localhost, win7, wamp), also tested new db backups module. Everything worked very smoothly!

Is 2.5 the greatest PW to date or what!?! Great additions Ryan!

Yes, that what I mean when I said "custom profiles". Create a site, export the profile and then say lightning.pw "use this as a profile". But this will be a feature in the near future, not at launch.

For anyone that has the map hidden initially before being opened resulting in bad rendering of the map. I tried the following that was mentioned here on this post but with no success. After a while(2 hours ) scratching my head I changed it to the following: setTimeout(function() { google.maps.event.trigger($("#mgmap1")[0], 'resize'); mgmap1.map.setCenter(mgmap1.options.center); }, 250); Now works perfectly.

This thread is used as a place to collect: 1. links to posts in the forum answering (repeating) newbie questions 2. links to posts in the forum and elsewhere on the net giving good insight in processwire 3. links to good articles about processwire 4. links to good tutorials posted in the forum 5. links to movie clips 6. links to posts in the forum talking about modules 7. code snippets or links to code snippets 8. Usefull Helpfiles Many good posts that answers (repeating) newbie questions or give good insight in the how and why of processwire, links to tutorial posts, (also on the net), movie clips, clarifying articles and code snippets are spread over the forum. PM me if you know a link. About this kick start see this post: http://processwire.com/talk/topic/4143-wordpress-dominates-19-of-the-web/page-2#entry40910 This is a work in progress, it takes time to make it grow bigger and better. = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = STARTING NEWBIES AND DESIGNERS Link1: Starting and growing with processwire. https://processwire.com/talk/topic/3990-another-simple-photo-gallery-tutorial/page-4#entry61069 Link2: I am basically a designer with some programming skills. My question is this: Can I go ahead to use processwire for this even though i am still learning php. http://processwire.com/talk/topic/3954-starting-out-with-website-intranet-and-internet/ Link3: Feeling overwhelmed http://processwire.com/talk/topic/3215-newbie-overwhelmed/ Link4: Questions concerning PW and it's capabilities http://processwire.com/talk/topic/1557-questions-concerning-pw-and-its-capabilities/ NEWBIES FIRST CODING QUESTIONS link1: Using a default install, I'm stepping through the tutorials, templates, etc and trying to understand the basic concepts behind processwire and at this point in time "head.inc" & "foot.inc". http://processwire.com/talk/topic/3421-footinc/ Link2: I am puzzled why some html tags are starting in head.inc but don't end in head.inc Instead they are ended in foot.inc http://processwire.com/talk/topic/3388-question-about-headinc-and-footerinc/ Link3: Question about not using ?> in processwire http://processwire.com/talk/topic/3370-question-about-missing/ Link4: After you installed processwire, it comes with a default website. What is the best way to fill in your own website ? How do you replace the default processwire website with your own ? http://processwire.com/talk/topic/3379-how-to-fill-in-your-own-website/ Link5:How much extra work/time will I have to put in, as far as understanding and writing php and getting the hang of the PW system, just to be able to create the same responsive designs I would make in HTML/CSS/Javascrip, while also achieving the easiest type of content editing capabilities (in line with what you can get with a CushyCMS type product)? http://processwire.com/talk/topic/3961-new-to-cms/ Link6: I realize what I am confused about was really something quite basic, such as where are the snippets of php code go beside on templates? Can they go on a page as the value of body field for example? http://processwire.com/talk/topic/3383-back-to-basic/ Link7: I'm stuck in something that should be very simple. http://processwire.com/talk/topic/3720-my-first-doubt-using-pw/ Link8: Several questions before I can start. http://processwire.com/talk/topic/3589-several-questions-before-i-can-start/ PROCESSWIRE CMS INSIGHTS Link1: Reading this thread makes you understand processwire real quick. http://processwire.com/talk/topic/5667-help-a-noob-get-started/ Link2: Very good case study from RayDale giving good insight in processwire http://processwire.c...a-a-case-study/ Link3: Symphony or Processwire ? Another good insight. http://getsymphony.com/discuss/thread/79645/ ARTICLES Link1: Why he choses processwire over modx http://www.mademyday.de/why-i-chose-processwire-over-modx.html COMING FROM MODX ? Link1: You've been using MODX but now you've found ProcessWire. It’s totally amazed you and you can’t wait to get started. But…you are wondering where everything is. If this is you, read on… http://processwire.c...ning-from-modx/ Link2: A MODX refugee: questions on features of ProcessWire http://processwire.com/talk/topic/3111-a-modx-refugee-questions-on-features-of-processwire/ Link3: Code comparison between modx and processwire. http://processwire.com/talk/topic/2850-processwire-for-designers/page-2#entry30349 COMING FROM DRUPAL ? Link1: How to move your site from Drupal to ProcessWire. http://processwire.c...ndpost__p__8988 PAGES IN PROCESSWIRE Link1: Understanding pages in processwire http://processwire.com/talk/topic/5667-help-a-noob-get-started/page-2#entry55820 Link2: More about the function of pages in processwire http://processwire.c...fused-by-pages/ Link3: How to hide Pages from the Topnavi via Adminmenu http://processwire.com/talk/topic/2037-how-to-hide-pages-from-the-topnavi-via-adminmenu/ TEMPLATES IN PROCESSWIRE Link1: A good post with code examples to start a template http://processwire.com/talk/topic/43-template-tutorial/ Link2: Template design a better route http://processwire.com/talk/topic/2782-template-design-better-route/ Link3: A different way of using templates http://processwire.com/talk/topic/740-a-different-way-of-using-templates-delegate-approach/ FRONT-END / BACK-END Link1: ProcessWire Setup and front-end editing made easy http://processwire.com/talk/topic/2382-processwire-setup-and-front-end-editing-made-easy/ Link2: Creating a front-end admin http://processwire.com/talk/topic/2937-creating-a-front-end-admin/ Link3: How would I build functionality and write information from the front-end to the back-end? http://processwire.com/talk/topic/2174-writing-from-front-end-to-back-end/ Link4: Is it possible to create a custom login page like a template ? http://processwire.com/talk/topic/107-custom-login/ Link5: A "members-only" section in the front-end. Integrating a member / visitor login form http://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/ Link6: Trouble deleting pages from the front-end. http://processwire.com/talk/topic/2290-trouble-deleting-pages-from-the-frontend/ MODULE Front-end Edit. It turns the content of $page->body into a clickable area and gives the ability to frontend edit the content via tinyMCE http://processwire.com/talk/topic/3210-module-frontend-edit https://github.com/Luis85/PageInlineEdit/ MODULE Fredi, friendly frontend editing. http://processwire.com/talk/topic/3265-fredi-friendly-frontend-editing/?hl=fredi http://modules.processwire.com/modules/fredi/ MODULE Admin-bar Provides easy front-end admin bar for editing page content in ProcessWire 2.1+. http://processwire.com/talk/topic/44-is-there-way-to-get-information-about-current-user-in-templates/ http://processwire.com/talk/topic/50-adminbar/ http://modules.processwire.com/modules/admin-bar/ MULTI LANGUAGE WEBSITE IN PROCESSWIRE Link1: Multi-language website page names / URLs http://processwire.com/talk/topic/2979-multi-language-page-names-urls/ Link2: API http://processwire.com/api/multi-language-support/multi-language-urls/ Link3: The name of the default language can't be changed in Pw, but the title. http://processwire.com/talk/topic/4145-recoverable-fatal-error/#entry40611 ADD NEW USER TO YOUR WEBSITE AND PASSWORD RESET Link1: Integrating a member / visitor login form http://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/?hl=%2Bpassword+%2Breset#entry15894 Module http://processwire.com/talk/topic/2145-module-send-user-credentials/?hl=%2Bpassword+%2Breset BASIC TUTORIALS FOR NEWBIES Link1: Approaches to categorising site content http://processwire.com/talk/topic/3579-tutorial-approaches-to-categorising-site-content/ CODE SNIPPETS AND FUNCTIONS Link1: Get page id from images object https://processwire.com/talk/topic/6176-get-page-id-from-images-object/ Link2: Function to render Bootstrap 3 carousel markup from ProcessWire images object https://gist.github.com/gebeer/11200288 .HTACCESS EXAMPLES ON YOUR HOSTING SERVER Example1: A working .htaccess file. The issues were that the .htaccess file must exist on the server before installing processwire and that the server did not allow options in the .htaccess file. After fixing that processwire could be installed on the server without any problem. Note that such restrictions might be different on your server that you need to find in the faq of your host. RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php?q=$1 [L,QSA,NC] HTML KICKSTARTER Link1: How can i integrate HTML Kickstarter with processwire? http://processwire.com/talk/topic/2731-how-can-i-integrate-html-kickstarter-with-processwire/ MOVIE CLIPS Field dependencies are coming in ProcessWire 2.4. Field dependencies are basically just a way of saying that one field depends on another. It dictates which fields should be shown in a given context. https://www.youtube.com/watch?feature=player_embedded&v=hqLs9YNYKMM HELP FILES Cheatsheet Link1 Cheatsheet 1.1 as pdf file Download: http://processwire.com/talk/index.php?app=core&module=attach&section=attach&attach_id=1299 Link2 Cheatsheet is now a processwire site (great work by Soma) http://cheatsheet.processwire.com/pages/built-in-methods-reference/pages-find-selector/ INTERVIEWS Link1: About the history and coming to be of processwire http://processwire.com/talk/topic/4084-about-ryan-and-processwire-an-interview-with-ryan-cramer/

A few new/minor additions on the dev branch: You can now paginate with "limit=1" selectors. Previously ProcessWire didn't build the pagination information when a limit of 1 was specified. Now it does. ProcessWire now preloads pages that it knows it's going to need on every request. This speeds up everything slightly, as what was previously done in 6-7 queries is now done in one shot. Should you want to, you can also specify additional preloaded pages, though I don't think many (any?) would need to. Several optimizations to the PageFinder engine which improves the speed of certain types of queries. One of them is a $pages->count("selector") query, which is now even faster than before. Selector Grouping Added support for selector grouping to change the behavior of how they match. This is best explained by example. Lets say we're building a big news site, and we have a template called news-item that represents each news article. Each news-item page has a field called cats that is a multi-page reference to one or more category pages. This is a pretty common scenario in ProcessWire. The site has a lot of categories, so want to designate some categories as featured so that we can display featured categories on the homepage and elsewhere, with accompanying news items. Rather than just adding a featured checkbox, we add two fields to represent the date range that we want them featured: featured_from and featured_to. On our homepage, we want to display articles from all the current featured categories, so we build a selector like this: $items = $pages->find("cats.featured_from<today, cats.featured_to>=today, sort=-date"); ...but we end up with more news-items than we expect, including some that have categories that aren't actually featured right now. Why? Because each news-item can have multiple categories, and that selector above is saying this: The keywords there are "at least one", as "categories.featured_from" and "categories.featured_to" may not be referring to the same category. The only way to solve it was this: $categories = $pages->find("template=category, featured_from<today, featured_to>=today"); $items = $pages->find("categories=$categories, sort=-date"); That's easy enough... but now you can also do it like this, by prepending an @ to identify a group: $items = $pages->find("@cats.featured_from<today, @cats.featured_to>=today, sort=-date"); The "@" symbol at the beginning of "cats" is telling ProcessWire those are grouped together and "these must match the same exact page". This was added because there are situations where you need to perform your query with 1 selector rather than breaking it up. An example would be when used with the new InputfieldSelector module and Lister, among others. We will likely be adding more ways to perform complex matching scenarios with a single selector as well. Currently this "@" grouping applies only to multi-page reference fields, as I'm not sure yet where else it might be useful. It is only supported by selectors that hit the database at present (though will be completing it for in memory selectors as well). Not planning to extend it into that area at this time, but good ideas to think about for the future or for modules. It should already be fixed. If we're talking about the same thing, someone recently posted this to the GitHub issues list and I added their fix on dev. Adrian already knows this because we've been chatting in the GitHub issues queue, but for anyone else reading this, it has also been fixed.

I've added a feature on the 2.4 dev branch that several people have asked for in the past: 1-step adding of pages. To enable it: edit the template used by the parent where you want to support 1-step adding of children. In the 'Family' tab, in Allowed template(s) for Children choose the single template you want to be used for children. Once you do that, you'll see a new box appear below it, titled Name format for children. You can enter any text that you want here, and the page names will use it. If the name causes a collision with another page, then an incrementing number will be appended. You can also enter just the word title if you want it to base your page name on the title field (when you later populate it), or you can enter a PHP date format to base the page name on the current date and/or time. More details This screenshot explains it all. Look at the "Allowed template(s) for children" field and the "Name format for children" field. There are drawbacks to 1-step adding of pages, which is the main reason we've not supported this in the past. The biggest drawback is that you can end up with a unused pages due to accidental clicks on an add page button. To reduce this problem ProcessWire assigns a temporary status to pages created this way (Page::statusTemp) that gets removed as soon as you save it the first time. Pages that remain statusTemp will be automatically moved to the trash after having that status for 1+ days. Of course, pages created this way also have Unpublished status, so they aren't going to be showing up on the front-end of your site until you publish them (like any other page you create). The second drawback is that you are skipping over the page naming step, so pages have to be named automatically (which is what the Name Format you specified is for). Of course, you can easily change the name to whatever you'd like from the 'Settings' tab of any page. I've removed that drawback by adding the "title" option. When used, it populates your page with a temporary name and then re-populates it with your page title when you save. For most situations, you'll probably still want to stick with the 2-step page adding process. But for situations where you'd find it worthwhile to have 1-step, you now have the option.

Slideshows can get complicated quickly. Especially when serving different image sizes and resolutions like the example above. Then you can start intermingling video slides, and well, the rabbit hole goes further and further... I only look smart because I hang around here and absorb everyone's great examples. So, you are doing the right thing.

Further down the rabbit hole…. A function for responsive (retina) slideshows using Filament Group's responsive carousel and picturefill function slideshow(){ $page = wire('page'); // Resposive Carousel from Filament Group // https://github.com/filamentgroup/responsive-carousel $out = "<div class='carousel arrows' data-paginate data-autoplay data-interval='8000'>"; foreach ($page->images as $image){ // create required images sizes (based on 16:9 aspect ratio) //large $large = $image->size(920,518); $large_2x = $image->size(1840,1036,array('quality' => 25)); //medium $medium = $image->size(720,405); $medium_2x = $image->size(1440,810,array('quality' => 25)); //small $small = $image->size(540,304); $small_2x = $image->size(1080,604,array('quality' => 25)); //extra small $xsmall = $image->size(300,169); $xsmall_2x = $image->size(600,338,array('quality' => 25)); // serve 2x thumb to all devices $thumb = $image->size(200,106,array('quality' => 50)); $out .= "<div data-thumb='{$thumb->url}'>"; $out .= "<span data-picture data-alt='{$image->description}'>"; // extra small $out .= "<span data-src='{$xsmall->url}'></span>"; $out .= "<span data-src='{$xsmall_2x->url}' data-media='(max-width: 399px) and (min-device-pixel-ratio: 2.0)'> </span>"; //small $out .= "<span data-src='{$small->url}' data-media='(min-width: 400px)'></span>"; $out .= "<span data-src='{$small_2x->url}' data-media='(min-width: 400px) and (min-device-pixel-ratio: 2.0)'></span>"; // medium $out .= "<span data-src='{$medium->url}' data-media='(min-width: 800px)'></span>"; $out .= "<span data-src='{$medium_2x->url}' data-media='(min-width: 800px) and (min-device-pixel-ratio: 2.0)'></span>"; // large $out .= "<span data-src='{$large->url}' data-media='(min-width: 1000px)'></span>"; $out .= "<span data-src='{$large_2x->url}' data-media='(min-width: 1000px) and (min-device-pixel-ratio: 2.0)'></span>"; // Internet Explorer 8 and older have no support for CSS3 Media Queries // serve large image to older version of IE desktop. $out .= "<!--[if (lt IE 9) & (!IEMobile)]>"; $out .= "<span data-src='{$large->url}'></span>"; $out .= "<![endif]-->"; // Fallback content for non-JS browsers. Same img src as the initial, unqualified source element. $out .= "<noscript>"; $out .= "<img src='{$large->url}' alt='{$image->description}'/>"; $out .= "</noscript>"; $out .= "</span>"; // end picturefill // use image description field to generate a caption $out .= $image->description ? "<div class='caption'>{$image->description}</div>" : ""; $out .= "</div>"; // end slide } $out .= "</div>"; // end carousel return $out; } In your template <?php // render slideshow if there are images if (count($page->images) > 0){ echo slideshow(); } ?> *gah, formatting got a little mangled in the forum. You get the idea.

Or difficult like this: echo $page->images->implode(function($item) { $large = $item->size(1200,800); $thumb = $item->size(400,300); return "<li><a href='$large->url'><img src='$thumb->url' alt='$item->description'></a></li>"; }, array('prepend' => '<ul>', 'append' => '</ul>'));

Hi Folks, I just added a small module that keeps track of search keywords encoded in http referrers from common search engines leading to your site. See the README for a full documentation of features. Please let me now, if you have found any issues, feature requests or opinions by leaving your comments here in the forum or on github. Regards from Hanover, Germany, Marco