Peter Knight

Actually, I think I just found the answer to my questions apart from number 2 1. Retain the "Add New" button on the top right of my Admin screen with just "Add new blog post" appearing. I found some Access settings for the Blog template and this enabled this. 2. Restrict her view of the site tree to just the Blog and child pages No idea how to do this 3. All her to edit any pages under the blog parent Access setting for that particular template.

Hi guys I have a tiny PW site with a blog and want to give my client admin access create and edit her own posts, moderate comments etc. I've already set her up as a User, assigned her a role of "blog-author" with permissions of: View pages Edit pages View Blog page User can update profile/password However, when I log in as her I am wondering how I could achieve following within the admin IE Not hard-coding or PHP-ing? 1. Retain the "Add New" button on the top right of my Admin screen with just "Add new blog post" appearing. 2. Restrict her view of the site tree to just the Blog and child pages 3. All her to edit any pages under the blog parent Particularly confused as to why no. 3 is not working as her role of "blog-author" has "edit-pages" ticked.

Nico Youre right of course - I could always use a very long template name. I just tried your example and wierdly enough, when I hit submit PW tried to create a separate template for every word in the template title. So not I have templates called a automatically Gallery generate template this to use - Wierd !

When creating or adding a new template I'd like a short template description field. That template description should then also be visible when choosing a template for a page. If you've a lot of templates, it gives editors some asseurance that the template they are selecting is the correct one.

Cheers. Looks pretty comprehensive and I've got the printer working it's way through it. Could you point me in the direction of how to output fields from my selected pages? I've created a page field, added it to my template and then on my actual page, I have selected my 3 pages. That was all remarkably straighforward. But how do I get the field values I want out onto a different page? foreach ($page->pattern_type as $pt) { echo $pt->title; echo $pt->featured-image; echo $pt->featured-summary; } Should I replace "pattern_type" as my Pages Field name?

Thanks diogo There's just too many ways to do this in PW. Guess thats the beauty of it! That would certainly work. Would my client be able to reorder the sequence of featured items though? They could be from very disparate areas of the site. Thank you for introudcing me to the page field! I hadn't seen it before and watching this, I can't believe how simple and powerful it will be for my client. I've purchased ProFields anyway but I'm sure I'll find a use for it

Hi I have an area on every page of my site which includes 3 columns of "featured" content as determined by my client. Each feature consists of: A page title (and link to parent page) An image Small paragraph of summary text I know that I must add these fields to my pages and then populate them with content. The part i'm stuck at is how best to let client my determine which 3 pages get featured. I think number 3 here is the best way but wanted to ask more seasoned users their approach. Should I ... 1. Create some mechanism for a client to specify a page as "featured" thereby triggering inclusion into a footer. I'd have some API call scanning pages for a checked "featured" checkbox etc or 2. Create 3 small sub-pages elsewhere on the site consisting solely of the title,image,paragraph fields. I could place them in some kind of sub-folder called "featured". My client would be told to only ever have 3 sub pages and they could edit, rearrange etc or 3. Create a single page called "Featured" consistign of the new ProField Table whereby client can order and reorder as they wish. That ProField Table would be a row consisting of "Title", "Image" and "Summary".

Love Phillips work on the theme with the split tree/editing Having used Silverstripe and MODX, split screen editing is much better IMHO. As a new comer to PW, I appreciate that there's a simplicity in displaying only the tree but I'd love to see this as an option.

Guys - thanks for all your help. I did a reboot of MAMP, rebooted my Mac and did a fresh install of PW and it's working now. Appreciate all the help though. What are the benefits of a virtual host when developing locally? And whats the difference between running on MAMP or some localhost?

MAMP 3.05 running on Mac OSX Mavericks Might fire up the other Mac and see if I have the same issue and try one of the Windows machines too.

My mistake - I *can* edit the htaccess file and have uncommented the appropriate line RewriteBase / So right now I am getting the error as follows. Not Found The requested URL /index.php was not found on this server.I presume there should be an index.php file in the root of /processwire ?

Cheers adrian. Understood. I've reverted the folder name back to the original name. Re the URL you supplied, I can confirm that mod_rewrite is working. Unfortunately I can't make any htaccess chaneges this is a local install. Thanks for the help. I'll perform a remote install.

Ok, fair enough - thanks for clarifying. Same issue though. Installation says I should visit /processwire/ to access the admin but browsing to this gives me a 404 on a local install.

I did a reinstall with a new database and left the Admin Login URL on the setup screen as "processwire". After successful installation, I was given the new URL of /processwire/ Looking at my local files, the default folder called "wire" is still "wire" so I'm not suprised to get a 404 error. Renaming that folder to "processwire" throws the original "forbidden" error. I think I'll just install remotely for the moment or try the stable branch

