Leaderboard

That modules issue mentioned above should be fixed now, though let me know if you still experience it. A few interesting mid-week updates for those following ProcessWire 2.5 development (aka the dev branch). Here are links to the blog post about it: The ProcessWire installer now lets you choose a site profile New site profile exporter is far better than the previous Support for append/prepend files on a per-template basis With ProcessWire 2.5 getting very close to release, we could especially use help testing out the new installer if anyone wants to give it a try.

Post #2000! Better be good! Better be big!! Thanks for waiting ...what? It's only been 1 year . Finally! Some tutorials are up! OK, for now, it is my Blog module's documentation. Hey, that's not cheating! Don't laugh . Meanwhile, I also refreshed my website (how can you refresh an empty house you say? hehe - but it now has content. Nuh, for real, it has content). Toned down on the narcissism as well. Updated first post. Next lessons by great public demand - "Process Wire Modules!" Cheers/k

@Ivan Gretsky, I will. It will probably be a few months before that happens. I currently have a second generation prototype working with a few of my clients now. PW is proving to be a great platform for doing that type of thing.

Here's a real word example. $base_url = $_SERVER['SERVER_NAME']; switch ($base_url) { // LOCAL CONFIG case "mytestsite.dev": $config->dbHost = 'localhost'; $config->dbName = 'mytestsite'; $config->dbUser = 'user1'; $config->dbPass = 'PaSsWoRd1'; $config->dbPort = '3306'; $config->debug = true; $config->httpHosts = array('mytestsite.dev/', 'www.mytestsite.dev/'); break; // LIVE CONFIG case "mylivewebsite.com": $config->dbHost = '127.0.0.1'; $config->dbName = 'mylivewebsite'; $config->dbUser = 'user2'; $config->dbPass = 'pAsSwOrD2'; $config->dbPort = '3306'; $config->debug = false; $config->httpHosts = array('mylivewebsite.com/', 'www.mylivewebsite.com/'); break; } I have that in my config.php file. I can now freely make all my changes off line without fear of messing something up. Then all I do is dump and copy/paste the database.

Take what Antti said, replace 90% with 99.9% and you've got my opinion. Anyway, reading this made me cringe; if that's your idea of responsive design, I'm not surprised at all to hear that you're not very impressed with it. Take a look at the RWD patterns library collected by Brad Frost and you might get a better idea of what it's actually about.. or listen what Google has to say about responsive design fundamentals. (In a way you might be right, as that's really what a lot of people are doing -- but that's just because they're doing it wrong. RWD is all about making things usable and future proof regardless of resolution, window size, (physical) screen size etc.) By the way, I liked your sites. Keep up the good work!

I agree with everyone about RWD, however I also agree with things that @muzzer says. First, content will always be king. A great looking website means nothing without good content. RWD, SEO and a host of other things cannot replace content that is specific to whatever the website is about. Secondly, the customer pays the bills. We can create all these gee wiz bang websites, however someone (the paying client) needs to be satisfied with your work. Ultimately, they are the only ones who count, no matter what their artistic tastes are. I support anyone who has the tenacity to spend their time and resources creating websites. Some people are more talented than others, but we all deserve appreciation for doing what others haven't done. I honestly believe the only websites that I would never support are the ones that have music playing as soon as you arrive at the site.

What you could do (without making a mess) Make a hidden page in you site tree as suggested, but the difference: give it a logical name like 'preview'. This 'preview' page should have it's own template, call it preview or something and enable url segments. On pages that you want to be previewed ad a FieldtypeTextUnique field, call it 'preview_code' or whatever you like. Now on the hidden preview page something like this: <?php if (count($input->urlSegments) !== 1) { throw new Wire404Exception(); } // get your page to preview $preview = $pages->get("preview_code=" . $input->urlSegment1); if (!$preview->id) { throw new Wire404Exception(); } else { echo $preview->render(); } ps, not tested Now you're able to give someone an URL like: www.domain.ext/preview/vxrj9w765omxhg87g975ghu/

