Leaderboard

It was a busy summer and I finally have a little time to breathe. Now that ProcessWire 2.5 is out (as well as WordPress 4.0), it's a great time to get going with this project. I gave the idea more thought, and I'm going to start with a series of videos called "WordPress vs. ProcessWire". Each of the episodes in this series will begin by demonstrating a task/feature/approach in WordPress, then the equivalent task/feature/approach in ProcessWire. The episodes will also touch upon the architectural differences between both systems and highlight the strengths and weaknesses. Each video will be quick and to the point... somewhere between 3-8 minutes. Some episodes in the works: installation: just a simple walkthrough of the installation process of both systems pages page templates custom fields custom post types taxonomies page ordering plugins (an explanation of the repositories and how to install) forms (gravityforms vs. formbuilder) shortcodes (vs. hanna code) images embedding videos caching documentation etc. etc. I've actually created 10 episodes in one day today. This "WordPress vs. ProcessWire" series is targeted towards intermediate to advanced WordPress developers... anyone who knows how to custom theme WordPress well and has been using it regularly for at least one year. My thought is they are comfortable with WordPress despite some of its annoyances (speed, security issues, generated markup, api, data architecture, custom fields and custom post types approach), but they haven't found an alternative system that can match it pound for pound. This series will reduce the anxiety that's associated with a decision to invest one's time to learn an alternative technology. If I can prove that almost everything they are comfortable with in WordPress can be done with ProcessWire more elegantly, my hope is that it'll get a lot of people to switch. More coming soon.

Hey, Ehsan and I recently finished redesign of the website phototriennale.de. It's one of multiple ProcessWire sites I'm currently working on and I'm really happy it finally went online:

