adrian

I think the issue might be the PW version. I started using $mail->new() which I think maybe wasn't available in that version. Could you please clarify that it works if you change that line to: $mailer = wireMail();

Does this do what you need? http://modules.processwire.com/modules/fieldtype-select-ext-option/

Yep!

Then go with child pages, or pull info from the file's description and tags fields. You could possibly put the date in the description and the type (Regular, Financial. etc) in the tags field.

I would strongly recommend not doing this with an RTE textarea - it is always going to be a mess I would suggest building the table in your template file with the API. You can iterate through the PDFs in the files field, or use a repeater, or even child pages if you need more info for each PDF. Let me know if you need some help with this.

@tpr - it's implemented, although a little differently because I didn't want "default" taking up so much space in the input. I went with a warning icon and outside of the input so I could add a title tag to it. I am checking if the "FieldtypePageTitleLanguage" module is installed before checking if there is a title in the user's language. Maybe one of the ML gurus can tell me if there is a better approach: $this->modules->isInstalled("FieldtypePageTitleLanguage") && !$cp->title->getLanguageValue($this->user->language) Let me know if this suits your needs.

As it says: "use pageName instead" /** * Format required by ProcessWire user names * * #pw-internal * * @deprecated, use pageName instead. * @param string $value * @return string * */ public function username($value) { return $this->pageName($value); }

I have committed a new version which: adds a new "From Name" field setting so that the email new users receive comes from your name/email, not just a raw email address. adds support for HTML body text. A plain text version will be generated automatically from this and both sent with proper headers. makes the parseBody method hookable, so you can define more complex field tag replacements. For example, this will accomplish @Timothy de Vos's needs: $this->wire()->addHookBefore('EmailNewUser::parseBody', null, function($event) { $page = $event->arguments[2]; $pageId = $page->location; $replacement = "http://".wire($pageId)->parent->name.".".wire('config')->httpHost; $event->arguments(0, str_replace('{location}', $replacement, $event->arguments[0])); }); Please let me know if you have any problems with this new version! Thanks to Timothy for helping to test this new version and as he noted, if you want full HTML support in the supplied CkEditor body input, you'll need to set: config.allowedContent = true

Sorry @Nukro - I haven't tested with multisite. Perhaps if you can point me to where the problem is I can figure out a fix. Unfortunately I don't have time at the moment to setup the multisite module to test myself. Let me know if you can narrow it down.

@Hantsweb - any chance you have the SessionHandlerDB module installed? @tpr - I wonder if in reality this should come under an overhaul for BCE to add multi-language support in general - maybe the edit interface needs tabs to make it possible to edit titles in all languages? Trouble is that I am really going to start running out of time for major module changes here. Anyone up for putting together a PR?

Just added a new "Email Batcher" action, which has the following features: Select recipients by user role, or using a pages selector for any pages on the site Parsing of field tags in the body so you can do something like: Dear {first_name} Option to send a test email HTML body, with automated text only version also sent Special {fromEmail} and {adminUrl} tags. Ability to hook EmailBatcher::parseBody to apply other custom replacements Don't forget TracyDebugger's Mail panel when testing - it will capture the outgoing emails (so they won't actually be sent): http://processwire.com/blog/posts/introducing-tracy-debugger/#mail-panel

I am a big fan of Forklift: http://www.binarynights.com/Forklift/ dual pane finder replacement ftp/sftp directory synchronizer

Have you tried: http://modules.processwire.com/modules/croppable-image3/

@Hantsweb - can you narrow it down to a certain branch of the page tree or does it happen everywhere on your site? What version of PW? What version of this module? What other modules do you have installed?

https://github.com/ryancramerdesign/skyscrapers2

I can't seem to reproduce, but it seems like it's related to this: http://stackoverflow.com/questions/22148080/an-invalid-form-control-with-name-is-not-focusable From a quick read of that, it sounds like the "width" field is hidden and required which doesn't seem to be the case for me. Is there any chance you have some JS that could be adding the html5 "required" attribute to this? Have you checked the generated HTML to see what's going on?

Thanks @kongondo - I was PHP was strict on function name case! I think I inadvertently copied the case of $fieldName through to the getPathname() method. Anyway, it's fixed in the latest version - thanks for noticing and pointing it out.

Blog post in Norwegian on setting up https with PW: https://www.asbjornness.no/blogg/https-med-processwire-hos-proisp/

I just checked Ryan's most recent commit (https://github.com/processwire/processwire/commit/43986173fb449bf0fb967a0d613896f2e3d6b4da) and the problem is now fixed for 3.0.48.

Try rolling back your PW version to 3.0.47 - https://github.com/processwire/processwire-issues/issues/151

Hi Harmen, Sorry it's taken me a while to respond to your post. I took a quick look at the code you added and I think all that logic needs to end up in a function that we can call for children and then again for grandchildren, rather than duplicating. I am honestly wondering if this is a good fit for BCE because I am not sure that everyone will want the same formatting for grandchildren, although honestly I don't know how it looks yet, but grandchildren can have different templates/fields which would surely make a mess in a CSV? I wonder if you'd be better off with something like a custom implementation using PHPExcel (https://github.com/PHPOffice/PHPExcel). I do however agree with adding options for multilanguage support for exports. I don't expect this should be too difficult if we take the approach of a separate column for each language version of each field. Cheers, Adrian

@Ivan Gretsky - I ended up doing some more tweaking on this and decided to commit it so you can get the new version from the modules directory now. Here's a screenshot of the tabs in action: I have also added a new: FTP Files to Page action based on this request: It works with files and images and looks like this:

Yes - sorry, I thought I had linked to it earlier: Blog post documentation: http://processwire.com/blog/posts/introducing-tracy-debugger/ Forum thread: https://processwire.com/talk/topic/12208-tracy-debugger/ Modules directory: http://modules.processwire.com/modules/tracy-debugger/

Check out the PW Info and Template Resources panels in Tracy. Those will show all sorts of info on the contents of fields (and their settings) as well as the variables you have defined manually in your templates.

Tracy to the rescue: <?php foreach($pages->find("parent=recommendations") as $child) { ?> <?php echo $child->title;?> <img src="<?php echo $child->post_image->first()->size(200,0)->url;?>"> <?bd($child);?> <?php } ?> But that said, I really don't know what you mean by: "see what variables are available". If we knew more we could tweak what the bd() call will dump. Are you wanting to get a list of fields on the child pages? Do you mean actual template variables defined for each page? I really don't know. Also, I know you might be used to that style of going in and out of PHP, but when there is more php than html, this reads much nicer: <?php foreach($pages->find("parent=recommendations") as $child) { echo $child->title; echo '<img src="'.$child->post_image->first()->size(200,0)->url.'" />'; bd($child); }