Back at my desk again, and thinking through this properly - I think the better option is actually: $np->images->add($p->images->last()->filename); You either need the full URL or the full disk path. I think that is where you were having trouble. In my first example, it wasn't working without the 'http://'.$config->httpHost part, but using "->filename" works great and is cleaner!

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?

@cory_dobson, welcome to PW and the forums . Glad you sorted it out. For your other issue, see this troubleshooting guide: http://processwire.com/docs/tutorials/troubleshooting-guide/ It's probably an .htaccess issue.

http://www.schumacher-visuell.de/blog/processwire-usability-cms/ (in German, but Google translates nicely to English).

With you declaring yourself as pw noob I would strongly suggest, to give pagetables another try as this would be the far easier solution. From your post I assume that you're using the FieldtypeSelect module right now. This is a easy to begin fieldtype, but not very flexible. In your case you've to use the Page fieldtype. This is a type where you save a reference to the choosen page. This fieldtype can also be displayed as a select box, but also provides other input solutions. The setup I would suggest would be: Page Setup: - Positions - … - Players - … - Games - Game 1 (game) - Line-Up Player 1 (lineup) - Line-Up Player 2 Template: lineup This template holds at least the first two fields below. With a custom naming convention you can define, you prevent the need of defining a custom name each time you add a page of this template. Fields: player PageField Here you can use the "custom php code for selectable pages" which is a option for that fieldtype: $players = $pages->find("template=PLAYERTEMPLATE"); // All Players $other_lineups = $page->parent->children; // All other Subpages, where Players are already choosen // $page is one of the subpages, therefore the parent selector part foreach($other_lineups as $lineup){ $players->remove($lineup->player); // Remove unavailable Players } return $players; // Return the adjusted selection position PageField Also use the custom php code, and just adapt my previous example for positions. lineup PageTable This pagetable is viewed in the game-template and let's you generate the lineup template, which should be used for the subpages of a game. The PageTable can show player.title and position.title in it's shown table, so you do have an overview in the game template, without the need to look into every subpage. With this setup everytime you add a new lineup subpage to a game, it removes already used positions and players from the fields.

I guess this is why I have an ongoing philosophical problem with frameworks... the basic aspects of responsive design are really not that difficult to understand, but by using frameworks, people are just bypassing that essencial understanding and accepting some limitations that are imposed to them. In essence, making a website responsive is not much more difficult than rearranging a bunch of photos in different physical formats (with the advantage that you can also change their size) and registering the movements that are needed from one form to the other. Only thing to keep in mind is: with CSS you can change the horizontal order of elements with floatings, but not the vertical order -> that's actually the only limitation. Ok, I'm drifting away from the thread theme, I'll stop here and focus on that Oh, @muzzer your sites don't seem to be working right now, getting a 502 on all of them.

I could suggest using this or this module to send mail via SMTP instead. They are very easy to use and extend WireMail class which is future-proof as it will be used in PW 2.5 core. They work only in dev version though. The links are the same as in Martijn's post, don't bother to compare ))

Welcome Varma, I don't know PHPMailer, but we have 2 modules to send over SMTP. You can use them. WireMailSmtp WireMailSwiftMailer