A few updates in response to the PDF that was posted earlier. More to come, but this is a start. Currently these are just on dev, but will be merged to master soon. The main README file has been updated with a link to the HTML version at the very top. I honestly think including a README.html file in the core itself is bad form because it reveals exactly what software is running the site. Some might have noticed our README files are generally blocked from http access (by the .htaccess file) for this very reason. So I think putting a link to the HTML version of the document at the top of the Markdown file is a good compromise. The default site profile has been updated with its own README file and separately hosted HTML version: Introduction to the default site profile, which goes in depth in explaining exactly how the site profile works. The template files have also been updated, telling the user to see README.txt for more information (though not sure that's really necessary).

Avatar added. Crisis averted

Reno if by far my favorite admin theme. Many kudos for Tom and Ryan! The only thing I miss is a dark skin, so I'm creating one. It is in alpha state, there is a lot of details to do. I'm planning to share it here when finished if anyone is interested.

I need to make this a real thing - nobody would dare leave their avatar blank

Custom written webpanel, build upon ProcessWire (of course). Has a little customer management function, lists projects and can create invoices (in compliance with complicated german tax laws...).

i think PW handle much more than i (or maby you) can imagine... there some good explanations on cat's... the most important thing is to create a page/content structure that it expandable and fit exactly your needs before creating fields and templates handle structure: https://processwire.com/talk/topic/3579-tutorial-approaches-to-categorising-site-content/ example: https://processwire.com/talk/topic/4116-best-way-to-structure-a-classifieds-site/#entry40330 some posts on categories: simple: https://processwire.com/talk/topic/1232-simple-categories-filtering/ nested: https://processwire.com/talk/topic/2519-nested-categories/ a very usefull gist from soma on image tags: https://gist.github.com/somatonic/5808897 imagetag module: http://modules.processwire.com/modules/textformatter-image-tags/ and for blog examples check out the blog profile fram ryan https://processwire.com/talk/topic/1394-blog-profile/ and the blog module from konkondo https://processwire.com/talk/topic/7403-module-blog/ so i wish a good reading.... regards mr-fan

Have a look here: https://processwire.com/talk/topic/7588-admin-custom-files/

I use armed Jesuit Priests for all my invoicing. Payment is never late.....

By the way, You might want to get yourself an avatar. On your 21st post the forum system will automatically and irreversibly replace the generic image by one of the spice girls (randomly chosen)

You didn't sound defensive at all!! Sorry that I started that, I can't repeat anymore that I love the site as it is The comment on the menu comes exactly from that, because the site is so positively minimalistic, and yes, because it has a print feeling (I'm a graphic designer by the way), somehow I felt that the menu brings too much animation to it. It's also natural that André (onjegolders) and I have more or less the same vision on this because we worked together and had long conversations about these kind of details. But, unlike how pwired puts it, this was NOT criticism (constructive or not), but just a friendly and completely subjective remark on a detail on a site that I admire.

Various ways to do this, probably easiest is Adrian's Migrator: https://processwire.com/talk/topic/4420-migrator/ https://github.com/adrianbj/ProcessMigrator

AdminCustomFiles is awesome!

http:// and https:// does matter, so you should use the canonical link. Also google does reward you for switching to https:// as default. source:

Use pagefield->removeAll() first then add them back.

I think it would be a nice idea to add an image/field count to these inputfields. Something like below, where it says '(12)'. For me this would be a handy little addition.

Thanks again and I totally hear what you're saying. Particularly these words... "The comment on the menu comes exactly from that, because the site is so positively minimalistic, and yes, because it has a print feeling (I'm a graphic designer by the way), somehow I felt that the menu brings too much animation to it." That's exactly true and I never thought of it like that. The animation element is almost at odds with the static print feel, almost too slick. I get that completely and I wonder if that's why I have sort of mixed feeling about sliding menus. Hmm. Food for thought. Thanks.

I think Diogo's suggestion of it being hidden on your homepage as it gives the full effect of the beautiful photograph, then it could show on the inside pages but you can be pleased with your work

The answer is yes to everything with a little learning. Custom fields are what Processwire is all about so don't worry about your custom post types - that's covered

Use the selector option for your page field. template=sharks, sort=title

I call it constructive criticism with the goal to make things better - many times giving rise to things as you mention: negative reaction, a surprise, is it a "developers" type reaction, etc, etc, the list goes on. I almost decided to stop with it, but seeing you talk about it so openly made me change my mind.

Thanks you both for the great effort keeping with the enormous pace! I just dropped the pack on a 2.5 installation I'm working ATM and looks good so far, will try to report if I find something.

There's an option in the current .htaccess to forward to the www version of your site. But... I prefer a URLs without a www. However, I would still like said URLs to be accessible should someone type in the www sub-domain in their URL bar, or link to the "www version" of the URL. If you're like me, this could be a useful addition to the .htaccess file... # ----------------------------------------------------------------------------------------------- # OPTIONAL: Redirect users to the non 'www.' version of the site (uncomment to enable). # For example: http://www.processwire.com/ would be redirected to http://processwire.com/ # ----------------------------------------------------------------------------------------------- #RewriteCond %{HTTP_HOST} ^www\. #RewriteCond %{HTTPS}s ^on(s)|off #RewriteCond http%1://%{HTTP_HOST} ^(https?://)(www\.)?(.+)$ #RewriteRule ^ %1%3%{REQUEST_URI} [R=301,L] For me, this is the simplest way to do things. It also means any auto-populated canonical tags, such as... <link rel="canonical" href="<?php echo $page->httpUrl; ?>"> ...will never display the www version of your site. I know many of you will know this already, but I always forget exactly what to put in there, so this will come in useful for me and others in future, I hope! What are your thoughts on this? Some other solutions? I've heard about mod_alias also? How would that work in conjunction with ProcessWire? Would it be a better solution?

Have you seen Fredi? http://modules.processwire.com/modules/fredi/

As adrian said. Don't know if they influence on this but you have some problems with your code: <li><a href="<?php echo $page->url; //echo was missing ?>">Предложение</a></li> <li class="active"><a href="<?php echo $page->url; //echo was missing ?>spros/">Спрос</a></li> if($input->urlSegment2) throw new Wire404Exception(); if($input->urlSegment1 == 'spros') { $selectSpros = TRUE; } else if($input->urlSegment1) { throw new Wire404Exception(); } else { $selectSpros = FALSE; } // I think like this is more readable: if($input->urlSegment1) { if($input->urlSegment2 OR $input->urlSegment1 != 'spros') { throw new Wire404Exception(); } $selectSpros = TRUE; } else { $selectSpros = FALSE; }

Hi Adrian, thanks a lot! That's the solution. The children page was missing the create pages permission. Was hard to grasp at first, but know – after some tinkering – I understand all those the dependencies.

Have you checked the permission on the templates that are allowed as children of the template assigned to the page that you are expecting a new button on? So the parent template must have Add Children and the child template must have Edit Pages and Create Pages for the author role.

Hey Ivan, Just testing here to confirm and the url segments are not being included in $page->url for me. Not very helpful I know - maybe someone else will have an idea why you are getting different behavior.

Fixed in dev: https://github.com/ryancramerdesign/ProcessWire/commit/63692bdda65090032d4d5a0c29475263ea707bf7

Since the standard behaviour of the file field is to not overwrite files, I think yes. But I also think the language management should handle it different. What you can do is find the folder in assets/files/pages/ holding the files (while editing the language the id is shown in the address bar), delete all of it and reupload again. Not elegant but should work.

Of course there will be some that dare to do so

https://www.google.ch/search?q=processwire.com%20active%20language%20api&rct=j First result

Like it was said yes, it can. But if all you want is a simple tumblog have a look at Chyrp http://chyrp.net/ That said, PW can perfectly take care of the task and this is probably how I would approach it in PW: — Create the blog template and page to hold the articles in the tree — Create a template for each type of post (image, text, video, quote, whatever...) with the custom fields needed for each — Limit those templates to have the blog page as parent (this will allow you to have the quick creation of these on the quick button) — On each of these template files create the PHP for the individual post page ex: <?php //quote post if(!count($options['pageStack'])) include('head.inc'); //render the head only if this page is not being rendered inside another page ?> <blockquote> <?=$page->quote?> <footer> — <cite><a href="<?=$page->cite_source?>/"><?=$page->cite?></a></cite> </footer> </blockquote> <?php if(!count($options['pageStack'])) include('head.inc'); // same as with head — and then render them on the blog template: <?php include('head.inc'); foreach($page->children as $post) { echo $post->render(); //render all posts } include('head.inc'); Note: this is minimal code just for example, written directly in the browser and completely untested. See how to paginate results here https://processwire.com/api/modules/markup-pager-nav/ And read about categorisation here https://processwire.com/talk/topic/3579-tutorial-approaches-to-categorising-site-content/

I can't really help you with your error, but maybe use this to exclude all the admin stuff. has_parent!=2 Also you could use just a template to get all fields, without an extra page. $search_here = $templates->get("name"); foreach($search_here->fields as $field){ … }

Installed your admin theme. First impression... love it! One tiny, teeny thing. I noticed the new default admin theme, under the setup tab, it has icons for templates and fields. The field icon is a single cube and the template icon is like a mini pyramid of cubes. I saw those and suddenly the concept of templates and fields and how they normally relate to one-another made perfect sense. On yours, they both have a little lightning bolt icon, which is cool, but I think the cube and pyramid cube thing is very clever and succinct visual cue. But, of course, that's not a major thing at all and what I really want to say is: yes, best looking admin theme of any CMS I have ever used, ever. Thanks and well done!

Thanks Reno, staring me in the face, as they say!

Thanks for the compliment Douglas (although it is in the process of being updated)

I liked the nav too. If you ask a room full of people what they think there will always be a difference of opinion. You don't have to change things people have suggested of course but you may find you get more suggestions here than other places

the cookie setting script should be placed as high as possible in the dom. if you place this line at the bottom, the images on the first page load will load normal, as the php-script can't read the cookie, because it's not yet set. once the cookie is set, it will work as intended.

Great looking site, I agree with Diogo though about having the navigation hidden on inner pages can be a bit annoying. I suppose if it appeared on hover rather than click it may be a nice compromise. Really nice work though. And welcome to the community

Thanks to Manfred's relentless efforts (and a little merging by me), the German language pack for the stable version of ProcessWire is now officially updated for 2.5. I have to admit the merge was a bit of a rocky road, so if anyone notices any issues with this in 2.5 (I have only checked it briefly myself), please report them. The best way to do so is via the language pack's GitHub issues.

You are overwriting the $pictures variable in each loop iteration. It will only ever have the last image in it that way. You should concatenate instead. Something like this... if(count($page->images)) { $pictures = ''; // if the page has images on it, loop through them... foreach($page->images as $image) { $image = $image->width(400); $pictures .= "<img src='$image->url' alt='$image->description' />" . "<blockquote>$image->description</blockquote>"; } // output the images at the top of the sidebar $sidebar = $pictures . $page->sidebar; } Note that it is now $pictures .= "..." rather than $pictures = "..."

ProcessFish

There is nothing really wrong, just a case of not very explanatory notices. Go to the edit page for the field and save it again. You might need to save it twice to get the message to go away. Some discussion about it: https://github.com/ryancramerdesign/ProcessWire/issues/582 https://github.com/ryancramerdesign/ProcessWire/commit/c1dd1b37e529eff4e5219d1b790275fe71771936

Great BIG Thankyou!!!! I tried so much - since i thought it should be an easy way here....it works like a charm. I will present it on a casestudy - i've done my first project with a Adminpage for images (manage images as pages central) and since i don't wanna fall back to the /page/ while editing i search for some fancy way with a lightbox it works as expected. here is the complete code for a simple template that runs with CustomAdminPage http://modules.processwire.com/modules/process-admin-custom-pages/ <?php // Bilderübersicht Custom Admin Page ?> <style type="text/css" media="screen"> /** * larget magnific popup */ .mfp-iframe-holder .mfp-content { max-width: 1200px!important; } </style> <script type="text/javascript"> $(document).ajaxComplete(function() { //add trigger class and modal setup $('.PageListActionEdit a').each(function(){ $(this).addClass("lb-edit").attr("href",$(this).attr('href')+"&modal=1"); }); $('.PageListActionNew a').each(function(){ $(this).addClass("lb-edit").attr("href",$(this).attr('href')+"&modal=1"); }); //setup lightbox $('.lb-edit').magnificPopup({ type: 'iframe', disableOn: 0 }); }); </script> <?php //get Magnific css and js $this->modules->get('JqueryMagnific'); //render PageListtree with setting the parent page $formImages = $this->modules->get('InputfieldForm'); // prep the form $wrapperImages = new InputfieldWrapper; // a wrapper $wrapperImages->attr('value', '<h2>Bilder</h2>'); $i = $this->modules->get('ProcessPageList'); // get the pagelist process $i->set('id', 1015); // setting the parent page $pageTreeImages = new InputfieldMarkup; // the placeholder $pageTreeImages->value = $i->execute(); // fill the InputfieldMarkup form field... $wrapperImages->add($pageTreeImages); // put inside the wrapper... $formImages->append($wrapperImages); // append the wrapper echo $formImages->render(); So i've used the PageListTree with a preselected parent and the edit function works within the modal..... It's not my threat so i couldn't vote for best answer! Best Regards

On your page where you would want to see the Foundation Callout, you would have a textarea field (mine is called "body"). In the body field I add the Hanna code: [[wgc-panel-home-bottom-holiday]] I make use of the _init.php file and have the following: $body = $page->body; In the particular template file or better yet in _main.php or header.inc you would have: echo $body;

Pushed an update to the module: New settings: Path to TemplatesIf you use a delegated template approach, please provide your path to the templates (relative to templates directory). Collapse unpublished rowsIf checked, unpublished PageTable parts are rendered collapsed and can be opened on click. (hidden) CSS classes for PageTable page statusThe rendered parts (the div.renderedLayout) get the status of the page as CSS class: ".pte-hidden" for hidden pages ".pte-unpublished" for unpublished pages ".pte-locked" for locked pages @titanium: Could you please test the new version (0.2.0.) with your template delegate approach. I don't use it, so I can't test it quickly. But should work

@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.

+1 A bit OT regarding the threadtitle but another great thing that one can use with ProcessWire is the Hannacode module. When fetching pages from an online resource and store them locally I want that links in the bodycontent point to the local resources if they are available. But which one is, will or should be locally stored isn't easy to determine when fetching the (first) pages is in progress. Therefore I installed Hannacode and store every a-href in the bodycontent as hannacode: [[source_url source_url=http://example.com/path/to/page.html]] The codesnippet that get invoked for every link: $p = $pages->get("template=elektronik, source_url=$source_url"); if(0<$p->id) { // page is locally available echo $p->url; } else { // page is only online available, add a css class to the tag that this can be shown in the page output echo $source_url . '" class="externLink'; } This way I can add or remove pages without breaking (locally) references in other pages. Summary: created an importer script, modified the renderNav function, added one Hannacode and some css styles = a nice and comfortable to use site!