adrian

Sorry for the stream of updates, but you can now embed BCE into the flow of fields within the Content Tab. This makes for even easier access to inline ajax editing of child pages. It probably only makes sense for Lister, Edit, and Export modes. Just pushed this option to the dev branch.

Thanks @mr-fan! I just put together another screenshot showing how you can use BCE as the equivalent of an inline PageTable field interface. Obviously these are just child pages and are not callable from a field, but it provides an excellent editing interface in a dedicated tab along with all the filtering options of lister. It also doesn't have any of the problems with a PageTable field regarding editing the content page directly and not having new pages automatically added, etc. The inline ajax editing is also a great bonus over the popup modal editing. Of course, this inline editing requires ListerPro, but I think it is worth it

Forklift is my tool of choice - great FTP client and more importantly for me, a really nice dual pane Finder replacement which I can't live without!

Just added some new features and a couple of bug fixes to the dev branch. Fixes for export mode with certain complex field types Added support for AJAX loading of BCE - especially useful if you are using the "New Tab" position option - requires PW 2.6.11+. This will make Page -> Edit load much quicker when you have lots of child pages. New Lister mode - this allows you to view (and configure the default columns/filters) all children under the current page. If you have ListerPro installed you can also use the Actions on the children. This also supports inline editing which makes for a very quick and easy way to edit the key fields on each child page. Please let me know how the new AJAX load and Lister mode features work for you - I think I need some wider testing before pushing this to the master branch. You can define the Lister config settings sitewide, and then provide overrides for each parent page that has been enabled under "Configurable Pages" This screenshot shows the new Lister mode configured to show a predefined set of columns - a great way to preview the page content of child pages. This shows the Lister Inline Edit mode - making for very quick editing of key fields in child pages.

The issue is the empty <i> tag. You could try: <i class="krown-icon-bubble" style="color:#e64d36"> </i> Otherwise, the recommended approach seems to be this setting: // allow i tags to be empty (for font awesome) CKEDITOR.dtd.$removeEmpty['i'] = false

Three free modules that might be useful (to varying degrees) for your request to be able to preview changes: http://modules.processwire.com/modules/process-page-draft/ http://modules.processwire.com/modules/process-preview/ http://modules.processwire.com/modules/process-textarea-preview/

Ok, it should be fixed in the latest version. This fix is only needed for PW 2.6.6+ but I think it should also work fine on older versions.

Actually the issue is not what I thought - it is a recent PW dev problem. I checked a PW 2.6.1 stable site and it works fine. I am not sure what has changed in PW dev to cause this - I will need to investigate further - hopefully I can find some time in the next few days to figure it out. EDIT: This is the PW commit that breaks things: https://github.com/ryancramerdesign/ProcessWire/commit/fd719abc6ad4dc12792592b6715f986d29af2625

Sorry about this Charles - I'll take a look a little later today or maybe tomorrow - I had a similar issue with CustomUploadNames which actually stole the "Add Category" code from this module. I'll probably just need to make the same changes I made to that, so should be a fairly easy fix.

Actually if you want it to save to the assets/files/pageid folder for the current page, this is what you want: $page->filesManager()->path(); But do you want to save it directly, or would you rather just add it to a files field for the page? $page->pdfs->add("invoice.pdf"); If you went that route you could do: $mpdf->Output('/tmp/invoice.pdf', 'F'); $page->pdfs->add("/tmp/invoice.pdf"); unlink("/tmp/invoice.pdf"); or something like that

Also make sure "Show in the add-page shortcut menu" is set to Yes.

It isn't installed by default, so just go to Modules > Core > Select Options and install

