adrian

I forgot about that - should have remembered there was something built in

I am sure Wanze will be able to offer up a solution to get the filesize from the path. I just wanted to chime in with a nice function for converting to human readable filesizes: http://jeffreysambells.com/2012/10/25/human-readable-filesize-php function human_filesize($bytes, $decimals = 2) { $size = array('B','kB','MB','GB','TB','PB','EB','ZB','YB'); $factor = floor((strlen($bytes) - 1) / 3); return sprintf("%.{$decimals}f", $bytes / pow(1024, $factor)) . @$size[$factor]; }

I was a DirectoryOpus fan on Windows, and while I agree that Forklift doesn't have anywhere near as many config options, what it does, it does mostly very well and it has everything I need. It is not perfect but, in hindsight, DOpus almost has too many options. Each to his own right

Ionic is great and can work very nicely with ajax calls to a PW db and allows for iOS and Android development together with cordova. If you don't like angularjs (integral to ionic), take a look at famo.us or React Native.

Very nice - love the filter tool! Also - great to see the mention of PW on the credits page: http://ohmspeaker.com/credits/ Just one quick thing - the link to badasstheme.com on that page is broken.

Ok, just pushed a new version to dev that adds support for choosing an alternate Parent. This allows you to bring in child pages from any other parent in the page tree (like I mentioned in my previous post above). It's a new option under the Content / Deletion / Protection tab - obviously only available for page specific config settings. Also added an option to determine whether Filters/Columns/Actions are available in Lister mode - checkbox under the Lister mode settings tab. This version might require a little extra testing regarding allowed templates for editing/adding pages. Please let me know how it goes.

What version of PW are you running? I don't see a numChildren() of line 754 on either 2.6.1 stable or the latest dev.

@mr-fan - thanks for the great feedback, testing, and the PR for language labels. Yep - I think the issue with the Lister view not working when there is an images field selected is a problem with PW dev / Lister I don't quite understand the Normal/Ajax load problem (I am sure I am missing something obvious so will look better later to see if I can figure out why that needs to be an available option when Open is checked. Yep - I was planning on making the Lister EDIT mode configurable to include the modal option, but there is something stopping it from working properly in modal mode - I think it's because Lister is in an iframe, but I will look again and see if I can get it to work - it would be much nicer for times when inline/ajax editing is not enough (or the user doesn't have ListerPro). I am also thinking of making it possible to choose a different parent (or maybe even use a full PW selector) so you can make BCE grab children from somewhere else in the page tree - I think this would only work for Lister, Edit, and Export modes, but could be very cool - kinda like the ability of PageTable to specify a different parent, but even more powerful. I'll hopefully play with this in the next few days and post a new dev version then.

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?