No joy. I located the appropriate the table and indeed it was set to "wire" but changing it to "processwire" or "admin" has no result when I used that new directory within the URL. Thanks anyway Interesting bu the admin url is by "wire" by default when I unzip the latest gihub build

Hi guys I'm attempting to install PW locally for the first time. I've created and connected to the database but when I visit my admin/manager URL, I get the following error http://localhost:8888/procewsswire-test/wire/ The actual demo site is showing fine with the minimal site profile. This is a download from the dev branch of github. Just wondering is it a folders permission? I don't think I can CHMOD locally?

Cheers for the reply and apologies re the framework mixup. I guess I'm approaching this with a few expectations picked up from my other blogging platform. Within that, almost every part of the blog was a mini template which you could tweak to make fundamental layout changes.

Brilliant, thanks

Hmm. I think I see whats happening. Youre basically saying "for each page that uses blog-post as a template, output X". I just realised my output isn't creating a new row for each blog post so I modified it to be as follows. <!-- START Nested Column containing featureimage and post-summary --> <?php $blogposts = $pages->find("template=blog-post"); foreach ($pages->find("template=blog-post") as $b) { echo " <div class='row'> <div class='small-12 large-6 columns'><img src={$b->blog_images->first()->url} /></div> <div class='small-12 large-6 columns'><p>{$b->title}</p><p>{$b->blog_summary}</p></div> </div> "; } ?> <!-- END Nested Column containing featureimage and post-summary -->

Thanks adrian and marcus. Appreciate these are very noob Qs. The following code is working for me based on your suggestion. Basically, I have two responsive columns (using Foundation) and the left one outputs the image while the right one outputs the summary. <!-- START Nested Column containing featureimage and post-summary --> <div class="row"> <div class="small-12 large-6 columns"> <?php $blogposts = $pages->find("template=blog-post"); foreach ($blogposts as $b) { echo "<img src={$b->blog_images->first()->url} />";} ?> </div> <div class="small-12 large-6 columns"> <?php $blogposts = $pages->find("template=blog-post"); foreach ($blogposts as $b) { echo "<p>{$b->blog_summary}</p>";} ?> </div> </div> <!-- END Nested Column containing featureimage and post-summary --> I'm slowly getting there. I can see how PW will gradually improve my PHP too and am slowly understanding some of this variables stuff. No idea why I agreed to put together an urgent client project on a tight deadline with a CMS I'm not familar with.

I have a working blog thanks to this excellent module by kongondo http://modules.processwire.com/modules/process-blog/ Now that I'm tweaking it a bit, I am running into some noob problems. For example, my individual blog posts have 2 fields which I want to call onto the blogs main homepage. The two fields are: 1. The first image used in an image field called blog_images <!-- Display the first blog image --> $blog_images = $page->blog_images->first(); if($blog_images) echo "<img src='$blog_images->url'>"; 2. The content of a textarea field called blog_summary <!-- Display a summary of the blog --> echo $page->blog_summary; Both of these fields have content and I can call that content onto the blog post page with the PHP above. But calling it on the Blog homepage give me nothing and no errors. Within my Pages tree, the structure of my setup lookis like this Blog Posts Post 1 Post 2 Post 3 Post 4 Categories Tags Comments Widgets Authors Archives Any help much appreciated. Thanks

Thanks so much, Marcus. I'll try that later. I know with my "usual" CMS I could achieve this in about 15 - 30 mins so it's great to see it's as easy within PW

If my client has added more than 1 image to an image field (called "blog_images"), how could I 1. Output a grid of images on my webpage as cropped thumbnails. 2. Make them clickable so they display a lightbox such as http://fancyapps.com/fancybox/ Thanks

Can I suggest an improvement to the PW Manager. When editing a page, I should be able to mouse-over a fields label to display the actual field name as referenced in the API and templates. I just had a problem whereby calling a series of images onto a page was not working for me using the code example from the API docs. <?php foreach($page->images as $image) { echo "<img src='$image->url'>"; }?> This was because the field within my manager page was actually "blog_images" and not the regular "images" field. As both fields had a label of "Images" and the regular images field wasn't used elsewhere on my manager page, it took a while to realise my mistake. Better house-keeping on my behalf would definitely help but it's an idea that might make building sites a little quicker.

Interesting - thanks guys. I've installed CK editor and it's an improvement. I've used it before across other CMS and IMHO it's still too much clutter. Technically it seems to work well and there are plenty of great options. Just wish we had the cleanliness of redactor and less of those 90s pop ups etc