Hi @ArtArmstrong - thanks for your efforts with this and for sharing here. Just in case you missed it, the PW core now has FieldtypeOptions (http://processwire.com/blog/posts/new-options-fieldtype-processwire-2.5.17/) which is an enhanced version of FieldtypeSelect which works with InputfieldRadios, InputfieldChecboxes, InputfieldSelect, InputfieldAsmSelect, etc. Perhaps there is still an advantage to your module - I'd be curious to hear more. Thanks again!

http://modules.processwire.com/modules/inputfield-textarea-markup/

It's the same as wire('page') wire('config') Same goes for all PW variables (https://processwire.com/api/variables/)

I saw those two, but figured that since they are $pages->count() calls they wouldn't be a problem as they are not loading those page into memory - right ? Oops, they are count($pages....), rather than $pages->count(). Maybe that simple change would make a big difference.

I belie Unfortunately he already tried that based on my suggestion here: https://processwire.com/talk/topic/10609-processwire-site-header-and-footer-used-in-wordpress-blog/?p=100209 Are there any other places I have missed where adding a limit might help?

I am going to chime in and say that isn't really correct There are lots of acceptable ways to do something, but even as brilliantly thought out and architected as PW is, it doesn't prevent you from writing template code that results in slow/inefficient queries and also potentially dangerous holes that users could exploit. Keep in mind that there isn't any CMS out there that can prevent you from making these mistakes. PW makes it easy to do it the RIGHT WAY, but you still have to think things through, follow best practices, and if in doubt ask someone more experienced if you are doing it right, or at least make sure you are not doing it wrong!

Ok, good to know - I am not sure what the problem with the dashboard is. If you don't want the dashboard, I would consider doing the migration again without the blog module installed at all - I think its main benefits are setting up everything for you and also providing the example front-end markup code - great for PW newbies, but I don't think you need either of those things. This way you can start with a clean setup (no existing blog related fields or templates) and the migrator will take care of adding everything as needed. Then just write the template code to output the posts and you are good to go. You can even steal some bits from the markup code from the blog module if it helps.

What happens if you add a limit to the selector on this line: https://github.com/kongondo/Blog/blob/master/ProcessBlog.module#L825 Make it like this: $posts = wire('pages')->find('template=blog-post, include=all, sort=-blog_date, parent!=7, limit=10');

Sorry you are having issues with the blog dashboard. As I mentioned, I don't use it, so I am not sure how it works or what might be causing this issue. I saw your posts in the blog thread - hopefully you will get some help over there. Do you have debug mode on? Any errors there or in your php error log? It might be useful to start inserting some log statements in this method: https://github.com/kongondo/Blog/blob/master/ProcessBlog.module#L798 to see where things are getting to. There is a loop that iterates through all posts. I would also maybe start commenting out sections in this method to see if a certain chunk of code is to blame for the timeout. There is also some code in that loop that checks for comment stuff. Did all your post comments import OK?

If you having issues getting this to work, I have posted two separate ways of doing this: https://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/page-5#entry89599 and https://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/page-5#entry89616 Pros and cons to each version, so you should read all the posts in between as well. Personally I would go with the second one, just be aware that if you want it to work on the front-end you need to consider the name of your form fields.

What are the rules under Input > Selectable Pages for the "coach_user" page field? Do they allow adding users?

Good to here - yeah, the migrator template and field name defaults are not matched up for blog module. I don't personally use the blog module (Kongondo has done an awesome job with it, but I don't need the dashboard and I prefer to set up manually to configure exactly to my needs). Also when migrating a WP blog, migrator by default, uses the template and field names that I prefer. When you get a minute, it would be great if you could put together some tips for other users based on your experience. I think it's a pretty powerful took for getting more people using PW, but I don't think it's getting that much use at the moment. I'd also love to here any suggestions that you might have for improvements.

But you're not calling the repeater field anywhere in your template code. I also don't understand why you have all these references to Wordpress paths under your assets directory. With a repeater field you want to be foreach'ing through each item in the field. Read the section "Outputting Repeatable Fields" on this page: https://processwire.com/api/fieldtypes/repeaters/ If you still can't get it to work, show us your new code and we'll help you along.