Blog documentation up on my website. Focused on MarkupBlog. Decided to do them as PW lessons (hehe - kill 'em with one stone!)...99% done - just have to do some example Blogs. Thanks for being patient! <btw>Next lessons up - 'ProcessWire modules'. </btw>

I've got a friend who lives in New Zealand and he says he wasn't joking about IT in general being a bit behind the times there when he took his dual core PC over there a couple of years ago, so it's not really surprising that customers there aren't wanting cutting edge. Not sure if this is still the case - this was just his observation when he emigrated and took his old-ish PC with him that due to cost people are a bit slower than other countries upgrading to the latest and greatest all the time - I'm not sure and it might just have been a local thing to where he moved to. No insult intended there, that was just the impression I was given and it does sound way more relaxed and chilled out too - I'm envious whenever he posts photos on Facebook I agree with doing what clients want though. It's a pain, you might not like it, but if they really want it a certain way then unless it's going to take you longer in terms of time then you have to give in at some point and just go with it. I was very late to the responsive design party but with the likes of Foundation and, more recently, UIKit it's not difficult to design a responsive site any more (I never got on with Bootstrap for some reason, probably because every man and his dog was using it ). Heck, I've only recently started saving myself time using SASS - though on a basic website the time saved might be a few minutes, it can add up over a year or quicker on more complex projects. My experience with responsive design is that it was once hard for me to understand and now with so many good frameworks I don't need to understand it as much, plus you have an excellent foundation (no pun intended) to build from so you can actually build quicker than normal. It takes a little while to get used to, but those few hours will be time well spent. I'm now building responsive sites almost by accident - using either of the frameworks I linked to you can focus on the desktop version and chuck in a few extra classes to make it do different things at different screen sizes later, or do it as you go along with very little effort. Sorry - I went on a bit longer than intended there but yes, it's worth looking into. I wouldn't say at this stage there's much you could do (or want/need to do) but it's worth bearing in mind if they want to update/refresh further down the line.

Hey, I would love to have something like $config->defaultTemplateFile in the config.php. What it should do: If set to "true" every template (except admin of course) should use the defined template file instead of its own. If you want to use another file (or the default file like page.php for page) you have to define it as "alternate template filename". Advantage: It's great if you're using a ajax driven site if you don't have to set every template to use e.g. "main.php" or "app.php" or whatever. What do you guys think? -- Nico

Added a few new sites from New Zealand to the PW directory. Real MTB Adventures Uncharted Wilderness Tours Springlands Veterinary Centre PW has made building these sites super-easy. Two of the above include tour booking systems made with PW pages and PW API, all very simple to implement. Loving working in PW. The above are very basic sites, but I'm especially enjoying developing more complex sites utilizing the slick API, creating and amending pages on the fly, dynamically creating PDFs, booking and listing systems, and credit/debit registers . It just works so nicely

Hi all, I've finally managed to set up my website where I intend to post ProcessWire tutorials. The site (lessons) is very much WIP. I have tried to make the site as responsive as possible. I have only tested in Chrome and FF. I'd rather write more lessons than test in IE to be honest so I won't pursue that... I will try to post regularly but can't make any promises as to the frequency . I intend to randomly post some pre-planned lessons. I will update this forum post everytime I post something new. If you have questions, pointers, etc about any lesson, or a request for a specific lesson, please post them here. This way, other forum members can assist in answering the questions . Thanks. /k ==================================================================== Edit: 28 August 2014 - Fist Tutorial is up (OK, it's Blog Module documentation ) Creating a Blog in ProcessWire (Blog Module how to) - 28 August 2014 [99% done] Next: 'All you ever wanted to know about ProcessWire Modules [and other cool things]' - COMING very SOON

Awesome!! Export / Import teamplates & fields. Section modules remember the last tab. You can add modules from anywhere. The find section, wow!. And a solution to the huge images that collapsed your screen. I created a module that is no longer needed The heaven in my hands Thanks @ryan

public function ready(){ if(wire("page")->template == "admin") return; wire("page")->template = "ajax"; } done. Not sure about consequences. Page viewable is set by if template exists or not.

+11. Nope, not a typo -- just how much I want this to happen. I'm not much of a fan of AJAX driven sites, but I do tend to implement template level front controller pattern to all the sites I work on. Being able to route all requests to specific file without having to define that file separately to each and every template as an alternate template file would be very, very nice addition.

Or this are nice tool for colors. http://www.dasplankton.de/ContrastA/ https://kuler.adobe.com/de/create/color-wheel/ http://colourco.de/ (Just was trying to find an color palette tool I used year or two ago.)

Try something like http://snook.ca/technical/colour_contrast/colour.html I don't have an issue on my imac pro retina.

I like your first green

new german updates for actual PW dev 2.4.15 (28 August 2014). Zip contains only updated/added files (in comparison to the default 2.4 lang pack). updated files: wire--modules--process--processfield--processfield-module.json wire--modules--process--processforgotpassword-module.json wire--modules--process--processmodule--processmodule-module.json wire--modules--process--processrole--processrole-module.json wire--modules--process--processtemplate--processtemplate-module.json wire--modules--process--processuser--processuser-module.json added files: wire--core--fieldselectorinfo-php.json wire--core--fieldtypemulti-php.json wire--core--process-php.json wire--core--sanitizer-php.json wire--modules--inputfield--inputfieldpagetitle--inputfieldpagetitle-module.json wire--modules--languagesupport--processlanguage-module.json pw-lang-de-dev-update.zip

specify each sort separately, e.g. $pages->get('/mypage/')->children('sort=-date, sort=created'); That will first sort by 'date' then by 'created' It's all documented here: http://processwire.com/api/selectors/#sort

Okay, so what I understand is: 1. I need to create the field, choose Page, select a parent-page, then choose single. multi, or any other... 2. I then add it to the template. 3. Go to the page I want to add page reference to 4. and select the pages that need referencing. ---

@LostKobrakai With mpdf you can also use an existing podf document as template. That comes very close to what you want. Check Importing files & templates @OrganizedFellow I think the Processwire module Page2Pdf would do the trick. That module also uses the mpdf library.

Indeed mpdf came to my mind also. Works easy. Check by example for html to pdf And afcourse the Processwire Pages2Pdf Module If your are able to create a pagetemplate with which you can generate the invoice as html page, converting it to pdf wouldn't be a problem. It's created serverside, so automatic emailing it to the buyer is also possible.

I haven't used it, but there is also this module that might suit your needs: http://modules.processwire.com/modules/process-page-draft/

I agree that the PageTable field is not perfect in this sense, but there is a way around this: Set up the Automatic Page Name Format option for the PageTable field and then go to the title field and adjust the settings in context of the template being used for the PageTable field content and uncheck required and set it to hidden. So it's still there, but at least it's not in the user's way. This way the page can be published without the title field. Hope that helps a bit.

Agreed, but a lot of that has to do with the fact that some of the popular frameworks (BS, Foundation, UIkit) introduce too much 'design' and UI components, where indeed a lot of the stuff remains unused. There are better options though.

Music on a website, shocker, cstevensjr! However, to my mind design is not just about the look of a website but the functionality, and whilst I agree about content, etc. We still have a duty to inform and make our clients futureproof to some degree. And making sites non resolution dependent seems to make sense to me.

while reading - only one in the tuts is needed on the end of every part it would really be nice to get a little prev/next navigation? <- 1. Installing Blog 3. MarkupBlog API -> great stuff to read! Kind regards mr-fan (Maybe "kongondo" means "king of ongoing doing momentous occasions" - in a crazy non-native-speaker english )

+ a lot, what teppo said RWD is not some kind of afterthought to cater for those pesky smartphones. It's about displaying your content as optimal as possible on all screen sizes and resolutions, from small to large. " Out of interest, anyone else out there want to comment on the responsive aspect Bernhard touched on? - how important do you guys think this is? Most users have tablets or phones which can display 960px sideways, so does a 960px site wide really need to crunch itself down width-ways and be 3 miles deep just to fit a portrait screen? " If i take for example the Springlands Veterinary Centre site : My phone displays 1920 x 1080, so in that sense it fits, but, it's just not a nice user experience. I have to zoom to read the left column, where the main navigation resides. The footer text is so small you hardly notice it. So it's useable, but could very easily be much better. Switching, at some breakpoint, from 2 to 1 column, including a mobile friendly navigation would not be that hard if you design with these kind of things in mind. Imo it brings big rewards. The fixed (960px) layout just doesn't make that much sense anymore. RWD is here to stay.

It sounds more that your process needs refining. I copy my unpublished pages that need review to a temporary url (as listed) and give that URL to whomever needs it. Once finished with that page, I simply trash it. The original page then gets edited or published. The original content never gets moved. It's just an affordable process to allow a review by outside interests. I use a project management system (PW based system) for any internal or client review.

Just received the latest voting update: Best Free PHP CMS Joomla - 64% Concrete5 - 22% ProcessWire - 15% Popularity vs best !!! Hopefully some more of our community can make a difference?

@blad - what version of PW are you running? Looks like there was a bug in 2.4: https://processwire.com/talk/topic/7315-change-loop-order-without-reordering-items/?p=70460 And scroll down from there for teppo's response: https://processwire.com/talk/topic/7315-change-loop-order-without-reordering-items/?p=70467 Hope that helps and you don't get that error in the dev version of PW. If you do, then maybe submit an Issue on Github and reference that thread and this one.

What about this one: https://processwire.com/talk/topic/6003-conflict-bw-parent-of-selectable-pages-and-custom-selector/?p=58695 Seems like it matches your scenario of having a custom selector. To quote arjen: "I think you have to "unselect" the Parent of selectable page(s)."

Then it sounds like you are running an old config.php file - a version of PW from before that setting was added. You can grab a new version and take a look through to see if there are any other new settings you are missing. I don't recommend replacing it with a new version - you're better off just adding the new settings to make sure you don't break any of your database settings, userAuthSalt etc.

The reason we're in this forum is because we prefer Processwire. Each Cms has its own forum and community, I came because I loved the system and the community. Forgive my personal hatred that system (wp), my behavior was not the best.

I wouldn't build non-mobile optimized site at all (well, maybe some very specific application). And for the mobile optimization: responsive is way to go about 90% of times.

In a rush so not the cleanest code, but this seems to work for me - is this what you are looking for? $p = $pages->get(xxxx); //id of page to copy $np = new Page(); $np->of(false); $np->parent = $pages->get(1); //set parent to homepage $np->template = "basic-page"; $np->title = 'test new page'; $np->save(); $np->images->add('http://'.$config->httpHost.$p->images->last()->url); $np->save();

But if you want to add Bootstrap to an existing PW install, you really only need to grab the bootstrap files - put the css and js files in appropriate locations and then modify your template files to use the div structure and css classes that bootstrap requires to work it's layout. Shouldn't be too difficult at all if you are html/css savvy.

I think the PageTable field from a recent dev version is likely a good option, but another alternative is: https://processwire.com/talk/topic/6102-batch-child-editor/ In the modules config settings you may want to disable overwrite mode (and maybe even Add mode). See the screenshot under 3. Edit mode - it allows for easy adding, sorting, and editing of titles, along with modal editing of pages, kinda like PageTable, but unlike with PageTable, pages that are added manually as children will also be available for editing via this interface.

I can read nowhere someone has crossed a line of respect => and without comparing, how will you ever know what a cms is worth ? Comparing is the very reason why I ended up here with pw. There is a reason why wp is in the news because of it's plugins what blad only confirmed by his own findings. Totally agree and re-edited my post #8

Hi everyone! I think we are might be heading into dangerous territory here. I don't think any forum should become a place for bashing another product. This forum has by far the best community I have ever experienced - let's make sure that as we grow that we keep it that way This thread is a bit of a mix - it sounds like there has been some PM'ing going on to suggest fixes, which is positive and helpful. I also think that some of the posts here about WP bringing down PW are probably in jest If one of us finds a site mentioned here that is vulnerable (no matter the CMS), I think the best approach would be to contact them directly (PM etc) with some advice on how to remedy it, rather than criticizing their choice of CMS. Point them to resources that will help them. There are several groups out there that identify security holes in a variety of software packages, including open source CMS's. They usually contact the developers first to ensure they have a chance to fix the issue before it becomes public. Certainly Wordpress has its issues for inexperienced sys admins, but it can be made much more secure with a variety of simple techniques that are widely available with a quick google search. There are even some plugins designed to block a variety of common attacks. But Wordpress is certainly not alone - unfortunately no system is immune to vulnerabilities, especially those that allows for third party plugins/modules. Above all, let's not come across as too superior - it might just bite us one day! Thanks for listening to my thoughts on this - I am not aiming direct criticism at anyone - just trying to establish a general approach to these types of topics. Any thoughts?

Hi Mike, Such a wonderful work. Keep it up... Thanks